NullPointerException: CXFBus extensions and WSDLManager.class

Hi, I'm writing a JAX-WS client with cxf 2.0.10 but I have a nasty NullPointerException when using getBus().getExtension(WSDLManager.class). I have found some posts regarding this exception and the solution was to initialize the bus. But that didn't work for me with my Spring using

Re: Problem with SOAP handlers in Geronimo

Also, i tried to use very simple SOAPHandler. This handler only printed message to console. But I got same error:-((. And as I understood, problem occurred when server sent response to client. Are anybody can help me? F1 F1 :working: F1 F1 -- View this message in context:

How to avoid to generate hard coded wsdl file reference - wsdl2java

Hi, I would like to know if it is possible to have local reference of the wsdl file in the SEI instead of the hard coding generated by wsdl2java using the maven plugin cxf-codegen : Here is a snapshot : @WebServiceClient(name = ReportIncidentEndpointService, wsdlLocation =

RE: Logging/Debugging Question

Thanks, That worked great. Jeff -Original Message- From: Eoghan Glynn [mailto:eogl...@progress.com] Sent: Tuesday, March 03, 2009 5:05 PM To: users@cxf.apache.org; users@cxf.apache.org Subject: RE: Logging/Debugging Question Hi Jeff, If you enable WS-Addressing (see the

Re: JAX-RS response for POST and PUT no longer working

Having said that, I'm fixing it now, so that the error message will be properly reported even if its media type has not been originally accepted Cheers, Sergey - Original Message - From: Sergey Beryozkin sbery...@progress.com To: Sergey Beryozkin sbery...@progress.com;

Re: How to avoid to generate hard coded wsdl file reference - wsdl2java

There is a wsdlLocation flag on the code generator to specify the location that is spit into the code. The two common things to stick in there are: 1) META-INF/wsdl/. to resolve it from the war/classpath type thing 2) Some location that a catalog is then used to fully resolve. Dan

support for configuring addressing in the dynamic client

Is it possible to add WSAddressingFeature to the Client created from JaxWsDynamicClientFactory? I tried to do the following, but it failed at runtime due to class cast exception. So, I cannot cast it to a org.apache.cxf.jaxws.EndpointImpl which has getFeatures() API. I tried using

What does this WSDLException mean?

I've a client consuming a web service using the WSDL file given. When I started to test, I got the following exception thrown. javax.wsdl.WSDLException: WSDLException (at /soapenv:Envelope): faultCode=INVALID_WSDL: Expected element '{http://schemas.xmlsoap.org/wsdl/}definitions'. at

Aegis Databinding Re-use

Hello, There appears to be an inconsistency in the ability to reuse an Aegis Databinding across multiple services. In cxf 2.0, it was possible, but in the latest 2.2-SNAPSHOT it is not. Can anyone explain this, and whether it is intended? Here is a sample the configuration that works in 2.0

Re: Aegis Databinding Re-use

If it worked for you in 2.0, it worked purely by accident, I think. However, I am a bit confused as follows. Reusing the entire service factory for multiple endpoints had never worked, period. That doesn't necessarily imply that a databinding couldn't be used in multiple service factories.

Re: Aegis Databinding Re-use

I agree that sharing the databindings could cause a conflict and thus should probably not be allowed. I am also confused, because I think you are saying that a large part of my configuration is bad (i.e. reusing the service-factory). Is that the case, and can you show me or point me to an

Re: Aegis Databinding Re-use

What I've been telling people to do is to use scope='prototype' on service factories and data bindings. Example-wise, I bet we're short. Glenn or Dan? On Thu, Mar 5, 2009 at 3:00 PM, relphie relp...@gmail.com wrote: I agree that sharing the databindings could cause a conflict and thus should

Re: What does this WSDLException mean?

I'm unsure, but I think that the XMLSpy comment you have on line two may be causing the problem. (It's possible that such comments are not allowed, and hence the parser is complaining that it can't find the definitions element on line 2 where it is expecting it.) Can you remove that and see if

Re: Exception Inheritance Model

FWIW, this is what I did when I had several types of different error messages to handle: http://www.jroller.com/gmazza/entry/database_crud_actions_with_web HTH, Glen Petr V. wrote: Any one please ? Thanks, Petr --- On Wed, 3/4/09, Petr V. greatman...@yahoo.com wrote: From: Petr V.

Re: Problem with SOAP handlers in Geronimo

Can your web service operate with Tomcat? I don't know if your problem is CXF-related or Geronimo-related? Also, if desperate you may want to try Metro and see if it gives you different error messages. Using Tomcat w/CXF or Metro: http://www.jroller.com/gmazza/entry/creating_a_wsdl_first_web1

Re: WSSecurityEngine: No crypto property file supplied for decryption

Yes, I think you need encryption/signature configuration files: http://www.jroller.com/gmazza/entry/implementing_ws_security_with_the Bryan Kearney wrote: Has anyone else seen this? -- bk -- View this message in context:

Re: Is this a bug

Nope, the service name and port name you specify are overwritten by the CXF servlet that hosts the web service. Metro does the same. Note #2 here is what I was able to find out: http://www.jroller.com/gmazza/entry/creating_a_wsdl_first_web1#notes Glen RickCromer wrote: I’m generating the

RE: support for configuring addressing in the dynamic client

Hi Arul, We'd a vaguely similar requirement in distributed OSGi and here's the approach I took ... 1. Spring-load a CXF policy feature wrapping the AddressingPolicy assertion. p:policies id=nonDecoupledAddressing xmlns:p=http://cxf.apache.org/policy;

Re: What does this WSDLException mean?

Is the client grabbing the live wsdl at runtime at startup?It LOOKS like you pointed it at the endpoint address without adding the ?wsdl to the end of the URL. It's thus getting a SOAP message back (probably a fault) instead of the wsdl. Dan On Thu March 5 2009 2:46:27 pm Diginside

Re: Aegis Databinding Re-use

On Thu March 5 2009 3:06:02 pm Benson Margulies wrote: What I've been telling people to do is to use scope='prototype' on service factories and data bindings. Example-wise, I bet we're short. Glenn or Dan? Yea, scope=prototype is the way to go. Dan On Thu, Mar 5, 2009 at 3:00 PM, relphie

Re: Validating wsdlfile with -validate option

On Wed March 4 2009 8:04:07 am stevewu wrote: Hi Dan, Does it check for all WS-I BP file rules or just a subset. Also which version of WS-I BP was used for checking? Basically a subset, and I'm not even sure which rules. As people encounter issues, we add more checks. Dan Thanks

Specifying fields to include/exclude from return XML

Is anyone is aware of how I can dynamically tell CXF (and thus JAXB) that there are some fields I want excluded from the resultant XML being returned? I don't want to reinvent the wheel if I don't have to, but I can't find information on how to do what I want using the CXF framework rather than

Re: What does this WSDLException mean?

Thanks for the quick reply. I just removed the comment from the local wsdl file I used to generate my client stub, and tested it again. The error remains. I'll ask the wsdl author to remove the comment from the live wsdl and see if it helps. Glen Mazza wrote: I'm unsure, but I think that

Re: What does this WSDLException mean?

Thanks Dan. Well, in the CXF generated service, there is an annotation, and a static instantiation of url, @WebServiceClient(name = NotificationService, wsdlLocation = file:/E:/home/perforce/depot/development/software/client1/schema/notification/notification.wsdl,

Re: Specifying fields to include/exclude from return XML

David Castro wrote: Is anyone is aware of how I can dynamically tell CXF (and thus JAXB) that there are some fields I want excluded from the resultant XML being returned? I don't want to reinvent the wheel if I don't have to, but I can't find information on how to do what I want using the

Re: Exception Inheritance Model

Daniel, can you please look into this issue. :-( Thanks Glen for your response.I believe your BasicFault class is simple POJO which is not inheriting from java Exception class, Right ? Can you please confirm it. I have another issue. My web service calls some other business functions which

Re: Exception Inheritance Model

Petr V. wrote: Daniel, can you please look into this issue. :-( Thanks Glen for your response.I believe your BasicFault class is simple POJO which is not inheriting from java Exception class, Right ? Can you please confirm it. Yes. This is all defined in the JAX-WS 2.1 specification,

SOAP Payload size in a request

Hello, We use Apache CXF 2.1.3 as our SOAP engine and Apache Tomcat 6 to handle HTTP. When a SOAP requests is received by the system (via HTTP binding), how do I get the size of the payload so we can make security decision to process the request or not (because it may cause resource constraint)

Re: SOAP Payload size in a request

Chunking can be turned off (search the CXF user's guide for that) always giving you a Content-Length field as a result--is that an option for you? Glen Mahesh Seshan wrote: Hello, We use Apache CXF 2.1.3 as our SOAP engine and Apache Tomcat 6 to handle HTTP. When a SOAP requests is

Re: support for configuring addressing in the dynamic client

Thanks Eoghan for your inputs. My requirement is to use addressing in the dynamic client which does not seem to work. I am not sure if this is a limitation of DynamicClientFactory. I hope CXF ws-addressing feature can interoperate with non-CXF services too. Appreciate your help. -Arul

How to combine JAX-RS and JAX-WS with ApacheCXF2.1+Spring

Hi; I've followed what is said in the ApacheCXF UserGuide; The Build with maven2 is successful, but everyTime I want to deploy it on Tomcat it's returns : ECHEC - L'application pour le chemin de contexte /cxf-rest-example-1.0 n'a pas pus etredémarrée any Idea!! thanks in advance -- Tigre et

NullPointerException while using wsdl2java with asynchronous binding

Hi, I followed the instructions on: http://cwiki.apache.org/CXF20DOC/developing-a-consumer.html to generate asynchronous client stub code. I took the wsdl example on the page, make this change: wsdl:operation name=greetMeSometime soap:operation style=document/ wsdl:input

NullPointerException while using wsdl2java with asynchronous binding

Hi, I followed the instructions on: http://cwiki.apache.org/CXF20DOC/developing-a-consumer.html to generate asynchronous client stub code. I took the wsdl example on the page, make this change: wsdl:operation name=greetMeSometime soap:operation style=document/ wsdl:input

Re: Specifying fields to include/exclude from return XML

Hrmm, how about dynamically? Really what I am going for is something like: http://myapiserver.com/api/contacts?fields=id So this: contact id0/id firstNameA/firstName lastNameB/lastName /contact turns into this: contact id0/id /contact Although, in my particular case, I wouldn't just

Re: Specifying fields to include/exclude from return XML

Isn't this for what minOccurs='0' was invented? In JAXB, I think that's required=false, nillable=true or some such. On Thu, Mar 5, 2009 at 6:00 PM, David Castro apudcas...@entwash.org wrote: Hrmm, how about dynamically?  Really what I am going for is something like:

Re: SOAP Payload size in a request

With chunking mode, there isn't a way to determine the length without reading the entire message, which would break streaming and affect performance. The BEST way to deal with this would be to write an interceptor that lives VERY early in the chain, takes the InputStream and wrappers it with

RE: Specifying fields to include/exclude from return XML

In XFire, you could always use the annotation @IgnoreProperty (see org.codehaus.xfire.aegis.type.java5). However, for whatever reason, it appears Apache CXF doesn't want to support it any longer and is currently marked as deprecated, but still in there for backward compatibility. Hopefully,

Re: Specifying fields to include/exclude from return XML

Amazon web services have made a science of this with its response group feature[1]--when you make a SOAP request, you also specify how much of a potentially many-fielded response you get in exchange. Anything you don't choose to receive back is returned to you as empty tags. Glen [1]