[
https://issues.apache.org/jira/browse/CXF-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800286#action_12800286
]
Daniel Kulp commented on CXF-2605:
----------------------------------
Thanks for the testcase.
There are two issues:
1) In your interface, you are using WebParam annotations like:
{code}
@WebParam(name= "in0", targetNamespace = "http://filter.corymbus.db.com";)
{code}
The targetNamespace is telling the runtime to look for a qualified element
there. However, the client is sending it unqualified. There definitely was
a bug in early versions of CXF that more or less ignored that targetNamespace
which is probably why it worked OK with 2.1.1. If you remove that
targetNamespace attribute, everything works perfect. Likewise for the
@WebResult.
2) This test case DID identify a bug though. In this case, the element in the
schema SHOULD have had a
{code}
form="qualified"
{code}
attribute on it to mark that it was supposed to be qualified. I just fixed
that and am testing the fix now.
> 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
> 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.
