apBindingFactory.addListener(SoapBindingFa
> > ctory.java:721)
> > at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:122)
> > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:263)
> > at org.apache.cxf.jaxws.EndpointImpl.publish(Endpo
: Tuesday, November 11, 2008 2:11 AM
To: Seumas Soltysik
Cc: dev@cxf.apache.org; Daniel Kulp
Subject: Re: JMS 1.0.2 support..
Hi Seumas,
could you post the configuration you used?
Greetings
Christian
Seumas Soltysik schrieb:
> I have just upgraded to CXF 2.1.3 and am running against an
-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2008 10:42 AM
To: Christian Schneider; dev@cxf.apache.org
Subject: JMS 1.0.2 support..
Christian,
The old JMS transport pretty much just used the JMS 1.0.2 API's so it
worked
with old versions of JMS providers and
org.apache.cxf.jaxws.spi.ProviderImpl.createAndPublishEndpoint(ProviderI
mpl.java:84)
at javax.xml.ws.Endpoint.publish(Endpoint.java:47)
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2008 10:42 AM
To: Christian Schneider; dev@cxf.apache.org
Subject: JMS 1.0.2 support..
Christian,
The old JMS
On Saturday 11 October 2008 3:34:52 am Christian Schneider wrote:
> Hi Dan,
>
> sounds reasonable to me. I have added the config element to address and
> set the default.
I think setting useJms11 to false for 2.0.x and 2.1.x probably makes sense for
compatibility sake. For 2.2 (trunk), it proba
Hi Dan,
sounds reasonable to me. I have added the config element to address and
set the default.
Greetings
Christian
Daniel Kulp schrieb:
Christian,
The old JMS transport pretty much just used the JMS 1.0.2 API's so it worked
with old versions of JMS providers and such. The new stuff
Christian,
The old JMS transport pretty much just used the JMS 1.0.2 API's so it worked
with old versions of JMS providers and such. The new stuff seems to default
to 1.1 which is causing issues.I see that if you use the new config, it's
settable. However, if you use the old wsdl based
