Basically the servicemix-drools is operating with MessageExchange objects. If they contain messages with xml content or even without any content it doesn't really matter.
What you are then doing inside your drools logic with such MessageExchange objects is a different thing. Regards Lars Am Dienstag 21 Oktober 2008 15:19:49 schrieb ObjectOrange: > So I can send any XML to this Service and it will work? > > Lukasz Dywicki (splatch) wrote: > > Hello, > > You don't need WSDL to use drools. You can specify WSDL resource for http > > endpoints (soap-provider, soap-consumer). For this please look > > http://servicemix.apache.org/servicemix-http.html page. Drools is only > > buisness rules processor and it don't create WSDL from rules definition. > > > > Regards, > > Luke > > > > ObjectOrange wrote: > >> Thanks Luke! Is there also a WSDL somewhere? > >> > >> Lukasz Dywicki (splatch) wrote: > >>> Hello, > >>> Try use maven archetypes from tooling package: > >>> mvn archetype:create \ > >>> -DarchetypeGroupId=org.apache.servicemix.tooling \ > >>> -DarchetypeArtifactId=servicemix-drools-service-unit \ > >>> -DgroupId=com.mycompany.myproduct \ > >>> -DartifactId=mycomponent.artifact > >>> > >>> This should create correct service unit. Next steep is to use > >>> servicemix-http service unit: > >>> mvn archetype:create \ > >>> -DarchetypeGroupId=org.apache.servicemix.tooling \ > >>> -DarchetypeArtifactId=servicemix-http-consumer-service-unit \ > >>> -DgroupId=com.mycompany.myproduct \ > >>> -DartifactId=mycomponent.artifact > >>> > >>> In xbean.xml for http component you should use the same namespace and > >>> name for service like in drools xbean.xml. > >>> > >>> Regards, > >>> Luke > >>> > >>> ObjectOrange wrote: > >>>> Has anyone attempted to call the Drools SE using HTTP/SOAP? I couldn't > >>>> find a tutorial on the site.
