How do your two service.xml files look like? My guess would be that the problem is from there. You can find them in web-inf/services/muse/meta-inf.
Zhang, Jin-Zhai wrote: > > > Hi, > Now I have two muse notification producer war files in one ear and > the war files are the muse 2.2.0 wsn-producer sample with minor > modifications. > If one wsn-consumer want to subscribe the NotificationProducerA, then > it found NotificationProducerB and got soapfault. > > <soap:Fault> > <soap:Code> > <soap:Value>soap:Sender</soap:Value> > <soap:Subcode > xmlns:wsa="http://www.w3.org/2005/08/addressing";> > <soap:Value>wsa:DestinationUnreachable</soap:Value> > </soap:Subcode> > </soap:Code> > <soap:Reason> > <soap:Text>[ID = 'DestinationUnreachable'] There is no > resource available at the given EPR: > > <wsa:EndpointReference > xmlns:wsa="http://www.w3.org/2005/08/addressing"> > > <wsa:Address>http://localhost:8080/wsn-producer_a/services/NotificationP > roducerA</wsa:Address> > </wsa:EndpointReference> > > The existing EPRs hosted by this endpoint are: > > <wsa:EndpointReference > xmlns:wsa="http://www.w3.org/2005/08/addressing"> > <wsa:ReferenceParameters > xmlns:wsa="http://www.w3.org/2005/08/addressing"/> > > <wsa:Address>http://localhost:8080/wsn-producer_b/services/Notific > ationProducerB</wsa:Address> > </wsa:EndpointReference> > </soap:Text> > </soap:Reason> > </soap:Fault> > > Can you help me understand how to configure these two wsn producers to > avoid this fault? > By the way, if take one wsn producer from the ear, then the remained > one Works fine. > > The difference between the current configuration of these two wsn > producers is simple: > > 1. the war file name is wsn-producer_a.war and wsn-producer_b.war. > > 2. In muse.xml of the NotificationProducer a, > <resource-type use-router-persistence="true"> > <context-path>NotificationProducerA</context-path> > <wsdl> > <wsdl-file>wsdl/WsResource.wsdl</wsdl-file> > > <wsdl-port-type>wsn_a:WsResourcePortType</wsdl-port-type> > </wsdl> > ..... > </resource-type> > > In muse.xml of the NotificationProducer b, > <resource-type use-router-persistence="true"> > <context-path>NotificationProducerB</context-path> > <wsdl> > <wsdl-file>wsdl/WsResource.wsdl</wsdl-file> > > <wsdl-port-type>wsn_b:WsResourcePortType</wsdl-port-type> > </wsdl> > ..... > </resource-type> > > 3. the router-entries is NotificationProducerA/resource-instance-1.xml > and NotificationProducerB/resource-instance-2.xml, > and the contents of these two resource-instance xml file are > identical: > <?xml version="1.0" encoding="UTF-8"?> <wsa:ReferenceParameters > xmlns:wsa="http://www.w3.org/2005/08/addressing"/> > > > > Justin ZHANG > CMEP (Communication, Media, Entertainment, and Public sector) HP Global > Delivery China Center (GDCC) > Tel: +86 21 3889 7219 > Email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/One-endpoint-but-two-wsn-producer-EPRs-tf4134220.html#a11762890 Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
