It depends if the component looks fine for you or not :)
Regards JB Guillaume Nodet wrote:
This looks more like a discussion thread rather than a vote thread, right ? I'll try to review the code tomorrow. On Wed, Sep 2, 2009 at 10:13, Jean-Baptiste Onofré <[email protected]> wrote:Hi all, I have completed a new version of the ServiceMix Exec component. This version includes WSDL support. It means that an Exec endpoint expose an abstract WSDL that can be used by a SOAP compliant front BC (such as HTTP or CXF-BC). The default Exec marshaler uses JAXB to marshal/unmarshal in/out messages. For example, you can expose directly an Exec endpoint using a HTTP one. The Exec xbean looks like: <exec:endpoint service="my:TestService" endpoint="exec"/> and the HTTP xbean looks like: <http:soap-consumer service="my:TestService" endpoint="http" targetService="my:TestService" targetEndpoint="exec" locationUri="http://0.0.0.0:8192/test/exec/"; useJbiWrapper="false"/> The HTTP endpoint generates a concrete WSDL using the porttypedef provided by the exec endpoint. The users can generate a SOAP envelope containing the exec request. I have updated the wiki doc of the exec endpoint to explain this: http://servicemix.apache.org/servicemix-exec.html The exec endpoint source code is here: http://svn.apache.org/repos/asf/servicemix/components/engines/servicemix-exec/trunk/ Any comment is welcome, feel free to raise Jira to add enhancement or change request. Thanks, Regards JB
