Issues with the BPEL Define Correlation wizard

View: New views
2 Messages — Rating Filter:   Alert me  

Issues with the BPEL Define Correlation wizard

by Brynjar Glesnes :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I have a couple of issues when using the BPEL Define Correlation wizard.

1) The elements I like to use for correlation id has type xsd:string. This is a major problem for the Define Correlation wizard. I'm not able to connect the values that should correlate on the second step in the correlation wizard. However if a change the type to xsd:int, I'm able to connect the correlated nodes - and I'm able to complete the wizard. If I manually change the type back to string after having completed the wizard everything works fine runtime and design-time.

2) The xPaths of the propertyAliases of the wrapper WSDL generated by the wizard are wrong. When building or verifying the BPEL I get errors like:

ERROR: Can not find the element "ns2:CorrelationId" at the namespace "http://xml.netbeans.org/schema/Person". Expression: "/ns2:CorrelationId"

When I make the xPaths relative the errors vanish (i.e. /ns2:CorrelationId -> ns2:CorrelationId )


This seems like bugs to me. Can someone verify?

I'm using the 20080919 open-esb distribution.

Re: Issues with the BPEL Define Correlation wizard

by Sergey Lunegov :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Please try the latest build.
This problem was fixed recently.

Thanks,
Sergey


Brynjar Glesnes wrote:

> I have a couple of issues when using the BPEL Define Correlation wizard.
>
> 1) The elements I like to use for correlation id has type xsd:string.
> This is a major problem for the Define Correlation wizard. I'm not
> able to connect the values that should correlate on the second step in
> the correlation wizard. However if a change the type to xsd:int, I'm
> able to connect the correlated nodes - and I'm able to complete the
> wizard. If I manually change the type back to string after having
> completed the wizard everything works fine runtime and design-time.
>
> 2) The xPaths of the propertyAliases of the wrapper WSDL generated by
> the wizard are wrong. When building or verifying the BPEL I get errors
> like:
>
> ERROR: Can not find the element "ns2:CorrelationId" at the namespace
> "http://xml.netbeans.org/schema/Person". Expression: "/ns2:CorrelationId"
>
> When I make the xPaths relative the errors vanish (i.e.
> /ns2:CorrelationId -> ns2:CorrelationId )
>
>
> This seems like bugs to me. Can someone verify?
>
> I'm using the 20080919 open-esb distribution.