SamlTokenInterceptor

2015-12-03 Thread joesam
Hi all, I am new to CXF. I am using v3.0.4. I have a requirement to read SAML token from a incoming SOAP header request and store the token for other purposes. I want to use SamlTokenInterceptor. Do I need to extend this class and override processToken method? Also, in configuration, do I pass

Re: MLHttpRequest cannot load

2015-12-03 Thread Shashank Dutt Jha
I added following code: Still facing issue @CrossOriginResourceSharing( allowOrigins = { "http://localhost:56696; }, allowCredentials = true, maxAge = 1, allowHeaders = { "X-custom-1", "X-custom-2" }, exposeHeaders = {

Re: Log incoming message with the corresponding response

2015-12-03 Thread Sergey Maslov
Guys, Christian, Could I set LoggingFeature for logging application requests acting as a web service client? I looks like, it is for endpoints only. What could I use for ws client logging to log request and response (with the similar functionality as LoggingFeature)? Sergey Maslov On Mon, Nov

RE: Java2WS - SEI - multiple classpaths

2015-12-03 Thread Kastelic, Benjamin
The path parameter is correct. I tried loading a class manually in a separate project and there were no problems. It would seem that the classpath parameter is ignored by CXF? Benjamin -Original Message- From: Aki Yoshida [mailto:elak...@gmail.com] Sent: torek, 01. december 2015 19:04

Re: CXF incorrect WSDL automatically generated ? Please help !

2015-12-03 Thread Aki Yoshida
the cxf (including version 2.7.12) should be generating the parts attribute in that case and I don't understand why you needed to manually add it. i just tried your sample (only changed the return type from your custom type to String) with cxf-2.7.12 and I am getting the following binding

Upgrading to CXF 3.1.4 getting "No Server set for org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine"

2015-12-03 Thread martijn.list
Hi, I trying to upgrade from an old CXF version to the latest release (3.1.4). I'm using spring 3 and try to configure a stand alone HTTP transport using jetty. My application starts. However during startup there are warnings indicating that the HTTP server is not correctly setup. Also jetty

Re: MLHttpRequest cannot load

2015-12-03 Thread Sergey Beryozkin
Please do not copy exception traces into Subject :-) Have a look at http://cxf.apache.org/docs/jax-rs-cors.html Register that filter as a provider Sergey On 03/12/15 11:04, Shashank Dutt Jha wrote: I want the REST server to be accessible to web/ browser app. Which is correct example to refer

Re: MLHttpRequest cannot load http://161.85.91.7:9001/office/offices/123. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the req

2015-12-03 Thread Shashank Dutt Jha
I want the REST server to be accessible to web/ browser app. Which is correct example to refer to. On Wed, Dec 2, 2015 at 11:15 AM, Shashank Dutt Jha wrote: > Server side code: > >protected Server() throws Exception { > JAXRSServerFactoryBean sf = new

RE: CXF incorrect WSDL automatically generated ? Please help !

2015-12-03 Thread Mercader, Felix
Daniel / Aki... thank you very very much !!! My problem is now fixed. My webservice is working nice wonderfully and the header parameters are in the header only, not in the body too anymore. Let me show you how I fixed and ask you one more question please. Daniel, you were totally right about

Re: CXF incorrect WSDL automatically generated ? Please help !

2015-12-03 Thread Aki Yoshida
to add to what i said below, as the generated wsdl in your cxf setup and the plain cxf setup differs, i suspect that your cxf setup has some inconsistency, either having a duplicate very old cxf version being picked up that might have this incorrect behavior or something other than cxf is

RE: CXF incorrect WSDL automatically generated ? Please help !

2015-12-03 Thread Mercader, Felix
Hi Aki Thank you very much for your interest and responses. As an update, as you suggested, I was able to update to cxf 3.0.7. I can't use 3.1.4 at the moment as my webservice fails when I deploy in weblogic but well, I am ok with this. I just did it again, without using the plain wsdl. I

Re: Log incoming message with the corresponding response

2015-12-03 Thread Sergey Maslov
Thank you! I've cleared up this by myself. I can configure it like the usual feature in the features section! Sergey Maslov On Fri, Dec 4, 2015 at 12:37 PM, Sergey Maslov wrote: > Guys, Christian, > Could I set LoggingFeature for logging application requests acting as a

Re: CXF incorrect WSDL automatically generated ? Please help !

2015-12-03 Thread Aki Yoshida
Hi Felix, you'll have to check with weblogic people. we can't do nothing more from the cxf side. maybe you can try the below test service with your web logic setup and see how it generates its wsdl.

Request/response message determine with EventType.FAULT_OUT and EventType.FAULT_IN

2015-12-03 Thread Sergey Maslov
Hi! I want to add custom logging to the cxf web application (acts as a client and as a server for different services). I can implement LogSender interface. It looks like I could not determine the type of message (request/response) based on EventType.FAULT_OUT (or EventType.FAULT_IN), cause they

Re: CXF incorrect WSDL automatically generated ? Please help !

2015-12-03 Thread Daniel Kulp
I guess I would start with taking your test case and building a war that would deploy on Tomcat and checking if the proper WSDL is OK there. Then try making the minimum modifications needed for WebLogic and seeing what happens. I wonder if it’s one of: 1) Picking up a different version of

RE: CXF incorrect WSDL automatically generated ? Please help !

2015-12-03 Thread Mercader, Felix
Hi Aki I tried but you said. The automatic WSDL that I got after deploying in WebLogic successfully is similar but not identical. In fact, mine is quite small. And the important bit... In your wsdl, where you have: I have again: So clearly I am having the same problem again. I have no

Re: @BeanParam doesn't seem to support inheritance on client side

2015-12-03 Thread Sergey Beryozkin
Hi Veit The proxy impl was not checking fields on superclasses, got it fixed: https://issues.apache.org/jira/browse/CXF-6701 If you can move JAX-RS annotations to setters then it will work without a fix, it will be a bit faster too Thanks, Sergey On 01/12/15 21:47, Veit Guna wrote: I