Yes, I am using the jaxws client, and also SOAP UI.  I get the same problem
with both front ends.
I used java2wsdl.  This is the message that is getting sent:
<soap:Envelope
        xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
        <soap:Body>
                <ns2:createPersonTypeInfo
                        
xmlns:ns2="http://student.kuali.org/poc/wsdl/personidentity/person";>
                        <personTypeInfo name="PersonType1">
                                <setList>
                                        <set name="AttrSet1">
                                                <attributeTypes name="Attr1">
                                                        <type>STRING</type>
                                                        <label>Attribute 1 
Label</label>
                                                </attributeTypes>
                                                <attributeTypes name="Attr2">
                                                        <type>DATE</type>
                                                        <label>Attribute 2 
Label</label>
                                                </attributeTypes>
                                        </set>
                                </setList>
                        </ns2:personTypeInfo>
                </ns2:createPersonTypeInfo>
        </soap:Body>
</soap:Envelope>
This results in a null parameter being set in the DocLiteralInInterceptor,
but when I add the namespace and change the line <personTypeInfo
name="PersonType1"> to <ns2:personTypeInfo name="PersonType1">, the
parameters get set correctly. Strange!

I removed the @XmlRootElement from my PersonTypeInfo class and it works now
without the namespace prefix.



Glen Mazza-2 wrote:
> 
> Are you using CXF's simple front end instead of its jaxws front end?  I
> think you want the latter for CXF.  That might explain the problem.
> (Also, did you run wsdl2java to generate the JAXB mappings to the XSDs
> in the WSDL?)  
> 
> Glen
> 
> Am Dienstag, den 01.04.2008, 12:21 -0700 schrieb depstei2:
>> Hello, I have a web service that works fine when using cxf on Tomcat, but
>> when I try to deploy on embedded jetty using the
>> org.apache.cxf.transport.servlet.CXFServlet, I get null parameters in my
>> service method calls, even though the cxf logger shows that the payloads
>> of
>> the messages contain correct data.  When I switch to using sun's
>> jaxws-rt's
>> com.sun.xml.ws.transport.http.servlet.WSSpringServlet, the service will
>> work
>> as expected on jetty embedded. 
>> 
>> The null parameter does not occur when the parameter is a primitive type,
>> but happens for all other parameter types.
>> 
>> Has anyone come across this problem?  Any ideas?  
>> 
>> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Null-paramaters-using-CXF-when-deployed-to-jetty-with-CXFServlet-tp16422010p16447084.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to