I fixed a bug preventing the WSDL to be exposed.
I also added a simple demo showing how to expose the
WS-NotificationBroker over http/soap.
All this should be available in next nightly snapshot.
Cheers,
Guillaume Nodet
On 5/1/06, frederic.dreyfus <[EMAIL PROTECTED]> wrote:
I tried your example but it did not work.
Actually, I have a simple WSNComponent declared in my servicemix.xml file :
<sm:activationSpec>
<sm:component>
<bean class="org.apache.servicemix.wsn.spring.WSNSpringComponent">
<property name="connectionFactory" ref="connectionFactory" />
</bean>
</sm:component>
</sm:activationSpec>
Then I deploy a JBI component into the deploy directory. This JBI component
contains the soap binding :
<http:endpoint service="wsn:NotificationBroker"
endpoint="http-binding"
targetService="wsn:NotificationBroker"
role="consumer"
locationURI="http://localhost:8192/Broker/";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
/>
The component seems to be successfully deployed (I get it in the services
list), but when I click on the service link, the wsdl is still not
retrieved.
I tried adding the wsdlResource property to the bean, but then there are
import problems.
Please help, I really need to make this work.
Thanks very much,
Fred
--
View this message in context:
http://www.nabble.com/Send-a-remote-WS-Notification-subscription-t1524232.html#a4172227
Sent from the ServiceMix - User forum at Nabble.com.
