CXF uses the prefix to determine which transport implementation to
use. So jms:// triggers
that the jms transport is handling this endpoint. So I think this is
more than only a requirement of jax ws.
As we now already have three ways of configuring jms we of course should
think about retiring
On Monday 20 September 2010 8:22:07 pm Benson Margulies wrote:
> I'm not sure what, if anything, to do with pubsub. It's all using the
> wsdl config, right? Is there anything wrong?
There's nothing WRONG. It's a perfectly fine example. It's just showing how
to use the older WSDL config and no
On Wednesday 22 September 2010 2:50:17 pm Łukasz Moreń wrote:
> Hi all,
>
> There are still "few" things to do with OAuth module before it can be easy
> usable for users.
>
> From what I see:
>
> - integration with java role based access control (@RolesAllowed, @Secured
> annotations). At least
On Wednesday 22 September 2010 8:24:39 am Aki Yoshida wrote:
> Hi,
> regarding this HTTP 202 problem for a piggybacked WS-RM ack response,
> I created the jira entry:
>
> CXF-3004
> Inconsistent HTTP response code 202 returned for WS-RM piggybacked Ack
> response message
I'll try an take a look.
