Next question: does this work java-first via the JAX-WS API?
On Wed, Sep 15, 2010 at 10:34 PM, Daniel Kulp wrote:
> On Wednesday 15 September 2010 2:33:47 pm Benson Margulies wrote:
>> This is from the java_first_jms sample that I cleaned up. Why is the URL in
>> the server factory trivial? Why d
On Sunday 19 September 2010 1:33:41 pm Benson Margulies wrote:
> Next question: does this work java-first via the JAX-WS API?
In theory, yes. :-) Just use the full jms: url defined in the spec. I think
some of the transport system tests do this, but not 100% sure.
Dan
>
> On Wed, Sep 15,
it figures out the transport ID for itself, or is there a snail in the house?
I'll try it.
On Sun, Sep 19, 2010 at 1:41 PM, Daniel Kulp wrote:
> On Sunday 19 September 2010 1:33:41 pm Benson Margulies wrote:
>> Next question: does this work java-first via the JAX-WS API?
>
> In theory, yes. :-
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.setServiceCl
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 co
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
wrote:
> Hi Benson,
> the important question i
svrFactory.setAddress("jms:queue:test.cxf.jmstransport.queue?timeToLive=1000"
+ "&jndiConnectionFactoryName=ConnectionFactory"
+ "&jndiInitialContextFactory"
+
"=org.apache.activemq.jndi.ActiveMQInitialContext
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.
Hi Sergey,
On Tue, Sep 14, 2010 at 11:33 PM, Sergey Beryozkin wrote:
> Hi Tomasz
>
> sorry for a delay
>
> On Fri, Sep 10, 2010 at 4:01 PM, Tomasz Oponowicz
> wrote:
>>
>> Hi Sergey,
>>
>> Welcome everyone after quite long break.
>>
>> I've prepared sample user interface for "search capabilities
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.2
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
wrote:
> Is that the full stack trace? Some times could not send message hides
Hi Tomasz
I think it looks really nice. I'd just prefer to rename "Fiter" to
"Settings" and "Edit details" to "Filter" - because "Filter" settings are
just some of the settings which users will want to change. But I'm OK with
Filter/EditSettings as well for now...
Please go ahead with implementin
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(M
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
wrote:
> Is that the full stack trace?
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 u
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 wrote:
> On Sunday 19 September 2010 7:20:12 pm Benson Margulies wrote:
>> Or, perhaps you prefer to
On 9/17/10 10:43 PM, Daniel Kulp wrote:
We've now challenged the last few remaining JAX-RS 1.1 tests. We're waiting
to see if the challenge is accepted or not (and it's going to be slow due to
JavaOne), but that pretty much means we're really close to having JAX-RS 1.1
stuff ready. JAX-WS 2.2
Willem,
If you've been reading the email, you'll see that I've hit a snag in
using the JAX-WS API to create a client proxy over JMS in the
java_first_jms sample. If you'd care to dive in and see if you can fix
the sample (or some bug in the underlying code) I'd be grateful.
--benson
>> 3) (opt
On 9/20/10 9:23 AM, Benson Margulies wrote:
Willem,
If you've been reading the email, you'll see that I've hit a snag in
using the JAX-WS API to create a client proxy over JMS in the
java_first_jms sample. If you'd care to dive in and see if you can fix
the sample (or some bug in the underlying
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 @WebServi
20 matches
Mail list logo
