[ 
https://issues.apache.org/jira/browse/CXF-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800745#action_12800745
 ] 

Daniel Kulp commented on CXF-2605:
----------------------------------


The "status" schema is defined as:
{code:xml}
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" 
targetNamespace="http://status.service.corymbus.db.com"; 
xmlns:ns0="http://filter.corymbus.db.com"; 
xmlns:ns1="http://datasynapse.corymbus.db.com"; 
xmlns:ns2="http://exception.corymbus.db.com"; 
xmlns:tns="http://status.service.corymbus.db.com"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
{code}
with the unqualified elements.   In that schema, with the targetNamespace 
defined on the WebParam, in the "getRequest" type needed to have its "in0" 
element set to:
{code:xml}
<xsd:element minOccurs="0" name="in0" form="qualified" 
type="ns0:FilterArguments" />
{code}
or similar to mark it qualified since that is what the runtime was expecting.

The namespace on the ResponseWrapper is different.   That defines what 
namespace the top level element is put into.   The top level elements are 
always qualified so it's mostly just a "which schema to stick it in" thing.






> Object argument is passed as null
> ---------------------------------
>
>                 Key: CXF-2605
>                 URL: https://issues.apache.org/jira/browse/CXF-2605
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.2.4
>            Reporter: Ravi Sukheja
>             Fix For: 2.1.9, 2.2.6
>
>         Attachments: package-info.java, StatusService.xml, 
> StatusService_211.xml
>
>
> Hi,
> We are using CXF-2.1.1 for our webservices and rest services, recently I 
> upgraded it to 2.2.4 as there was bug 2ith 2.1.1 when you go to /services to 
> view the list of all webservices and rest services. Upgrading to 2.2.4 seems 
> to fix that problem, but one of our webservice has stopped working, client is 
> passing the right object argument, but the service is getting null. I don't 
> know what the problem is. Any help would be appreciated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to