-
30. Re: SwitchYard BPEL to Bean Service routing question
mauroa85 Apr 11, 2014 1:40 PM (in response to adamdva)Hi,
I am hiiting in the same wall , run time error
(have a simple BPEL recive-> assign -> invoke -> assing ->response )
The bpel Process recives the values but then it seams to me that it goes on wrong direction.
The INVOKE does not call the partnerLink role it is supose too (wsdl imported and is defined as reference),
The behave in the message trace seams to Hit at the Invoke and then it Times out
(i have a felling that ODE DD file is not working the way is supose too it should defines the BPEL gateways where data will flow, But something is redirecting data in wrong ways to a dead end)
IMO ODE DD file (RIFT SAW legacy) is needed to the BPEL as services and references are in SY,
it look like it only works in the same SY domain when is needed to call external (References of SY )
it gets Lost connections is not made... ODE DD and SY they should look and use the same road to pass information the problem is they dont ride along and dont share the road.
i leave my project here and the txt of my message trace.
(i dont know if im doing something else wrong, my gide lines here was the example switchyard-quickstart-bpel-service-xts-subordinate-wsba-bpel
trying atomic transactions and the server has the config with xtc file)
Hope this helps in improving futher SY tools.
-
BSY.zip 32.6 KB
-
MessageTrace.txt.zip 6.2 KB
-
-
31. Re: SwitchYard BPEL to Bean Service routing question
objectiser Apr 14, 2014 4:34 AM (in response to mauroa85)The issue of deploy.xml vs switchyard.xml is the subject of this jira: https://issues.jboss.org/browse/SWITCHYARD-1283
Although the duplication in the tooling is unwanted, the ODE runtime will still require this information - so at some point in the future it is possible that the deploy.xml may be generated from switchyard.xml.
Regards
Gary
-
32. Re: SwitchYard BPEL to Bean Service routing question
mauroa85 Apr 14, 2014 5:55 AM (in response to objectiser)Garry Brown,
Is there any work arround or something else to fix this problem?
-
33. Re: SwitchYard BPEL to Bean Service routing question
objectiser Apr 14, 2014 6:45 AM (in response to mauroa85)Hi Mauro
No, only solution at present is to ensure the details in the deploy.xml match those in the switchyard.xml.
Best thing would be to 'watch' the referenced jira for any progress. Rob mentions a separate jira for tackling this specific issue, but couldn't find it - possibly he can provide a reference to it.
Regards
Gary
-
34. Re: SwitchYard BPEL to Bean Service routing question
mauroa85 Apr 14, 2014 11:23 AM (in response to objectiser)hi,
thanks for your help.
I realy need to create a working BPEL 'watch' jira could be a solution
but in the mean while i need to have a working BPEL so,
Is Rift Saw (alone) a realible working BPEL tool, since other options that SY offers like BPM is not compatible with my bussiness process
and because we have already a SOA BPEL implemented (oracle) that we pretend to migrate.
and if yes witch version should i pick ?
Can i use SY BPEL as a 'single mode' or i have to install and old RIFTSAW version (the previous one 2.X) ?
Thanks.
-
35. Re: SwitchYard BPEL to Bean Service routing question
objectiser Apr 14, 2014 11:34 AM (in response to mauroa85)Hi Mauro
Not sure what you mean by RiftSaw (alone)? RiftSaw is now only supported as a component within SwitchYard. Previous versions of RiftSaw only run on JBoss AS 5.x.
You previously mentioned basing your example on the XTS quickstart. The XTS work is not properly supported at the moment, it is experimental work - so these are not good examples to base your examples upon.
If you are looking for an example where one BPEL process invokes another, then the bpel_loan_approval example is a better one to try.
Regards
Gary