Community
Participate
Working Groups
[ https://issues.jboss.org/browse/RIFTSAW-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Yu updated RIFTSAW-353: ---------------------------- Fix Version/s: 3.0.0.M2 (was: 3.0.0.M1) > Support invocation of RESTful services from BPEL (backport Ode 2 extensions to 1.x when available) > -------------------------------------------------------------------------------------------------- > > Key: RIFTSAW-353 > URL: https://issues.jboss.org/browse/RIFTSAW-353 > Project: RiftSaw > Issue Type: Feature Request > Components: ODE > Affects Versions: 2.2.0.Final > Reporter: Robert (Bob) Brodt > Assignee: Gary Brown > Priority: Optional > Fix For: 3.0.0.M2 > > > Transcript of email conversation: > Hi Bob and Jeff > Actually part of the issue is the transport (although there may be engine issues to consider aswell). JBossWS-CXF 3.4.0 supports CXF 2.3.1, which supports JAX-RS 1.1 - so from a transport perspective, we would need to investigate how to switch between the two APIs, and whether BPEL processes could be used to 'provider' a RESTful interface. > @Bob, could you create a feature request for this, as the focus for any future discussion - and then Jeff if you could add any relevant info to it. > Regards > Gary > ----- Original Message ----- > > Hi Bob > > > > I've cc'd Jeff as he works more with the ODE community, but I believe > > the RESTful work was targetted towards ODE2, which has now become an > > experimental branch. There is supposed to be a call with the ODE team > > in the near future, one of the topics is backporting features from > > ODE2 back to the 1.x based trunk, so we could see if there are any > > specific plans. > > > > Regards > > Gary > > > > ----- Original Message ----- > > > Hi Gary, > > > > > > Have you had any success with invoking REST services from BPEL? I've > > > been working through the example here > > > http://www.w3.org/TR/wsdl#_http > > > without much luck. Also, I see that ODE has proposed REST extensions > > > (http://ode.apache.org/restful-bpel-part-i.html) - any idea what the > > > status of that is? > > > > > > Thanks! > > > > > > _______________________________________ > > > Robert ("Bob") Brodt > > > Senior Software Engineer, JBoss Riftsaw > > > JBoss by Red Hat -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
I think this is more a "runtime" feature for ODE or EasyBPEL or Orchestra. What do you think should be added to the tooling?
The proposed ODE extension will require UI support for the "method" attribute of the Invoke element. See http://ode.apache.org/restful-bpel-part-i.html Any thoughts about whether we should or should not support this extension?
The main issue is that this new attribute will not conform to the BPEL XSD and adding it to the editor can make it create BPEL files that cannot be consumed by other BPEL tools. IMHO, that's a good idea to support this, but with a very light coupling. So that there may be need to add new extension points. More generally, I don't know what is the strategy of ODE. Do you think that the new trend in ODE is to add support for new attributes, to extend the standard, and then to not respect the standard?
Hi, > Any thoughts about whether we should or should not support this extension? Given its behavior, it seems more like an extended activity to me. It would be better to have another name for it at design time and rename it when exporting it for ODE. It's far from being perfect, but the approach taken by ODE is ambiguous.
I agree, this should be an extension activity for which we already have extension points defined. I'm not sure what the ODE community's plans are regarding a standard for RESTful service support, but I think it's a feature that should have been addressed by the standard.
> I'm not sure what the ODE community's plans are regarding a standard for > RESTful service support, but I think it's a feature that should have been > addressed by the standard. We may suggest in ODE's bug tracker to define an alias for their activity to invoke RESTful services. Those who will have created BPEL process with this special "invoke" will see it supported and new developers will be able to use the alias directly (e.g. invoke-rest). It will then be easy to support it in the designer.
"Version" must be the product version number to which this bug applies - it can't be a "future" version.
