If you don't use the hot deployer (using ant for example), components are not automatically started after being installed (this is the JBI spec). So when you deploy your SA, you may encouter this error. Just start the component from the jmx console (for example) should be fine, so you can then deploy and start your SA.
On 12/4/06, bernulfiskus <[EMAIL PROTECTED]> wrote:
I tried to deploy the service assembly, then i got the following error although the target webservice is correctly running on a Tomcat-Server: [INFO] Unable to deploy project, Error accessing ServiceMix administration <?xml version="1.0" encoding="UTF-8"?> <jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message"; version="1.0"> <jbi-task-result> <frmwk-task-result> <frmwk-task-result-details> <task-result-details> <task-id>deploy</task-id> <task-result>FAILED</task-result> <message-type>ERROR</message-type> <task-status-msg> <msg-loc-info> <loc-token/> <loc-message>Target component servicemix-http for service unit ZDEHttpProvider is not started</loc-message> </msg-loc-info> </task-status-msg> </task-result-details> </frmwk-task-result-details> </frmwk-task-result> </jbi-task-result> </jbi-task> Configuration Http-Provider: <beans xmlns:http="http://servicemix.apache.org/http/1.0"; xmlns:stiwa="http://stiwa.com";> <http:endpoint service="stiwa:ZDEService" endpoint="soap" role="provider" locationURI="http://localhost/ZDEWeb/services/ZDEService/"; defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; soap="true" /> </beans> Any Idea? Bernie gnodet wrote: > > You need to disable the jbi descriptor generation for the SU: > > <plugin> > <groupId>org.apache.servicemix.tooling</groupId> > <artifactId>jbi-maven-plugin</artifactId> > <version>${servicemix-version}</version> > <extensions>true</extensions> > <configuration> > <generateJbiDescriptor>false</generateJbiDescriptor> > </configuration> > </plugin> > > > On 12/1/06, bernulfiskus <[EMAIL PROTECTED]> wrote: >> >> Thank you for the info. >> >> Unfortunately the component install fails... >> The #context-beandefinition is missing... where do define? >> >> [INFO] Created Service Unit Analyzer >> [EMAIL PROTECTED] >> [ERROR] mojo-execute : jbi:generate-jbi-service-unit-descriptor >> Diagnosis: Failed to generate jbi.xml >> FATAL ERROR: Error executing Maven for a project >> [ERROR] project-execute : >> com.mycompany:ZDEJsrService:jbi-service-unit:1.0-SNAPSHOT ( >> task-segment: >> [install] ) >> Diagnosis: Failed to generate jbi.xml >> FATAL ERROR: Error executing Maven for a project >> [INFO] >> ---------------------------------------------------------------------------- >> [INFO] BUILD SUCCESSFUL >> [INFO] >> ---------------------------------------------------------------------------- >> [INFO] Total time: 34 second >> [INFO] Finished at: Fri Dec 01 07:42:31 CET 2006 >> [INFO] Memory 6M/29M >> [INFO] >> ---------------------------------------------------------------------------- >> [INFO] Error for project: An example JSR-181 Service Unit (during >> install) >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Failed to generate jbi.xml >> >> Embedded error: Unable to generate service unit descriptor! >> No bean named 'context' is defined >> [INFO] >> ------------------------------------------------------------------------ >> [DEBUG] Trace Failed to generate jbi.xml >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] reactor-execute : C:\Programme\lb_eclipse\workspace\ZDEJsrService >> FATAL ERROR: Error executing Maven for a project >> [INFO] BUILD ERRORS >> >> >> >> >> gnodet wrote: >> > >> > The best is to use a proxy and inject it on your >> > service implementation. >> > >> > <jsr181:endpoint wsdlResource="classpath:service.wsdl"> >> > <jsr181:pojo> >> > <bean class="MyWebserviceImpl"> >> > <property name="webService"> >> > <jsr181:proxy service="qname target" context="#context" >> > type="java class name" /> >> > </property> >> > </bean> >> > </jsr181:pojo> >> > </jsr181:endpoint> >> > >> > The type attribute is the name of the java interface generated >> > representing the >> > target web service. It should also be the type of the property on the >> > injected pojo . >> > >> > The service attribute is the qname of the target JBI endpoint (the http >> > provider >> > endpoint). >> > >> > The context="#context" attribute is to be able to retrieve a >> > ComponentContext. >> > This only works inside a SU deployed onto the jsr181 component. >> > If you use a single servicemix configuration file, you can use a >> > reference to the JBI >> > container instead: container="#jbi". >> > >> > >> > On 11/30/06, bernulfiskus <[EMAIL PROTECTED]> wrote: >> >> >> >> How can I delegate from the jsr component (through the NMR) to the >> >> HttpProvider BC? Which modifications are necessary in the xbean.xml >> and >> >> WebServiceImpl to call the HttpEndpoint? >> >> >> >> <beans xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0";> >> >> <classpath> >> >> <location>.</location> >> >> </classpath> >> >> <jsr181:endpoint pojoClass="MyWebserviceImpl" >> >> wsdlResource="classpath:service.wsdl" /> >> >> </beans> >> >> >> >> Please help ;-) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> gnodet wrote: >> >> > >> >> > Right. >> >> > Be aware that some problems were fixed recently, >> >> > so you should try a nightly distribution of 3.1, or build >> >> > from svn head. >> >> > >> >> > On 11/29/06, bernulfiskus <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> ;-) >> >> >> >> >> >> To call a webservice via wsdl-generated proxy classes I think a >> >> >> jsr181Wsdl-Service Component should be the best choice, right? >> >> >> >> >> >> jsr181 -> http-bc -> webservice system 2 >> >> >> >> >> >> Bernie >> >> >> >> >> >> >> >> >> >> >> >> gnodet wrote: >> >> >> > >> >> >> > Web service calls, either as a client or a server, can be >> achieved >> >> by >> >> >> > using >> >> >> > the servicemix-http component. In between, you can use whatever >> JBI >> >> >> > component you want, from bpel engine, servicemix-jsr181, etc ... >> >> >> > >> >> >> > On 11/29/06, bernulfiskus <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> >> >> Hi! >> >> >> >> >> >> >> >> What's the best way to integrate webservices to the esb? >> >> >> >> >> >> >> >> situation: System 1 calls a webservice from System 2 >> >> >> >> System 1, Client (C#) -> Webservice-Call -> ESB -> >> Webservice-Call >> >> -> >> >> >> >> System >> >> >> >> 2, Server (java) >> >> >> >> >> >> >> >> Bernie >> >> >> >> -- >> >> >> >> View this message in context: >> >> >> >> >> >> >> >> >> >> http://www.nabble.com/Best-way-to-integrate-webservices-tf2723771s12049.html#a7595782 >> >> >> >> Sent from the ServiceMix - User mailing list archive at >> Nabble.com. >> >> >> >> >> >> >> >> >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > Cheers, >> >> >> > Guillaume Nodet >> >> >> > >> >> >> > >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> http://www.nabble.com/Best-way-to-integrate-webservices-tf2723771s12049.html#a7597807 >> >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> > >> >> > >> >> > -- >> >> > Cheers, >> >> > Guillaume Nodet >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Best-way-to-integrate-webservices-tf2723771s12049.html#a7614668 >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> > -- >> > Cheers, >> > Guillaume Nodet >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Best-way-to-integrate-webservices-tf2723771s12049.html#a7634267 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/Best-way-to-integrate-webservices-tf2723771s12049.html#a7674747 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
