There currently is a command execution stateless session bean in the source tree. So we already have a starting point for this EJB. This is being used by the Jms command executor but could easily be exposed as a web service.
The command object would have to have a special serializer because it is a complex XML type. If we create a sample Java client with the serializer thrown in it should not be that hard for our clients to get up to speed using it.
Perhaps, someone could then create a sample .NET or other language client from that model.
Thanks, I did not look into this for the last few months . For this 'customer' I'll try using axis2 with xmlbeans (their, no rather mine current preference) but it has to wait for at least two weeks since I'm off playing golf in France for 5 days.
The XML Schema allows for deriving types from other types. Java-XML binding frameworks such as JAXB match type derivation with class inheritance. Therefore, the Command service should not be hard to expose.
Regarding invocation, be careful, don't treat web services as RMI. For a document-oriented service, the notion of "parameters" has no meaning. We must devise a way to assemble an XML document from the process variables.
I remember discussing this topic some time ago (in the sourceforge forums!). Back then I rounded up the conclusions and put together a paper. I just attached it to a Wiki page. We can pick up from there.
please also consider the new JBoss WS stack: http://www.jboss.org/wiki/Wiki.jsp?page=JBossWS
i know heard they had compatibility problems with axis and therefor started this new project. if you want more background, you can ask on the jboss ws forums. some very competent people there that know much better then i why they needed to write a separate impl.
alternatively, i also like the approach that alex took with bpel: using jee 1.4 web services so that your solution becomes portablel across app servers.
I don't know what is the best solution, but at DiSiD we are developing BPM applications using jBPM but without using EJBs, our applications are the most portable applications because they can be deployed in an application server and in a servlet container like Tomcat.
Exposing the jBPM API as webservices with EJBs signifies to limit the portability that the jBPM has. I don't know if JBoss offers another way to implement WS as another frameworks does (like Springframework) but it could be a good feature to not limit the use of the jBPM-WS to applications that must be deployed on application servers.
I would, but this 'customer' is *not* running JBoss, but a plain tomcat server and currenty not willing to migrate (yet). If JBoss-WS runs on Tomcat, I'll have a look, but if it does not run (out of the box) on tomcat.
I'll have a look next week
Have a nice holiday with the familiy
it does run outside of jboss. i remember that was recently announced. you may want to check which exact version that supports this on
or ask it on
I like it the other way around, first ask and only if someone posts a RT..... I'll go and have a look in the wiki/docs/....
You didn't see the answers yet that Thomas Diesler dares to throw at guys who did not read the smart questions manual I presume? ;-)
No I did not.... Now you made me scared to even try to start using JBossWS. I hate forum guys.... They are the biggest jackasses ever to populate the world.
Sorry, should have added a ;-) to this last post. I do not want people to take this last remark to seriously
Sounds like Koen needs a holiday, he is getting delirious or maybe I should just kick him of this forum for verbally abusing the moderator
shhoooooot I did it. I FIRST searched the JBossWS forum. The second topic I found was
which indicates a small packaging issue, but more important, refers to http://labs.jboss.com/portal/jbossws/user-guide/en/html/installation.html#install-tomcat so I am probably going to use jbossWS but....
We've run into an issue (not jBPM/JBoss related) where a customer already had axis in its environment and was relying on specific functionality and another stack could not be run concurrently.... maybe an issue to keep in mind