Disabling the BPEL validation during deployment - Websphere

This is a discussion on Disabling the BPEL validation during deployment - Websphere ; Hi All, Is it possible to disable validation of BPEL during the deployment of ear?The problem im facing is that im trying to place the libraries in external folder.This approach works fine in windows environment.when i try to install the ...

+ Reply to Thread
Results 1 to 3 of 3

Disabling the BPEL validation during deployment

  1. Default Disabling the BPEL validation during deployment

    Hi All,



    Is it possible to disable validation of BPEL during the deployment of ear?The problem im facing is that im trying to place the libraries in external folder.This approach works fine in windows environment.when i try to install the ear in unix,it throws errors saying that XSD and port type not found.So if im able to disable the BPEL validation,i will be able to install the application.


    Have any one tried placing the libraries in external folder.



    Thanks in advance.

  2. Default Re: Disabling the BPEL validation during deployment

    Validation always fails for a reason, disabling it is likely pointless.

    --
    Dan Zrobok -Technical Architect - Perficient
    WID/WPS/WESB Blog: http://blog.danzrobok.com


    <dwforums@us.ibm.com> wrote in message
    news:1759827413.1212697176811.JavaMail.wassrvr@ltsgwas009.sby.ibm.com...
    > Hi All,
    >
    >
    >
    > Is it possible to disable validation of BPEL during the deployment of
    > ear?The problem im facing is that im trying to place the libraries in
    > external folder.This approach works fine in windows environment.when i try
    > to install the ear in unix,it throws errors saying that XSD and port type
    > not found.So if im able to disable the BPEL validation,i will be able to
    > install the application.
    >
    >
    > Have any one tried placing the libraries in external folder.
    >
    >
    >
    > Thanks in advance.




  3. Default Re: Disabling the BPEL validation during deployment

    That was pretty "clever" answer, really.

    1.) Ive faced the very same problem and found out that it was caused by disabled "Deploy with Module" checkbox in Module's Dependencies view.

    2.) It's also worth closing and opening the Module again in Business Integration perspective (=recreating App/EJB/Web projects). App project contains references to other used (shared) libraries, so recreating it may also help.

+ Reply to Thread