You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2009/06/18 14:53:07 UTC
[jira] Created: (AXIS2-4396) JAX-WS:@XmlSeeAlso annotations are not
being processed on an SEI, which causes an application failure
JAX-WS:@XmlSeeAlso annotations are not being processed on an SEI, which causes an application failure
-----------------------------------------------------------------------------------------------------
Key: AXIS2-4396
URL: https://issues.apache.org/jira/browse/AXIS2-4396
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Reporter: Rich Scheuerle
Assignee: Rich Scheuerle
A JAX-WS Service Endpoint Interface (SEI) may contain @XmlSeeAlso annotations. These annotations inform the runtime about the existence of specific classes that are not directly referencedby the web service. The JAX-WS runtime uses the annotations to determine how to marshal or unmarshal data objects.
Due to a problem in the JAX-WS runtime, these annotations are not being processed correctly. This may cause the JAX-WS runtime to unmarshal the data objects as Data Object Model (DOM) Elements instead of JAXB objects. When the web service application attempts to process the data object an error may occur indicating that the DOM Element is incompatible with a user class. Example:
javax.xml.ws.soap.SOAPFaultException:
org.apache.xerces.dom.ElementNSImpl incompatible with some_class
org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils
...
The root of the problem is that the SEI is not being correctly located for the scenario where the web service implementation does not implment the SEI but instead
uses the @WebService endpointInterface parameter to designate the SEI.
The solution is to locate and load the SEI for this scenario, and process the @XmlSeeAlso annotations on the SEI.
I am completing my testing on the solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4396) JAX-WS:@XmlSeeAlso annotations are
not being processed on an SEI, which causes an application failure
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4396.
-----------------------------------
Resolution: Fixed
Committed Revision: 786049
> JAX-WS:@XmlSeeAlso annotations are not being processed on an SEI, which causes an application failure
> -----------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4396
> URL: https://issues.apache.org/jira/browse/AXIS2-4396
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> A JAX-WS Service Endpoint Interface (SEI) may contain @XmlSeeAlso annotations. These annotations inform the runtime about the existence of specific classes that are not directly referencedby the web service. The JAX-WS runtime uses the annotations to determine how to marshal or unmarshal data objects.
>
> Due to a problem in the JAX-WS runtime, these annotations are not being processed correctly. This may cause the JAX-WS runtime to unmarshal the data objects as Data Object Model (DOM) Elements instead of JAXB objects. When the web service application attempts to process the data object an error may occur indicating that the DOM Element is incompatible with a user class. Example:
>
> javax.xml.ws.soap.SOAPFaultException:
> org.apache.xerces.dom.ElementNSImpl incompatible with some_class
> org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils
> ...
> The root of the problem is that the SEI is not being correctly located for the scenario where the web service implementation does not implment the SEI but instead
> uses the @WebService endpointInterface parameter to designate the SEI.
> The solution is to locate and load the SEI for this scenario, and process the @XmlSeeAlso annotations on the SEI.
> I am completing my testing on the solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4396) JAX-WS:@XmlSeeAlso annotations are not
being processed on an SEI, which causes an application failure
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIS2-4396:
-----------------------------------
Fix Version/s: 1.6
> JAX-WS:@XmlSeeAlso annotations are not being processed on an SEI, which causes an application failure
> -----------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4396
> URL: https://issues.apache.org/jira/browse/AXIS2-4396
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Fix For: 1.6
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> A JAX-WS Service Endpoint Interface (SEI) may contain @XmlSeeAlso annotations. These annotations inform the runtime about the existence of specific classes that are not directly referencedby the web service. The JAX-WS runtime uses the annotations to determine how to marshal or unmarshal data objects.
>
> Due to a problem in the JAX-WS runtime, these annotations are not being processed correctly. This may cause the JAX-WS runtime to unmarshal the data objects as Data Object Model (DOM) Elements instead of JAXB objects. When the web service application attempts to process the data object an error may occur indicating that the DOM Element is incompatible with a user class. Example:
>
> javax.xml.ws.soap.SOAPFaultException:
> org.apache.xerces.dom.ElementNSImpl incompatible with some_class
> org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils
> ...
> The root of the problem is that the SEI is not being correctly located for the scenario where the web service implementation does not implment the SEI but instead
> uses the @WebService endpointInterface parameter to designate the SEI.
> The solution is to locate and load the SEI for this scenario, and process the @XmlSeeAlso annotations on the SEI.
> I am completing my testing on the solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.