Hi, A Question on BPEL4WS 1.1 compliance in ODE .9

[Prasanna Rajaperumal <pr...@soa-matrix.com>]

Hi all,

BPEL4WS 1.1 requires a global WSDL to be set, as BPEL4WS 1.1 does not 
allow import statements in BPEL.
How and where do i specify this in the DeplymentDescriptor.

Do anyone have an example DeploymentDescriptor for this.

Thanks
Prasanna

Re: Hi, A Question on BPEL4WS 1.1 compliance in ODE .9

[Maciej Szefler <mb...@intalio.com>]

In future versions of ODE (or svn trunk), you can specify the BPEL 1.1
wsdl file using the "bpel11wsdlFileName" attribute on the <process>
element. If you do this, you will need to specify the "fileName"
attribute (which specifies the process file name).  Watch the page

http://incubator.apache.org/ode/user-guide.html#UserGuide-ProcessDeployment

for documentation.

-mbs

On 6/11/07, Prasanna Rajaperumal <pr...@soa-matrix.com> wrote:
> Hi all,
>
> BPEL4WS 1.1 requires a global WSDL to be set, as BPEL4WS 1.1 does not
> allow import statements in BPEL.
> How and where do i specify this in the DeplymentDescriptor.
>
> Do anyone have an example DeploymentDescriptor for this.
>
> Thanks
> Prasanna
>
>

Re: Hi, A Question on BPEL4WS 1.1 compliance in ODE .9

[Maciej Szefler <mb...@intalio.com>]

It seems that this is no longer possible with the compile-on-deploy
option. You can manually compile the process with bpelc command which
has a -wsdl option, and then place the generated .cbp file in the
deploy directory.

I'll add a property to the deployment descriptor that lets you specify
a 1.1 wsdl, so you don't have to go through this in the future.

-mbs

On 6/11/07, Prasanna Rajaperumal <pr...@soa-matrix.com> wrote:
> Hi all,
>
> BPEL4WS 1.1 requires a global WSDL to be set, as BPEL4WS 1.1 does not
> allow import statements in BPEL.
> How and where do i specify this in the DeplymentDescriptor.
>
> Do anyone have an example DeploymentDescriptor for this.
>
> Thanks
> Prasanna
>
>