Hi Sergey ,
After I apply the fix CXF-6390 , all buildGet and buildPost for async
invocation work fine now.
So this fix is valid for me.
Great thanks for your help! :)
--
View this message in context:
http://cxf.547215.n5.nabble.com/Does-not-follow-spec-throw-ProcessingException-if-an-invoca
tried setter injection and get mvn build error...
private WebServiceContext context;
@Resource
public void setContext(WebServiceContext context) {
this.context = context;
}
java.lang.RuntimeException:
org.apache.cxf.service.factory.ServiceConstructionException
trying this:
@Resource
@WebMethod(exclude = true)
public void setContext(WebServiceContext context) {
this.context = context;
}
--
View this message in context:
http://cxf.547215.n5.nabble.com/WebServiceContext-is-null-after-upgrading-to-Karaf-3-0-3-tp5757099p5757107.ht
http://cxf.apache.org/docs/webservicecontext.html
the example code in page above is using:
@Resource
WebServiceContext wsContext;
which is what we are using and now suddenly not working after cxf upgrade.
is there some config required? which version of cxf is this code applicable
for? thx.
The Apache CXF community is proud to announce that CXF 3.1.0 has been released.
CXF 3.1.0 contains several new features:
* Optional enhancements to generated code to better support Java 7/8
* New Metrics capabilities for collecting metrics about CXF services
* New Throttling features for thro
Suddenly we are getting NPE for WebServiceContext instance in code that has
not changed before or after the Karaf 3.0.3 upgrade (culprit most likely is
cxf 3.0.4). This is causing a web service call from web client to fail.
We are using following code:
javax.xml.ws.WebServiceContext foo;
Con
Hi,
Could you try to move policy annotation to the class level, if the problem
persists?
Regards,
Andrei.
> -Original Message-
> From: Jose Luiz Berg [mailto:jluiz.b...@jbdesign.com.br]
> Sent: Mittwoch, 29. April 2015 21:27
> To: users@cxf.apache.org
> Subject: Re: Antwort: RE: Antwort
Hi,
> -Original Message-
> From: nikolaus.hu...@cargarantie.com
> [mailto:nikolaus.hu...@cargarantie.com]
> Sent: Dienstag, 5. Mai 2015 16:16
> To: users@cxf.apache.org
> Subject: Antwort: RE: Antwort: RE: Antwort: RE: Custom WS-Security Policy for
> Webservice
>
> Hi,
>
> > > I've debug
Hi Sergey,
Thanks for the reply! It does not report a user principal. I can try the
ContainerRequestFilter or if the UriInfo is also accessible from the
MessageContext I might be able to bypass the code that breaks as well.
Regards
Kiren
On Wed, May 6, 2015 at 12:47 PM, Sergey Beryozkin
wrote:
Hi Kiren,
sorry for a delay.
is the actual security context is returned as null or it does not report
a user principal ?
If it is the latter then it would explain it, the default
SecurityContext is set at the HTTP transport level which is bypassed in
the local case.
What you can do though
Does it not work for you ? Let me know please what exactly are you
interested in
Cheers, Sergey
On 06/05/15 05:05, las wrote:
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
11 matches
Mail list logo
