Thanks Sergey, I'm afraid I just didn't fully grasp what the real deal was
about, being test client and server in the same jee instance.
Regards
--
View this message in context:
Hi Mandy
Thanks for the help :-),
I've thought of the other possible option which
might be used before 2.7.8 gets released,
- create JAX-RS Response and return it as CXF MessageContentsList,
Response r = new MyExceptionMapper().toResponse(new MyException());
return new MessageContentsList(r);
Hi
On 11/10/13 20:52, David Hay wrote:
I'm trying to pass in an empty array as a JSON parameter, but it seems to
come through as null.
I'm trying:
-d '{cmd:{obj1: []}}'
where cmd is an object Cmd which has Obj1[ ]
Is there a way to do this in CXF?
I'm not sure it is possible at the
Hi Susan,
You should be able to use a SymmetricBinding to avoid the need for
client certificates with WS-SecureConversation - see my article at
http://www.ibm.com/developerworks/java/library/j-jws17/index.html for an
example. That still leaves you distributing server certificates to
clients,
On 10/15/2013 12:24 AM, Dennis Sosnoski wrote:
...That still leaves you distributing server certificates to clients,
but you can always embed these in the policy and have the client load
that from a secure source (note that I haven't tried this with CXF,
but AFAIK it should work).
Sorry, I
On 14/10/2013 01:17, Jim Talbut wrote:
I /think/ this is breaking because the proxy for the PreAuth is meaning that
the @Context annotation isn't being detected by CXF.
Can that be fixed?
I don't have experience CXF + Spring Security directly, but I am using Spring
and it had to create a
Hi
On 14/10/13 13:17, Winnebeck, Jason wrote:
On 14/10/2013 01:17, Jim Talbut wrote:
I /think/ this is breaking because the proxy for the PreAuth is meaning that
the @Context annotation isn't being detected by CXF.
Can that be fixed?
I don't have experience CXF + Spring Security directly,
Hi,
I made the above observation when trying to populate field soapaction which
in my case was empty.
When I then tried to insert soapAction explicitly via
headers.put(SOAPAction, Arrays.asList(http://mysoapaction;));
I got an error from server the given soapaction does not match an
operation.
I
Hi Susan,
This sounds like a perfect use-case for XKMS. CXF ships with an XKMS
service, and also a a WSS4J Crypto implementation which can ask the
remote service for certificates for WS-Security. For example, see the
following system test:
Hi Jason, Thanks for the response, but this does not appear to work for
me, at least not in CXF 2.7.6. I set this property but the WSDL still
includes every single jaxb class within the types section in the WSDL even
though my service doens't even reference them at all.
*Aaron Titus*
Senior
On Oct 14, 2013, at 9:39 AM, Aaron Titus ati...@fwdco.com wrote:
Hi Jason, Thanks for the response, but this does not appear to work for
me, at least not in CXF 2.7.6. I set this property but the WSDL still
includes every single jaxb class within the types section in the WSDL even
though
On 10/14/2013 09:05 AM, Colm O hEigeartaigh wrote:
Hi Susan,
This sounds like a perfect use-case for XKMS. CXF ships with an XKMS
service, and also a a WSS4J Crypto implementation which can ask the
remote service for certificates for WS-Security. For example, see the
following system test:
And now that I've had some sleep I'll modify my earlier retraction.
Metro, at least, does provide a way of doing the server certificate
distribution in WSDL, but through the WS-Addressing EndpointReference
rather than through the policy:
Hi Colm,
I will resume work on this subject tomorrow.
So I'm in a situation where there's no soap header setted, and the spring
configuraiton seems to be ignored (which would be quite logical as we don't
use it in the java code, just rebuiling all ourselves.)
So how can I make sure the soap
Looking further into this problem, I notice that the replies' To addresses are
always correct. If there's a fault, then the WS-Addressing To header shows the
faultTo address. The problem in both synchronous and asynchronous situations
is that the reply always comes back to the replyTo address
15 matches
Mail list logo
