Could you please elaborate a bit more?
--
View this message in context:
http://cxf.547215.n5.nabble.com/Auto-generation-of-WADL-tp5756919p5757041.html
Sent from the cxf-user mailing list archive at Nabble.com.
On Tue, May 5, 2015 at 1:58 AM, Alx wrote:
> As a client, I need to connect to a remote web service which provides a
> WSDL that does not specify any WS-SecurityPolicy. I have a local copy of
> the WSDL where I added the policy. The rest of the WSDL is the same.
>
It should work fine. We usuall
Sure, the issue I linked to earlier was about an async client hanging in
case of a GET request failing early at the client side due to the
connection issue, it was fixed for 3.0.4. Note CXF 3.0.5 has just been
released.
CXF-6390 has just been resolved and addresses the issue with similar
reques
and do you have any fix in the newer build?
I see it aslo not work in 3.0.4
Thanks!
--
View this message in context:
http://cxf.547215.n5.nabble.com/Does-not-follow-spec-throw-ProcessingException-if-an-invocation-processing-failure-tp5756972p5757027.html
Sent from the cxf-user mailing list arc
When invoking a JAX-WS service that is supposed to send a multipart/related
message with an attachment whose Content-Type is "image/jpeg", the following
occurs:
Caused by: javax.activation.UnsupportedDataTypeException: no object DCH for
MIME type image/jpeg
at
javax.activation.ObjectDataC
My CXF version is 3.0.3
--
View this message in context:
http://cxf.547215.n5.nabble.com/Does-not-follow-spec-throw-ProcessingException-if-an-invocation-processing-failure-tp5756972p5757024.html
Sent from the cxf-user mailing list archive at Nabble.com.
An update to my reply.
I had a chat with Dan on #apache-cxf and he explained to me that the
logic was for creating the client from an annotated class and the
jaxws spec requires non-namespaced targetNamespace to be qualified. In
addition to this, WS-I Basic Profile rule R1014 also states the root
I am using EAP6.2
--
View this message in context:
http://cxf.547215.n5.nabble.com/Custom-WS-Security-Policy-for-Webservice-tp5756262p5757011.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi - what CXF version is it ?
Sergey
On 05/05/15 13:45, ellen wrote:
Hi Sergey,
Thanks for quickly follow up.
BTW, in my sample test code, if I change the buildPost to buildGet:
Invocation invocation = builder.buildGet();
I cannot get the Exception and the thread will hang and java process w
Hi,
> > I've debugged the PlicyAnnotationListener at the recommended
> position, but no
> > result. Both methods in case ENDPOINT_SELECTED (addPolicies(...) and
> > addEndpointImplPolicies(...)) do not add a policy since the
policylists are
> > always empty (null). The reason for this is probab
Thank you...I will try .
Thank you for your help.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Ws-Security-client-newbie-tp5756790p5756997.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi Sergey,
Thanks for quickly follow up.
BTW, in my sample test code, if I change the buildPost to buildGet:
Invocation invocation = builder.buildGet();
I cannot get the Exception and the thread will hang and java process won't
stop.
So I think buildPost and buildGet should be the different is
CXF-6252 is simpler, in this case a bit more work is needed
I'll have a look
Cheers, Sergey
On 05/05/15 12:04, Sergey Beryozkin wrote:
Hi
What version are you testing ?
I think this issue has been fixed as part of
https://issues.apache.org/jira/browse/CXF-6252
and the test should pass with CXF
There seems to be a bug in CXF. I think I am seeing the same issue.
I'll have to look into it a little more.
A quick workaround to make your broken client talk to the server is to
use CXF's transform feature. See
http://cxf.apache.org/docs/transformationfeature.html#TransformationFeature-Changingi
Hi
What version are you testing ?
I think this issue has been fixed as part of
https://issues.apache.org/jira/browse/CXF-6252
and the test should pass with CXF 3.0.4
Cheers, Sergey
On 05/05/15 07:11, ellen wrote:
Hi all,
I'm watching and testing CXF with jaxrs spec.
When using invocation, I
The "Type" attribute does not have a "wsse" prefix. Also "PasswordText" is
incorrect, you are missing the URI that goes before it. Here is an
example...
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
xmlns:wsu="
http://docs.oasis-open.org/wss/2004/01/oasis-2004
You can have your WSDL stored anywhere, whether locally or on another
machine. As long as this WSDL specifies the correct target URL, the
client will send the requests to that target URL.
2015-05-04 19:58 GMT+02:00 Alx :
> As a client, I need to connect to a remote web service which provides a
>
On 04/05/2015 22:16, Sergey Beryozkin wrote:
Hi Francesco
Good stuff, thanks for isolating the problem.
I'm not sure how to make it easier on the CXF side - I'll update the
generator to log a warning (will make it into 3.1.1-SNAPSHOT though
:-)) when a JAXBContext is null despite a number of J
18 matches
Mail list logo
