Hi

I've tried to make a simple http -> pojo bean connection to no avail, using
the JBI deployment scheme. Basically, I have one SA with two SUs: 

SU1 contains the Echo POJO from servicemix.apache.org/servicemix-bean.html,
and the jbi.xml file is :
<jbi xmlns="..." version="1.0">
  <services binding-component="false" xmlns:tns="ServiceURI">
    <consumes service-name="tns:ServiceBean" endpoint-name="bean"/>
  </services>
</jbi>

and xbean.xml is:
<beans xmlns:tns="ServiceURI"
       xmlns:bean="...">
  <bean:endpoint service="tns:ServiceBean" endpoint="bean"
beanName="serviceBean"/>
  <bean id="serviceBean" class="test.Echo"/>
</beans>

SU2 contains only the XML files. jbi.xml is
<jbi xmlns="..." version="1.0">
  <services binding-component="false" xmlns:tns="ServiceURI">
    <consumes service-name="tns:ServiceHTTP" endpoint-name="http"/>
  </services>
</jbi>

and xbeanx.xml is
<beans xmlns:http="..."
       xmlns:tns="ServiceURI"
       >
  <http:endpoint service="tns:ServiceHTTP"
                 endpoint="http"
                 targetService ="tns:ServiceBean"
                 targetEndpoint ="bean"
                 role="consumer" 
                 locationURI="http:// localhost:8192/examples/Test"
                 defaultMep="(...)/in-out"
                 soap="true" />
</beans>

(I have removed the URLs of the namespaces because of the sdpam filter)

The SA contains both SUs, each of them deployed on the appropriate component
(SU1 on servicemix-bean, SU2 on servicemix-http)

Everything deploys fine, no errors anywhere, but then when I try to access
the above URL (locationURI) or the above URL plus ?wsdl, I get a 404 and no
errors or traces or other hints anywhere. Changing the log level to DEBUG
I've seen jetty saying that "chain = null", but I don't exactly understand
why.

Any help is welcome. Thanks in advance!
-- 
View this message in context: 
http://www.nabble.com/%3A---Can%27t-get-a-simple-connection-to-work-tp14903524s12049p14903524.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to