Hi
Since SOAP/JMS test suit could work with the other SOAP/JMS implementation,
I think we should not just write the test against CXF stack.
We could leverage the spring template and listener to implement the
generation of
the test JMS message, check the response JMS message.
In this way the tes
So, we got rid of our eclipse plugin because STP/WTP are supposed to
be covering the ground, and now users here can't find anything working
except betas on the bleeding edge, and our Confluence site is a
'someday' placeholder. Can someone tell me what's the current
situation, and I'll update conflu
> So, we got rid of our eclipse plugin because STP/WTP are supposed to
> be covering the ground, and now users here can't find anything working
> except betas on the bleeding edge, and our Confluence site is a
> 'someday' placeholder. Can someone tell me what's the current
> situation, and I'll upd
http://cwiki.apache.org/CXF20DOC/cxf-tools-in-eclipse.html
needs help.
I strongly remember that there was an entire eclipse plugin in our
tree back when I first showed up. I could be confabulating.
On Tue, Jul 14, 2009 at 12:11 PM, Oisin Hurley wrote:
>> So, we got rid of our eclipse plugin bec
> http://cwiki.apache.org/CXF20DOC/cxf-tools-in-eclipse.html
>
> needs help.
Thanks
> I strongly remember that there was an entire eclipse plugin in our
> tree back when I first showed up. I could be confabulating.
I think you might be confabulating about that :)
--oh
Sounds good to me. The messages could be read from files on the classpath.
In my company we do these tests with camel but I don´t think it would be
good to have this dependency.
Greetings
Christian
Willem Jiang schrieb:
Hi
Since SOAP/JMS test suit could work with the other SOAP/JMS implemen
The myeclipse people have subtracted XFire and not added CXF. Should
we goose them?
I don't think so. They're a private business and are welcome to make
whatever business decisions they feel will maximize their profits. If
they've come to the conclusion that removing XFire and not including CXF
maximizes income vs. outgo for them, so be it.
Glen
bimargulies wrote:
>
> The m
> I don't think so. They're a private business and are welcome to make
> whatever business decisions they feel will maximize their profits. If
> they've come to the conclusion that removing XFire and not including CXF
> maximizes income vs. outgo for them, so be it.
They are using Metro 1.1 for
So, I modified the aegis sample to demonstrate a service with a
Document as a return type. The client receives the
org.w3c.dom.Document for the 'return' wrapper element, not the actual
element corresponding to the server's return value, which is one
element down. Bug?
10 matches
Mail list logo