Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Message-ID: <28164016.17811272909835811.JavaMail.jira@thor>
Date: Mon, 3 May 2010 14:03:55 -0400 (EDT)
From: "Rich Scheuerle (JIRA)" <jira@apache.org>
To: java-dev@axis.apache.org
Subject: [jira] Created: (AXIS2-4700) JAX-WS: Wrapper defaulting is wrong
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

JAX-WS: Wrapper defaulting is wrong
-----------------------------------

                 Key: AXIS2-4700
                 URL: https://issues.apache.org/jira/browse/AXIS2-4700
             Project: Axis2
          Issue Type: Bug
          Components: jaxws
            Reporter: Rich Scheuerle
            Assignee: Rich Scheuerle


A JAX-WS Web service client or provider may receive an UnmarshalException "unexpected element" error when it receives 
an inbound message.   The error indicates that a problem has occurred converting the incoming message into the customer's JAXB data object.

Here is an example message:

Cause:javax.xml.bind.UnmarshalException
- with linked exception:
[javax.xml.bind.UnmarshalException: unexpected element
(uri:"http://my.test/", local:"myOperation"). Expected elements
are
<{http://my.test/}myOperationResponse>]


All of the following must be true for this error to occur:
  A) The JAX-WS Web service must use the document/literal 
wrapped style.
  B) The method being invoked must not have the 
@RequestWrapper or @ResponseWrapper annotation.
  C) The customer has provided a wrapper bean in the expected 
package (i.e. my.test.jaxws.MyOperationResponse).
  D) The customer has provided another (non-wrapper bean) in 
the same package as the Web service interface (i.e. 
my.test.MyOperationResponse)

Solution:
When a JAX-WS Web service method does not have the @RequestWrapper or @ResponseWrapper annotation, the JAX-WS project uses an algorithm to locate the wrapper classes.

The algorithm should first look in a sub-package named "jaxws" for the wrapper bean.  If the wrapper bean is not found, then it should look in the package associated with the target namespace.

The error occurred because the algorithm was examining the packages in the wrong order.  I am making a correction, and will commit code later today.


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


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org