You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Benson Margulies <bi...@gmail.com> on 2010/09/19 21:11:29 UTC
Java first and the new JMS config universe ...
I'm trying out the new JMS in the Java-first case, and I've hit my
first pothole.
I'm going to commit the sample in the state that gets this error.
Object implementor = new HelloWorldImpl();
JaxWsServerFactoryBean svrFactory = new JaxWsServerFactoryBean();
svrFactory.setServiceClass(HelloWorld.class);
svrFactory.setTransportId(JMSSpecConstants.SOAP_JMS_SPECIFICIATION_TRANSPORTID);
svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLive=1000");
svrFactory.setServiceBean(implementor);
svrFactory.create();
INFO: Setting the server's publish address to be
jms:queue:test.cxf.jmstransport.queue?timeToLive=1000
Exception in thread "main" java.lang.IllegalArgumentException: Target
ConnectionFactory must not be null
at org.springframework.util.Assert.notNull(Assert.java:112)
at org.springframework.jms.connection.SingleConnectionFactory.<init>(SingleConnectionFactory.java:130)
at org.apache.cxf.transport.jms.JMSConfiguration.getOrCreateWrappedConnectionFactory(JMSConfiguration.java:441)
at org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:104)
at org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:111)
at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48)
at org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:181)
at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:835)
at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127)
at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:186)
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183)
at demo.server.ServerJMS.main(ServerJMS.java:63)
Re: Java first and the new JMS config universe ...
Posted by Daniel Kulp <dk...@apache.org>.
Nice job guys. Glad to see it all working. :-)
Next question:
Should the original page that Benson stole the demo from:
http://cxf.apache.org/docs/jax-ws-java-first-with-jms-transport.html
be updated with the new demo or should we wait until after 2.3 is released?
Dan
On Monday 20 September 2010 7:21:56 am Benson Margulies wrote:
> Thanks, all that makes sense.
>
> On Sun, Sep 19, 2010 at 11:47 PM, Willem Jiang <wi...@gmail.com>
wrote:
> > On 9/20/10 8:00 AM, Benson Margulies wrote:
> >> That doesn't change the strange 'no endpoint' error. Do you have any
> >> hints for how to track this down, or do you JMS hackers want to pick
> >> up from here?
> >
> > The no endpoint error is caused by you set a wrong PortName :)
> > As the SEI doesn't have the @WebService annotation, CXF will try to setup
> > PortName which is based on the package and class name.
> >
> > After resolve this issue, I caught another snail which the Soap Over JMS
> > namespace is missed from the DEFAULT_NAMESPACES of SoapBindingFactory.
> >
> > Now the JMSClient is working like a charm.
> >
> > BTW, I don't think we need the ClientHTTP.java and ServerHTTP.java any
> > more, so I'm planing to remove them.
> >
> > Willem
> >
> >> On Sun, Sep 19, 2010 at 7:32 PM, Daniel Kulp<dk...@apache.org> wrote:
> >>> On Sunday 19 September 2010 7:20:12 pm Benson Margulies wrote:
> >>>> Or, perhaps you prefer to answer this question:
> >>>>
> >>>> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
> >>>> JMS_ENDPOINT_URI);
> >>>>
> >>>> looks wrong. But what should I pass? What is the binding ID for
> >>>> SOAP/JMS?
> >>>
> >>> I THINK you could use either of the SOAP id's:
> >>>
> >>> http://schemas.xmlsoap.org/wsdl/soap/
> >>> http://schemas.xmlsoap.org/wsdl/soap12/
> >>>
> >>> depending on what version you want.
> >>>
> >>>
> >>> Dan
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: Java first and the new JMS config universe ...
Posted by Benson Margulies <bi...@gmail.com>.
Thanks, all that makes sense.
On Sun, Sep 19, 2010 at 11:47 PM, Willem Jiang <wi...@gmail.com> wrote:
> On 9/20/10 8:00 AM, Benson Margulies wrote:
>>
>> That doesn't change the strange 'no endpoint' error. Do you have any
>> hints for how to track this down, or do you JMS hackers want to pick
>> up from here?
>
> The no endpoint error is caused by you set a wrong PortName :)
> As the SEI doesn't have the @WebService annotation, CXF will try to setup
> PortName which is based on the package and class name.
>
> After resolve this issue, I caught another snail which the Soap Over JMS
> namespace is missed from the DEFAULT_NAMESPACES of SoapBindingFactory.
>
> Now the JMSClient is working like a charm.
>
> BTW, I don't think we need the ClientHTTP.java and ServerHTTP.java any more,
> so I'm planing to remove them.
>
> Willem
>>
>> On Sun, Sep 19, 2010 at 7:32 PM, Daniel Kulp<dk...@apache.org> wrote:
>>>
>>> On Sunday 19 September 2010 7:20:12 pm Benson Margulies wrote:
>>>>
>>>> Or, perhaps you prefer to answer this question:
>>>>
>>>> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
>>>> JMS_ENDPOINT_URI);
>>>>
>>>> looks wrong. But what should I pass? What is the binding ID for
>>>> SOAP/JMS?
>>>
>>> I THINK you could use either of the SOAP id's:
>>>
>>> http://schemas.xmlsoap.org/wsdl/soap/
>>> http://schemas.xmlsoap.org/wsdl/soap12/
>>>
>>> depending on what version you want.
>>>
>>>
>>> Dan
>>>
>
Re: Java first and the new JMS config universe ...
Posted by Willem Jiang <wi...@gmail.com>.
On 9/20/10 8:00 AM, Benson Margulies wrote:
> That doesn't change the strange 'no endpoint' error. Do you have any
> hints for how to track this down, or do you JMS hackers want to pick
> up from here?
The no endpoint error is caused by you set a wrong PortName :)
As the SEI doesn't have the @WebService annotation, CXF will try to
setup PortName which is based on the package and class name.
After resolve this issue, I caught another snail which the Soap Over JMS
namespace is missed from the DEFAULT_NAMESPACES of SoapBindingFactory.
Now the JMSClient is working like a charm.
BTW, I don't think we need the ClientHTTP.java and ServerHTTP.java any
more, so I'm planing to remove them.
Willem
>
> On Sun, Sep 19, 2010 at 7:32 PM, Daniel Kulp<dk...@apache.org> wrote:
>> On Sunday 19 September 2010 7:20:12 pm Benson Margulies wrote:
>>> Or, perhaps you prefer to answer this question:
>>>
>>> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
>>> JMS_ENDPOINT_URI);
>>>
>>> looks wrong. But what should I pass? What is the binding ID for SOAP/JMS?
>>
>> I THINK you could use either of the SOAP id's:
>>
>> http://schemas.xmlsoap.org/wsdl/soap/
>> http://schemas.xmlsoap.org/wsdl/soap12/
>>
>> depending on what version you want.
>>
>>
>> Dan
>>
Re: Java first and the new JMS config universe ...
Posted by Benson Margulies <bi...@gmail.com>.
That doesn't change the strange 'no endpoint' error. Do you have any
hints for how to track this down, or do you JMS hackers want to pick
up from here?
On Sun, Sep 19, 2010 at 7:32 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Sunday 19 September 2010 7:20:12 pm Benson Margulies wrote:
>> Or, perhaps you prefer to answer this question:
>>
>> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
>> JMS_ENDPOINT_URI);
>>
>> looks wrong. But what should I pass? What is the binding ID for SOAP/JMS?
>
> I THINK you could use either of the SOAP id's:
>
> http://schemas.xmlsoap.org/wsdl/soap/
> http://schemas.xmlsoap.org/wsdl/soap12/
>
> depending on what version you want.
>
>
> Dan
>
>
>
>>
>> On Sun, Sep 19, 2010 at 6:18 PM, Christian Schneider
>>
>> <ch...@die-schneider.net> wrote:
>> > Is that the full stack trace? Some times could not send message hides an
>> > exception deeper down the trace.
>> > For example if there is no listener you get could not send message but
>> > deeper in the stack you see timeout waiting
>> > for response or something like this.
>> >
>> > Best Regards
>> >
>> > Christian
>> >
>> > Am 19.09.2010 22:59, schrieb Benson Margulies:
>> >> I've got everything working except using the JAX-WS Client API to
>> >> create a client.
>> >>
>> >> The code below blows up. Do I need a JMS binding ID?
>> >>
>> >> org.apache.cxf.interceptor.Fault: Could not send Message.
>> >> at
>> >> org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(Messag
>> >> eSenderInterceptor.java:48) at
>> >> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorC
>> >> hain.java:247) at
>> >> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516) at
>> >> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313) at
>> >> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265) at
>> >> org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
>> >> at
>> >> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
>> >> at $Proxy34.sayHi(Unknown Source)
>> >> at demo.client.ClientJMS.main(ClientJMS.java:61)
>> >>
>> >> private static HelloWorld createClientJaxWs() {
>> >> Service service = Service.create(SERVICE_QNAME);
>> >> // Add a port to the Service
>> >> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
>> >> JMS_ENDPOINT_URI);
>> >> return service.getPort(HelloWorld.class);
>> >> }
>> >>
>> >>
>> >>
>> >> On Sun, Sep 19, 2010 at 3:48 PM, Christian Schneider
>> >>
>> >> <ch...@die-schneider.net> wrote:
>> >>> Hi Benson,
>> >>> the important question is: Where do you set the connection factory. The
>> >>> code
>> >>> snippet you provided does not set one.
>> >>>
>> >>> Regards
>> >>>
>> >>> Christian
>> >>>
>> >>> Am 19.09.2010 21:11, schrieb Benson Margulies:
>> >>>> I'm trying out the new JMS in the Java-first case, and I've hit my
>> >>>> first pothole.
>> >>>>
>> >>>> I'm going to commit the sample in the state that gets this error.
>> >>>>
>> >>>> Object implementor = new HelloWorldImpl();
>> >>>> JaxWsServerFactoryBean svrFactory = new
>> >>>> JaxWsServerFactoryBean();
>> >>>> svrFactory.setServiceClass(HelloWorld.class);
>> >>>>
>> >>>>
>> >>>> svrFactory.setTransportId(JMSSpecConstants.SOAP_JMS_SPECIFICIATION_TRA
>> >>>> NSPORTID);
>> >>>>
>> >>>>
>> >>>> svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLiv
>> >>>> e=1000"); svrFactory.setServiceBean(implementor);
>> >>>> svrFactory.create();
>> >>>>
>> >>>>
>> >>>> INFO: Setting the server's publish address to be
>> >>>> jms:queue:test.cxf.jmstransport.queue?timeToLive=1000
>> >>>> Exception in thread "main" java.lang.IllegalArgumentException: Target
>> >>>> ConnectionFactory must not be null
>> >>>> at org.springframework.util.Assert.notNull(Assert.java:112)
>> >>>> at
>> >>>>
>> >>>> org.springframework.jms.connection.SingleConnectionFactory.<init>(Sing
>> >>>> leConnectionFactory.java:130) at
>> >>>>
>> >>>> org.apache.cxf.transport.jms.JMSConfiguration.getOrCreateWrappedConnec
>> >>>> tionFactory(JMSConfiguration.java:441) at
>> >>>>
>> >>>> org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured
>> >>>> (JMSConfiguration.java:104) at
>> >>>>
>> >>>> org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.ja
>> >>>> va:111) at
>> >>>>
>> >>>> org.apache.cxf.transport.AbstractObservable.setMessageObserver(Abstrac
>> >>>> tObservable.java:48) at
>> >>>>
>> >>>> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBind
>> >>>> ingFactory.java:181) at
>> >>>>
>> >>>> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBinding
>> >>>> Factory.java:835) at
>> >>>> org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127) at
>> >>>>
>> >>>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.jav
>> >>>> a:186) at
>> >>>>
>> >>>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryB
>> >>>> ean.java:183) at demo.server.ServerJMS.main(ServerJMS.java:63)
>> >>>
>> >>> --
>> >>> ----
>> >>> http://www.liquid-reality.de
>> >
>> > --
>> > ----
>> > http://www.liquid-reality.de
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
Re: Java first and the new JMS config universe ...
Posted by Daniel Kulp <dk...@apache.org>.
On Sunday 19 September 2010 7:20:12 pm Benson Margulies wrote:
> Or, perhaps you prefer to answer this question:
>
> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
> JMS_ENDPOINT_URI);
>
> looks wrong. But what should I pass? What is the binding ID for SOAP/JMS?
I THINK you could use either of the SOAP id's:
http://schemas.xmlsoap.org/wsdl/soap/
http://schemas.xmlsoap.org/wsdl/soap12/
depending on what version you want.
Dan
>
> On Sun, Sep 19, 2010 at 6:18 PM, Christian Schneider
>
> <ch...@die-schneider.net> wrote:
> > Is that the full stack trace? Some times could not send message hides an
> > exception deeper down the trace.
> > For example if there is no listener you get could not send message but
> > deeper in the stack you see timeout waiting
> > for response or something like this.
> >
> > Best Regards
> >
> > Christian
> >
> > Am 19.09.2010 22:59, schrieb Benson Margulies:
> >> I've got everything working except using the JAX-WS Client API to
> >> create a client.
> >>
> >> The code below blows up. Do I need a JMS binding ID?
> >>
> >> org.apache.cxf.interceptor.Fault: Could not send Message.
> >> at
> >> org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(Messag
> >> eSenderInterceptor.java:48) at
> >> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorC
> >> hain.java:247) at
> >> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516) at
> >> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313) at
> >> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265) at
> >> org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> >> at
> >> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> >> at $Proxy34.sayHi(Unknown Source)
> >> at demo.client.ClientJMS.main(ClientJMS.java:61)
> >>
> >> private static HelloWorld createClientJaxWs() {
> >> Service service = Service.create(SERVICE_QNAME);
> >> // Add a port to the Service
> >> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
> >> JMS_ENDPOINT_URI);
> >> return service.getPort(HelloWorld.class);
> >> }
> >>
> >>
> >>
> >> On Sun, Sep 19, 2010 at 3:48 PM, Christian Schneider
> >>
> >> <ch...@die-schneider.net> wrote:
> >>> Hi Benson,
> >>> the important question is: Where do you set the connection factory. The
> >>> code
> >>> snippet you provided does not set one.
> >>>
> >>> Regards
> >>>
> >>> Christian
> >>>
> >>> Am 19.09.2010 21:11, schrieb Benson Margulies:
> >>>> I'm trying out the new JMS in the Java-first case, and I've hit my
> >>>> first pothole.
> >>>>
> >>>> I'm going to commit the sample in the state that gets this error.
> >>>>
> >>>> Object implementor = new HelloWorldImpl();
> >>>> JaxWsServerFactoryBean svrFactory = new
> >>>> JaxWsServerFactoryBean();
> >>>> svrFactory.setServiceClass(HelloWorld.class);
> >>>>
> >>>>
> >>>> svrFactory.setTransportId(JMSSpecConstants.SOAP_JMS_SPECIFICIATION_TRA
> >>>> NSPORTID);
> >>>>
> >>>>
> >>>> svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLiv
> >>>> e=1000"); svrFactory.setServiceBean(implementor);
> >>>> svrFactory.create();
> >>>>
> >>>>
> >>>> INFO: Setting the server's publish address to be
> >>>> jms:queue:test.cxf.jmstransport.queue?timeToLive=1000
> >>>> Exception in thread "main" java.lang.IllegalArgumentException: Target
> >>>> ConnectionFactory must not be null
> >>>> at org.springframework.util.Assert.notNull(Assert.java:112)
> >>>> at
> >>>>
> >>>> org.springframework.jms.connection.SingleConnectionFactory.<init>(Sing
> >>>> leConnectionFactory.java:130) at
> >>>>
> >>>> org.apache.cxf.transport.jms.JMSConfiguration.getOrCreateWrappedConnec
> >>>> tionFactory(JMSConfiguration.java:441) at
> >>>>
> >>>> org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured
> >>>> (JMSConfiguration.java:104) at
> >>>>
> >>>> org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.ja
> >>>> va:111) at
> >>>>
> >>>> org.apache.cxf.transport.AbstractObservable.setMessageObserver(Abstrac
> >>>> tObservable.java:48) at
> >>>>
> >>>> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBind
> >>>> ingFactory.java:181) at
> >>>>
> >>>> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBinding
> >>>> Factory.java:835) at
> >>>> org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127) at
> >>>>
> >>>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.jav
> >>>> a:186) at
> >>>>
> >>>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryB
> >>>> ean.java:183) at demo.server.ServerJMS.main(ServerJMS.java:63)
> >>>
> >>> --
> >>> ----
> >>> http://www.liquid-reality.de
> >
> > --
> > ----
> > http://www.liquid-reality.de
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: Java first and the new JMS config universe ...
Posted by Benson Margulies <bi...@gmail.com>.
I can get more trace in the debugger probably. The interesting thing
to me is that the CXF API equivalent works fine. If you update trunk
you can see this yourself.
On Sun, Sep 19, 2010 at 6:18 PM, Christian Schneider
<ch...@die-schneider.net> wrote:
> Is that the full stack trace? Some times could not send message hides an
> exception deeper down the trace.
> For example if there is no listener you get could not send message but
> deeper in the stack you see timeout waiting
> for response or something like this.
>
> Best Regards
>
> Christian
>
>
> Am 19.09.2010 22:59, schrieb Benson Margulies:
>>
>> I've got everything working except using the JAX-WS Client API to
>> create a client.
>>
>> The code below blows up. Do I need a JMS binding ID?
>>
>> org.apache.cxf.interceptor.Fault: Could not send Message.
>> at
>> org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:48)
>> at
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:247)
>> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
>> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
>> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
>> at
>> org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
>> at
>> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
>> at $Proxy34.sayHi(Unknown Source)
>> at demo.client.ClientJMS.main(ClientJMS.java:61)
>>
>> private static HelloWorld createClientJaxWs() {
>> Service service = Service.create(SERVICE_QNAME);
>> // Add a port to the Service
>> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
>> JMS_ENDPOINT_URI);
>> return service.getPort(HelloWorld.class);
>> }
>>
>>
>>
>> On Sun, Sep 19, 2010 at 3:48 PM, Christian Schneider
>> <ch...@die-schneider.net> wrote:
>>>
>>> Hi Benson,
>>> the important question is: Where do you set the connection factory. The
>>> code
>>> snippet you provided does not set one.
>>>
>>> Regards
>>>
>>> Christian
>>>
>>>
>>> Am 19.09.2010 21:11, schrieb Benson Margulies:
>>>>
>>>> I'm trying out the new JMS in the Java-first case, and I've hit my
>>>> first pothole.
>>>>
>>>> I'm going to commit the sample in the state that gets this error.
>>>>
>>>> Object implementor = new HelloWorldImpl();
>>>> JaxWsServerFactoryBean svrFactory = new
>>>> JaxWsServerFactoryBean();
>>>> svrFactory.setServiceClass(HelloWorld.class);
>>>>
>>>>
>>>> svrFactory.setTransportId(JMSSpecConstants.SOAP_JMS_SPECIFICIATION_TRANSPORTID);
>>>>
>>>>
>>>> svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLive=1000");
>>>> svrFactory.setServiceBean(implementor);
>>>> svrFactory.create();
>>>>
>>>>
>>>> INFO: Setting the server's publish address to be
>>>> jms:queue:test.cxf.jmstransport.queue?timeToLive=1000
>>>> Exception in thread "main" java.lang.IllegalArgumentException: Target
>>>> ConnectionFactory must not be null
>>>> at org.springframework.util.Assert.notNull(Assert.java:112)
>>>> at
>>>>
>>>> org.springframework.jms.connection.SingleConnectionFactory.<init>(SingleConnectionFactory.java:130)
>>>> at
>>>>
>>>> org.apache.cxf.transport.jms.JMSConfiguration.getOrCreateWrappedConnectionFactory(JMSConfiguration.java:441)
>>>> at
>>>>
>>>> org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:104)
>>>> at
>>>>
>>>> org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:111)
>>>> at
>>>>
>>>> org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48)
>>>> at
>>>>
>>>> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:181)
>>>> at
>>>>
>>>> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:835)
>>>> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127)
>>>> at
>>>>
>>>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:186)
>>>> at
>>>>
>>>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183)
>>>> at demo.server.ServerJMS.main(ServerJMS.java:63)
>>>>
>>> --
>>> ----
>>> http://www.liquid-reality.de
>>>
>>>
>
> --
> ----
> http://www.liquid-reality.de
>
>
Re: Java first and the new JMS config universe ...
Posted by Benson Margulies <bi...@gmail.com>.
Here's the stack trace at 'point of boom'
HTTPConduit.getURL(boolean) line: 836
HTTPConduit.getURL() line: 818
HTTPConduit.setupURL(Message) line: 764
HTTPConduit.prepare(Message) line: 497
MessageSenderInterceptor.handleMessage(Message) line: 46
PhaseInterceptorChain.doIntercept(Message) line: 247
ClientImpl.invoke(BindingOperationInfo, Object[], Map<String,Object>,
Exchange) line: 516
ClientImpl.invoke(BindingOperationInfo, Object[], Exchange) line: 313
ClientImpl.invoke(BindingOperationInfo, Object...) line: 265
JaxWsClientProxy(ClientProxy).invokeSync(Method, BindingOperationInfo,
Object[]) line: 73
JaxWsClientProxy.invoke(Object, Method, Object[]) line: 124
$Proxy34.sayHi(String) line: not available
ClientJMS.main(String[]) line: 61
Re: Java first and the new JMS config universe ...
Posted by Benson Margulies <bi...@gmail.com>.
Or, perhaps you prefer to answer this question:
service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING, JMS_ENDPOINT_URI);
looks wrong. But what should I pass? What is the binding ID for SOAP/JMS?
On Sun, Sep 19, 2010 at 6:18 PM, Christian Schneider
<ch...@die-schneider.net> wrote:
> Is that the full stack trace? Some times could not send message hides an
> exception deeper down the trace.
> For example if there is no listener you get could not send message but
> deeper in the stack you see timeout waiting
> for response or something like this.
>
> Best Regards
>
> Christian
>
>
> Am 19.09.2010 22:59, schrieb Benson Margulies:
>>
>> I've got everything working except using the JAX-WS Client API to
>> create a client.
>>
>> The code below blows up. Do I need a JMS binding ID?
>>
>> org.apache.cxf.interceptor.Fault: Could not send Message.
>> at
>> org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:48)
>> at
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:247)
>> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
>> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
>> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
>> at
>> org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
>> at
>> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
>> at $Proxy34.sayHi(Unknown Source)
>> at demo.client.ClientJMS.main(ClientJMS.java:61)
>>
>> private static HelloWorld createClientJaxWs() {
>> Service service = Service.create(SERVICE_QNAME);
>> // Add a port to the Service
>> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
>> JMS_ENDPOINT_URI);
>> return service.getPort(HelloWorld.class);
>> }
>>
>>
>>
>> On Sun, Sep 19, 2010 at 3:48 PM, Christian Schneider
>> <ch...@die-schneider.net> wrote:
>>>
>>> Hi Benson,
>>> the important question is: Where do you set the connection factory. The
>>> code
>>> snippet you provided does not set one.
>>>
>>> Regards
>>>
>>> Christian
>>>
>>>
>>> Am 19.09.2010 21:11, schrieb Benson Margulies:
>>>>
>>>> I'm trying out the new JMS in the Java-first case, and I've hit my
>>>> first pothole.
>>>>
>>>> I'm going to commit the sample in the state that gets this error.
>>>>
>>>> Object implementor = new HelloWorldImpl();
>>>> JaxWsServerFactoryBean svrFactory = new
>>>> JaxWsServerFactoryBean();
>>>> svrFactory.setServiceClass(HelloWorld.class);
>>>>
>>>>
>>>> svrFactory.setTransportId(JMSSpecConstants.SOAP_JMS_SPECIFICIATION_TRANSPORTID);
>>>>
>>>>
>>>> svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLive=1000");
>>>> svrFactory.setServiceBean(implementor);
>>>> svrFactory.create();
>>>>
>>>>
>>>> INFO: Setting the server's publish address to be
>>>> jms:queue:test.cxf.jmstransport.queue?timeToLive=1000
>>>> Exception in thread "main" java.lang.IllegalArgumentException: Target
>>>> ConnectionFactory must not be null
>>>> at org.springframework.util.Assert.notNull(Assert.java:112)
>>>> at
>>>>
>>>> org.springframework.jms.connection.SingleConnectionFactory.<init>(SingleConnectionFactory.java:130)
>>>> at
>>>>
>>>> org.apache.cxf.transport.jms.JMSConfiguration.getOrCreateWrappedConnectionFactory(JMSConfiguration.java:441)
>>>> at
>>>>
>>>> org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:104)
>>>> at
>>>>
>>>> org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:111)
>>>> at
>>>>
>>>> org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48)
>>>> at
>>>>
>>>> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:181)
>>>> at
>>>>
>>>> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:835)
>>>> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127)
>>>> at
>>>>
>>>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:186)
>>>> at
>>>>
>>>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183)
>>>> at demo.server.ServerJMS.main(ServerJMS.java:63)
>>>>
>>> --
>>> ----
>>> http://www.liquid-reality.de
>>>
>>>
>
> --
> ----
> http://www.liquid-reality.de
>
>
Re: Java first and the new JMS config universe ...
Posted by Christian Schneider <ch...@die-schneider.net>.
Is that the full stack trace? Some times could not send message hides
an exception deeper down the trace.
For example if there is no listener you get could not send message but
deeper in the stack you see timeout waiting
for response or something like this.
Best Regards
Christian
Am 19.09.2010 22:59, schrieb Benson Margulies:
> I've got everything working except using the JAX-WS Client API to
> create a client.
>
> The code below blows up. Do I need a JMS binding ID?
>
> org.apache.cxf.interceptor.Fault: Could not send Message.
> at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:48)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:247)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> at $Proxy34.sayHi(Unknown Source)
> at demo.client.ClientJMS.main(ClientJMS.java:61)
>
> private static HelloWorld createClientJaxWs() {
> Service service = Service.create(SERVICE_QNAME);
> // Add a port to the Service
> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
> JMS_ENDPOINT_URI);
> return service.getPort(HelloWorld.class);
> }
>
>
>
> On Sun, Sep 19, 2010 at 3:48 PM, Christian Schneider
> <ch...@die-schneider.net> wrote:
>> Hi Benson,
>> the important question is: Where do you set the connection factory. The code
>> snippet you provided does not set one.
>>
>> Regards
>>
>> Christian
>>
>>
>> Am 19.09.2010 21:11, schrieb Benson Margulies:
>>> I'm trying out the new JMS in the Java-first case, and I've hit my
>>> first pothole.
>>>
>>> I'm going to commit the sample in the state that gets this error.
>>>
>>> Object implementor = new HelloWorldImpl();
>>> JaxWsServerFactoryBean svrFactory = new JaxWsServerFactoryBean();
>>> svrFactory.setServiceClass(HelloWorld.class);
>>>
>>> svrFactory.setTransportId(JMSSpecConstants.SOAP_JMS_SPECIFICIATION_TRANSPORTID);
>>>
>>> svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLive=1000");
>>> svrFactory.setServiceBean(implementor);
>>> svrFactory.create();
>>>
>>>
>>> INFO: Setting the server's publish address to be
>>> jms:queue:test.cxf.jmstransport.queue?timeToLive=1000
>>> Exception in thread "main" java.lang.IllegalArgumentException: Target
>>> ConnectionFactory must not be null
>>> at org.springframework.util.Assert.notNull(Assert.java:112)
>>> at
>>> org.springframework.jms.connection.SingleConnectionFactory.<init>(SingleConnectionFactory.java:130)
>>> at
>>> org.apache.cxf.transport.jms.JMSConfiguration.getOrCreateWrappedConnectionFactory(JMSConfiguration.java:441)
>>> at
>>> org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:104)
>>> at
>>> org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:111)
>>> at
>>> org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48)
>>> at
>>> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:181)
>>> at
>>> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:835)
>>> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127)
>>> at
>>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:186)
>>> at
>>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183)
>>> at demo.server.ServerJMS.main(ServerJMS.java:63)
>>>
>> --
>> ----
>> http://www.liquid-reality.de
>>
>>
--
----
http://www.liquid-reality.de
Re: Java first and the new JMS config universe ...
Posted by Benson Margulies <bi...@gmail.com>.
I've got everything working except using the JAX-WS Client API to
create a client.
The code below blows up. Do I need a JMS binding ID?
org.apache.cxf.interceptor.Fault: Could not send Message.
at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:48)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:247)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
at $Proxy34.sayHi(Unknown Source)
at demo.client.ClientJMS.main(ClientJMS.java:61)
private static HelloWorld createClientJaxWs() {
Service service = Service.create(SERVICE_QNAME);
// Add a port to the Service
service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING,
JMS_ENDPOINT_URI);
return service.getPort(HelloWorld.class);
}
On Sun, Sep 19, 2010 at 3:48 PM, Christian Schneider
<ch...@die-schneider.net> wrote:
> Hi Benson,
> the important question is: Where do you set the connection factory. The code
> snippet you provided does not set one.
>
> Regards
>
> Christian
>
>
> Am 19.09.2010 21:11, schrieb Benson Margulies:
>>
>> I'm trying out the new JMS in the Java-first case, and I've hit my
>> first pothole.
>>
>> I'm going to commit the sample in the state that gets this error.
>>
>> Object implementor = new HelloWorldImpl();
>> JaxWsServerFactoryBean svrFactory = new JaxWsServerFactoryBean();
>> svrFactory.setServiceClass(HelloWorld.class);
>>
>> svrFactory.setTransportId(JMSSpecConstants.SOAP_JMS_SPECIFICIATION_TRANSPORTID);
>>
>> svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLive=1000");
>> svrFactory.setServiceBean(implementor);
>> svrFactory.create();
>>
>>
>> INFO: Setting the server's publish address to be
>> jms:queue:test.cxf.jmstransport.queue?timeToLive=1000
>> Exception in thread "main" java.lang.IllegalArgumentException: Target
>> ConnectionFactory must not be null
>> at org.springframework.util.Assert.notNull(Assert.java:112)
>> at
>> org.springframework.jms.connection.SingleConnectionFactory.<init>(SingleConnectionFactory.java:130)
>> at
>> org.apache.cxf.transport.jms.JMSConfiguration.getOrCreateWrappedConnectionFactory(JMSConfiguration.java:441)
>> at
>> org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:104)
>> at
>> org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:111)
>> at
>> org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48)
>> at
>> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:181)
>> at
>> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:835)
>> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127)
>> at
>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:186)
>> at
>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183)
>> at demo.server.ServerJMS.main(ServerJMS.java:63)
>>
>
> --
> ----
> http://www.liquid-reality.de
>
>
Re: Java first and the new JMS config universe ...
Posted by Benson Margulies <bi...@gmail.com>.
I don't.
http://cxf.apache.org/docs/soap-over-jms-10-support.html
does not tell me to do so.
I'm trying to entirely avoid JNDI, and I (mis?)reading that web page
as telling me that I can do so.
On Sun, Sep 19, 2010 at 3:48 PM, Christian Schneider
<ch...@die-schneider.net> wrote:
> Hi Benson,
> the important question is: Where do you set the connection factory. The code
> snippet you provided does not set one.
>
> Regards
>
> Christian
>
>
> Am 19.09.2010 21:11, schrieb Benson Margulies:
>>
>> I'm trying out the new JMS in the Java-first case, and I've hit my
>> first pothole.
>>
>> I'm going to commit the sample in the state that gets this error.
>>
>> Object implementor = new HelloWorldImpl();
>> JaxWsServerFactoryBean svrFactory = new JaxWsServerFactoryBean();
>> svrFactory.setServiceClass(HelloWorld.class);
>>
>> svrFactory.setTransportId(JMSSpecConstants.SOAP_JMS_SPECIFICIATION_TRANSPORTID);
>>
>> svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLive=1000");
>> svrFactory.setServiceBean(implementor);
>> svrFactory.create();
>>
>>
>> INFO: Setting the server's publish address to be
>> jms:queue:test.cxf.jmstransport.queue?timeToLive=1000
>> Exception in thread "main" java.lang.IllegalArgumentException: Target
>> ConnectionFactory must not be null
>> at org.springframework.util.Assert.notNull(Assert.java:112)
>> at
>> org.springframework.jms.connection.SingleConnectionFactory.<init>(SingleConnectionFactory.java:130)
>> at
>> org.apache.cxf.transport.jms.JMSConfiguration.getOrCreateWrappedConnectionFactory(JMSConfiguration.java:441)
>> at
>> org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:104)
>> at
>> org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:111)
>> at
>> org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48)
>> at
>> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:181)
>> at
>> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:835)
>> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127)
>> at
>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:186)
>> at
>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183)
>> at demo.server.ServerJMS.main(ServerJMS.java:63)
>>
>
> --
> ----
> http://www.liquid-reality.de
>
>
Re: Java first and the new JMS config universe ...
Posted by Benson Margulies <bi...@gmail.com>.
svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLive=1000"
+ "&jndiConnectionFactoryName=ConnectionFactory"
+ "&jndiInitialContextFactory"
+
"=org.apache.activemq.jndi.ActiveMQInitialContextFactory");
works better.
I'll update the confluence page.
On Sun, Sep 19, 2010 at 3:48 PM, Christian Schneider
<ch...@die-schneider.net> wrote:
> Hi Benson,
> the important question is: Where do you set the connection factory. The code
> snippet you provided does not set one.
>
> Regards
>
> Christian
>
>
> Am 19.09.2010 21:11, schrieb Benson Margulies:
>>
>> I'm trying out the new JMS in the Java-first case, and I've hit my
>> first pothole.
>>
>> I'm going to commit the sample in the state that gets this error.
>>
>> Object implementor = new HelloWorldImpl();
>> JaxWsServerFactoryBean svrFactory = new JaxWsServerFactoryBean();
>> svrFactory.setServiceClass(HelloWorld.class);
>>
>> svrFactory.setTransportId(JMSSpecConstants.SOAP_JMS_SPECIFICIATION_TRANSPORTID);
>>
>> svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLive=1000");
>> svrFactory.setServiceBean(implementor);
>> svrFactory.create();
>>
>>
>> INFO: Setting the server's publish address to be
>> jms:queue:test.cxf.jmstransport.queue?timeToLive=1000
>> Exception in thread "main" java.lang.IllegalArgumentException: Target
>> ConnectionFactory must not be null
>> at org.springframework.util.Assert.notNull(Assert.java:112)
>> at
>> org.springframework.jms.connection.SingleConnectionFactory.<init>(SingleConnectionFactory.java:130)
>> at
>> org.apache.cxf.transport.jms.JMSConfiguration.getOrCreateWrappedConnectionFactory(JMSConfiguration.java:441)
>> at
>> org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:104)
>> at
>> org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:111)
>> at
>> org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48)
>> at
>> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:181)
>> at
>> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:835)
>> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127)
>> at
>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:186)
>> at
>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183)
>> at demo.server.ServerJMS.main(ServerJMS.java:63)
>>
>
> --
> ----
> http://www.liquid-reality.de
>
>
Re: Java first and the new JMS config universe ...
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Benson,
the important question is: Where do you set the connection factory. The
code snippet you provided does not set one.
Regards
Christian
Am 19.09.2010 21:11, schrieb Benson Margulies:
> I'm trying out the new JMS in the Java-first case, and I've hit my
> first pothole.
>
> I'm going to commit the sample in the state that gets this error.
>
> Object implementor = new HelloWorldImpl();
> JaxWsServerFactoryBean svrFactory = new JaxWsServerFactoryBean();
> svrFactory.setServiceClass(HelloWorld.class);
> svrFactory.setTransportId(JMSSpecConstants.SOAP_JMS_SPECIFICIATION_TRANSPORTID);
> svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLive=1000");
> svrFactory.setServiceBean(implementor);
> svrFactory.create();
>
>
> INFO: Setting the server's publish address to be
> jms:queue:test.cxf.jmstransport.queue?timeToLive=1000
> Exception in thread "main" java.lang.IllegalArgumentException: Target
> ConnectionFactory must not be null
> at org.springframework.util.Assert.notNull(Assert.java:112)
> at org.springframework.jms.connection.SingleConnectionFactory.<init>(SingleConnectionFactory.java:130)
> at org.apache.cxf.transport.jms.JMSConfiguration.getOrCreateWrappedConnectionFactory(JMSConfiguration.java:441)
> at org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:104)
> at org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:111)
> at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48)
> at org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:181)
> at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:835)
> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127)
> at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:186)
> at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183)
> at demo.server.ServerJMS.main(ServerJMS.java:63)
>
--
----
http://www.liquid-reality.de