On Friday 26 November 2010 6:47:11 pm Dennis Sosnoski wrote:
My original message is included in this one, at the bottom. There are
three different variations of Checkstyle errors: 1) unexpected char:
0x; 2) Missing a header - not enough lines in file; and 3) Wrong
order for import.
On Friday 26 November 2010 5:56:27 am Dennis Sosnoski wrote:
Relating to this same issue of the WS-RM status, does the current code
handle interactions with WS-Security? In particular, I'm wondering what
happens if you're using timestamps with signing - does the WS-RM code
generate a new
Per spec, the way CXF is working is OK.
Basically, on the server side, the server should return the 200/201 as soon as
the message is received (and we can tell it's a oneway). It should not wait
until the message has been fully processed and dispatched and such. For SOME
transports
On Thursday 25 November 2010 11:39:07 am Benson Margulies wrote:
I bet that Dan is his usual overtaxed self, but I'm restarting this
thread to attract his attention, since I fear that I've dug us into a
whole.
The idea of a default, or thread default, bus in CXF is modelled, in
some
OK, I'll unwind.
On Mon, Nov 29, 2010 at 2:04 PM, Daniel Kulp dk...@apache.org wrote:
On Thursday 25 November 2010 11:39:07 am Benson Margulies wrote:
I bet that Dan is his usual overtaxed self, but I'm restarting this
thread to attract his attention, since I fear that I've dug us into a
I am currently trying to dig deeper into the http transport.
One part of the code that I really don´t like is the CXFServlet. If I
understand correctly it is being used when you want to have a servlet
transport together with a spring application context.
In the documentation
Actually it's used when you want to have web services reside within a Servlet
container. It might be Spring aware, but should be Spring neutral. (AFAIK)
Craig.
On 2010-11-29, at 6:10 PM, Christian Schneider wrote:
I am currently trying to dig deeper into the http transport.
One part of the
