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 2010/05/10 17:38:18 UTC
[jira] Created: (AXIS2-4708) JAX-WS: JAXBContext construction
should prefer JAXB classes that are directly referenced.
JAX-WS: JAXBContext construction should prefer JAXB classes that are directly referenced.
-----------------------------------------------------------------------------------------
Key: AXIS2-4708
URL: https://issues.apache.org/jira/browse/AXIS2-4708
Project: Axis2
Issue Type: Bug
Reporter: Rich Scheuerle
Assignee: Rich Scheuerle
Summary:
The JAX-WS runtime may unmarshal data into incorrect JAXB java objects in the following scenario:
-----------------------------
Failing Scenario:
1) The JAX-WS web service methods reference JAXB classes from different packages (i.e. a.Bean2 and b.Bean1).
2) Both packages contain JAXB classes for the same namespace. (i.e. a.Bean2 and b.Bean1 are both generated from a schema whose target namespace is urn:sample)
3) Both packages contain other JAXB classes with similar names (i.e. b.Bean2 and a.Bean1)
In this scenario, the JAX-WS runtime may unmarshal data into the wrong JAXB object. For example, the data may be
unmarshaled into an a.Bean1 object even though b.Bean1 is referenced in the JAX-WS web service.
This is an unusual scenario, and will occur if the customer provides hand-written JAXB classes instead of using RAD wsimport tooling.
------------------------
Proposed Solution:
I am currently testing a solution that does the following:
* keeps track of the classes that are directly referenced.
* when the jaxbcontext is created from classes, the directly referenced classes are prefered.
I also have a unit fvt test that mimics the failing case.
--
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
[jira] Resolved: (AXIS2-4708) JAX-WS: JAXBContext construction
should prefer JAXB classes that are directly referenced.
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4708.
-----------------------------------
Resolution: Fixed
> JAX-WS: JAXBContext construction should prefer JAXB classes that are directly referenced.
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2-4708
> URL: https://issues.apache.org/jira/browse/AXIS2-4708
> Project: Axis2
> Issue Type: Bug
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Summary:
> The JAX-WS runtime may unmarshal data into incorrect JAXB java objects in the following scenario:
> -----------------------------
> Failing Scenario:
> 1) The JAX-WS web service methods reference JAXB classes from different packages (i.e. a.Bean2 and b.Bean1).
> 2) Both packages contain JAXB classes for the same namespace. (i.e. a.Bean2 and b.Bean1 are both generated from a schema whose target namespace is urn:sample)
> 3) Both packages contain other JAXB classes with similar names (i.e. b.Bean2 and a.Bean1)
> In this scenario, the JAX-WS runtime may unmarshal data into the wrong JAXB object. For example, the data may be
> unmarshaled into an a.Bean1 object even though b.Bean1 is referenced in the JAX-WS web service.
> This is an unusual scenario, and will occur if the customer provides hand-written JAXB classes instead of using RAD wsimport tooling.
> ------------------------
> Proposed Solution:
> I am currently testing a solution that does the following:
> * keeps track of the classes that are directly referenced.
> * when the jaxbcontext is created from classes, the directly referenced classes are prefered.
> I also have a unit fvt test that mimics the failing case.
--
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
[jira] Resolved: (AXIS2-4708) JAX-WS: JAXBContext construction
should prefer JAXB classes that are directly referenced.
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4708.
-----------------------------------
Resolution: Fixed
> JAX-WS: JAXBContext construction should prefer JAXB classes that are directly referenced.
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2-4708
> URL: https://issues.apache.org/jira/browse/AXIS2-4708
> Project: Axis2
> Issue Type: Bug
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Summary:
> The JAX-WS runtime may unmarshal data into incorrect JAXB java objects in the following scenario:
> -----------------------------
> Failing Scenario:
> 1) The JAX-WS web service methods reference JAXB classes from different packages (i.e. a.Bean2 and b.Bean1).
> 2) Both packages contain JAXB classes for the same namespace. (i.e. a.Bean2 and b.Bean1 are both generated from a schema whose target namespace is urn:sample)
> 3) Both packages contain other JAXB classes with similar names (i.e. b.Bean2 and a.Bean1)
> In this scenario, the JAX-WS runtime may unmarshal data into the wrong JAXB object. For example, the data may be
> unmarshaled into an a.Bean1 object even though b.Bean1 is referenced in the JAX-WS web service.
> This is an unusual scenario, and will occur if the customer provides hand-written JAXB classes instead of using RAD wsimport tooling.
> ------------------------
> Proposed Solution:
> I am currently testing a solution that does the following:
> * keeps track of the classes that are directly referenced.
> * when the jaxbcontext is created from classes, the directly referenced classes are prefered.
> I also have a unit fvt test that mimics the failing case.
--
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
[jira] Resolved: (AXIS2-4708) JAX-WS: JAXBContext construction
should prefer JAXB classes that are directly referenced.
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4708.
-----------------------------------
Resolution: Fixed
> JAX-WS: JAXBContext construction should prefer JAXB classes that are directly referenced.
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2-4708
> URL: https://issues.apache.org/jira/browse/AXIS2-4708
> Project: Axis2
> Issue Type: Bug
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Summary:
> The JAX-WS runtime may unmarshal data into incorrect JAXB java objects in the following scenario:
> -----------------------------
> Failing Scenario:
> 1) The JAX-WS web service methods reference JAXB classes from different packages (i.e. a.Bean2 and b.Bean1).
> 2) Both packages contain JAXB classes for the same namespace. (i.e. a.Bean2 and b.Bean1 are both generated from a schema whose target namespace is urn:sample)
> 3) Both packages contain other JAXB classes with similar names (i.e. b.Bean2 and a.Bean1)
> In this scenario, the JAX-WS runtime may unmarshal data into the wrong JAXB object. For example, the data may be
> unmarshaled into an a.Bean1 object even though b.Bean1 is referenced in the JAX-WS web service.
> This is an unusual scenario, and will occur if the customer provides hand-written JAXB classes instead of using RAD wsimport tooling.
> ------------------------
> Proposed Solution:
> I am currently testing a solution that does the following:
> * keeps track of the classes that are directly referenced.
> * when the jaxbcontext is created from classes, the directly referenced classes are prefered.
> I also have a unit fvt test that mimics the failing case.
--
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
[jira] Resolved: (AXIS2-4708) JAX-WS: JAXBContext construction
should prefer JAXB classes that are directly referenced.
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4708.
-----------------------------------
Resolution: Fixed
> JAX-WS: JAXBContext construction should prefer JAXB classes that are directly referenced.
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2-4708
> URL: https://issues.apache.org/jira/browse/AXIS2-4708
> Project: Axis2
> Issue Type: Bug
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Summary:
> The JAX-WS runtime may unmarshal data into incorrect JAXB java objects in the following scenario:
> -----------------------------
> Failing Scenario:
> 1) The JAX-WS web service methods reference JAXB classes from different packages (i.e. a.Bean2 and b.Bean1).
> 2) Both packages contain JAXB classes for the same namespace. (i.e. a.Bean2 and b.Bean1 are both generated from a schema whose target namespace is urn:sample)
> 3) Both packages contain other JAXB classes with similar names (i.e. b.Bean2 and a.Bean1)
> In this scenario, the JAX-WS runtime may unmarshal data into the wrong JAXB object. For example, the data may be
> unmarshaled into an a.Bean1 object even though b.Bean1 is referenced in the JAX-WS web service.
> This is an unusual scenario, and will occur if the customer provides hand-written JAXB classes instead of using RAD wsimport tooling.
> ------------------------
> Proposed Solution:
> I am currently testing a solution that does the following:
> * keeps track of the classes that are directly referenced.
> * when the jaxbcontext is created from classes, the directly referenced classes are prefered.
> I also have a unit fvt test that mimics the failing case.
--
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
[jira] Resolved: (AXIS2-4708) JAX-WS: JAXBContext construction
should prefer JAXB classes that are directly referenced.
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4708.
-----------------------------------
Resolution: Fixed
> JAX-WS: JAXBContext construction should prefer JAXB classes that are directly referenced.
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2-4708
> URL: https://issues.apache.org/jira/browse/AXIS2-4708
> Project: Axis2
> Issue Type: Bug
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Summary:
> The JAX-WS runtime may unmarshal data into incorrect JAXB java objects in the following scenario:
> -----------------------------
> Failing Scenario:
> 1) The JAX-WS web service methods reference JAXB classes from different packages (i.e. a.Bean2 and b.Bean1).
> 2) Both packages contain JAXB classes for the same namespace. (i.e. a.Bean2 and b.Bean1 are both generated from a schema whose target namespace is urn:sample)
> 3) Both packages contain other JAXB classes with similar names (i.e. b.Bean2 and a.Bean1)
> In this scenario, the JAX-WS runtime may unmarshal data into the wrong JAXB object. For example, the data may be
> unmarshaled into an a.Bean1 object even though b.Bean1 is referenced in the JAX-WS web service.
> This is an unusual scenario, and will occur if the customer provides hand-written JAXB classes instead of using RAD wsimport tooling.
> ------------------------
> Proposed Solution:
> I am currently testing a solution that does the following:
> * keeps track of the classes that are directly referenced.
> * when the jaxbcontext is created from classes, the directly referenced classes are prefered.
> I also have a unit fvt test that mimics the failing case.
--
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