Moved riftsaw user forum.

Hi Federico

A problem with dynamic endpoint references has been fixed in the current trunk (https://issues.jboss.org/browse/RIFTSAW-325), which may help.

I would normally suggest trying out the latest snapshot, but there is currently a problem with the build as we are in the process of upgrading the esb, juddi and jbossws versions. If you keep an eye on https://hudson.jboss.org/jenkins/job/Riftsaw/ until the job goes blue and then download the snapshot to try.

Regards

Gary

Sorry, just seen the environment details at the end - so you have already been using a snapshot that would incorporate that RIFTSAW-325 fix.

Best thing then is to create a simple example to demonstrate the issue and raise a jira.

Regards

Gary

Hi Gary,

Related to this topic, I have seen the issue for SOA:

https://bugzilla.redhat.com/show_bug.cgi?id=780990

which is not solved yet. As I understand this feature is not working yet. I'm right?

Thank you,

Laura

This bugzilla related to an incorrect URL being written to UDDI. A patch has been applied to trunk and the riftsaw-2.3.x branch, although there is also a workaround to simply turn off uddi support:

bpel.uddi.registration=false

bpel.uddi.lookup=false

in ${server.home}/server/${server.config}/deploy/riftsaw.sar/bpel.properties.

Regards

Gary

Hi Gary,

We have a similar issue. We tried the dyn partner quickstart with the workaround. Then how do we invoke the BPEL as web service?

Please help..

Thanks,

Ravi

Hi Ravi

Can you please clarify your issue - as this thread began discussing issues with dynamically assigning endpoint references, but has also touched on another issue.

From your description you mention trying the quickstart with the workaround, but have not indicated whether it worked for you or not. This example is about invoking an external web service based on a dynamically assigned URL - so your question is confusing in this context? Could you elaborate on what you are trying to do, and also what environment/versions you are using.

Regards

Gary

Hi Gary,

Thanks for your reply..

I am  currently using SOA Platform 5.2.0. I am trying to run the dynpartner quickstart example, but it is not assigning the url dynamically to the endpoint.

When I make

bpel.uddi.registration=false

bpel.uddi.lookup=false

in Bpel.properties file.

When I deploy  the bpel, the  wsdl is not registered in the uddi. Kindly tell me how to invoke the Bpel when set the above properties.

Similarly I tried with attached project to invoke the arithmetic operations dynamically based on the operation but unable to do it.

Thanks,

Ravi

Hi Ravi

Thanks for the clarification.

As mentioned in this thread, the problem with dynamic assignment (RIFTSAW-325) was fixed in 2.3.0.final which formed the basis of the BPEL support in SOA-P 5.2. However as described in the jira issue, a specific version of the jbossws-native stack was required as well as a patched version of the xalan.jar.

You will need to contact platform support to investigate why your specific case does not work on the platform - these forums are for issues related with the community project.

In terms of the properties - they simply bypass registering services (and looking them up) in UDDI. This simply means that when a BPEL process needs to invoke an external web service, it will use the soap address from the WSDL associated with that external service instead.

Regards

Gary