If you have turned off soap, you need to make sure the defaultMep attriebute on your http endpoint is set to InOnly, else an InOut mep will be send and cause the exception you have seen.
On 3/7/07, Chilson <[EMAIL PROTECTED]> wrote:
I'm using the Wsn-Http-Binding example, unchanged except for turning SOAP off. For the notification message, I'm just trying the one off of the wsn servicemix page. POST /Broker/ HTTP/1.1 Host: localhost:8192 Content-Type: text/xml; charset="utf-8" Content-Length: 210 <wsnt:Notify xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2 "><wsnt:NotificationMessage><wsnt:Topic>myTopic</wsnt:Topic><wsnt:Message><hello>world</hello></wsnt:Message></wsnt:NotificationMessage></wsnt:Notify> gnodet wrote: > > > Yeah, you're quite right, the problem comes from a MEP mismatch. > I guess that the servicemix-http BC sends an InOut MEP, but the operation > invoked is an InOnly MEP. This should be checked earlier and reported > with > a more understandable error (can you raise a JIRA please ?). > > Not sure how you configured your HTTP endpoint, but the problem may come > from the fact that the WSDL is not correctly recognized, so that the > informations > can not be retrieved. Did you use the one from the example in the > distribution ? > What request did you send ? > > -- > Cheers, > Guillaume Nodet > ------------------------ > Architect, LogicBlaze (http://www.logicblaze.com/) > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9360759 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
