Ah, good point. it explains while adding the soapAction attribute did not change anything. I think it comes down to how you create your suscription. What message did you send ?
On Thu, Apr 17, 2008 at 10:30 AM, yvdl <[EMAIL PROTECTED]> wrote: > > Hi Guillaume, > > I must also mention that: > > the behaviour was the same (no SOAPAction header in the HTTP message > (notification) sent by the SMX-wsn broker to the subscriber (the BPEL > process) before I added a "provider" endpoint in the xbean.xml > configuration > file. > > So I think that the problem comes from the fact that for some reason the > SMX-http does not "match" or "recognize" the endpoint defined in the > xbean.xml file. > > regards > > YVDL > > > gnodet wrote: > > > > I think you have two ways to debug such a problem: > > * remote debugging: before launching servicemix, just set the > > SERVICEMIX_DEBUG=true environment variable, then you can attach to the > > process from your IDE and debug. I would put a breakpoint in > > servicemix-http, in the > > org.apache.servicemix.http.processors.ProviderProcessor#process() method > > * create a simple junit test so that someone can reproduce and debug > the > > problem > > > > On Wed, Apr 16, 2008 at 3:50 PM, yvdl <[EMAIL PROTECTED]> > > wrote: > > > > > > -- > > Cheers, > > Guillaume Nodet > > ------------------------ > > Blog: http://gnodet.blogspot.com/ > > > > > > -- > View this message in context: > http://www.nabble.com/SM-WSN2005%3A-Broker-does-not-set-SOAPAction-field-value-tp16583522p16741183.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
