thanks for the confirmation, the http-jetty transport also supports the soap based URI, that is why it works. Actually, I recall now that defaulting transportId to a more neutral value was mainly about avoiding the confusing messages (where does soap-aware DestinationFactory come in in the first place ?) in case of JAX-RS frontends failing to get DestinationFactory located. Cheers, Sergey
On Mon, May 30, 2011 at 2:35 PM, Bruno Dusausoy <[email protected]> wrote: > On 05/30/2011 02:55 PM, Sergey Beryozkin wrote: >> >> Thanks...I'm wondering if explicitly adding a >> cxf-rt-transports-http-jetty dependency can help, that issue does not >> exist with the servlet transport being involved... >> Please, send me the test project if you can and I will look into it >> > > Bullseye ! > Indeed, when adding the dependency you've suggested it works equally well > for 2.3.3 and 2.3.4 ! > More interesting for you, it works *without* your workaround, no need to set > the transportId programmatically, even for 2.3.3. > > Thanks a lot. > > Regards. > > -- > Pensez environnement : limitez l'impression de ce mail. > Please don't print this e-mail unless you really need to. >
