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 2006/12/01 19:43:21 UTC
[jira] Created: (AXIS2-1805) JAX-WS JAXBContext construction with
package contextPath
JAX-WS JAXBContext construction with package contextPath
--------------------------------------------------------
Key: AXIS2-1805
URL: http://issues.apache.org/jira/browse/AXIS2-1805
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: jaxws
Reporter: Rich Scheuerle
There are two ways to construct a JAXBContext..
1) newInstance constructor that takes an Class[] of all of the JAXB classes.
2) newInstance constructor tha takes a String that is a colon separted list of packages.
Currently jaxws does (1), which is error prone.
However we encountered problems in the past using (2). We think the problems with (2) were due to the fact that wsgen does not generate ObjectFactory classes in each package.
This issue is opened to investigate possible solutions. Here are some ideas:
A) Write a test that deliberately removes the ObjectFactory and packageinfo from a JAXB package and verify that (2) does not work.
B) Change the code to look for ObjectFactory and packageinfo in each package. If they exist use approach (2) otherwise fallback to approach (1).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1805) JAX-WS JAXBContext construction with
package contextPath
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1805?page=all ]
Rich Scheuerle updated AXIS2-1805:
----------------------------------
Description:
There are two ways to construct a JAXBContext..
1) newInstance constructor that takes an Class[] of all of the JAXB classes.
2) newInstance constructor tha takes a String that is a colon separated list of packages.
Currently jaxws does (1), which is error prone.
However we encountered problems in the past using (2). We think the problems with (2) were due to the fact that wsgen does not generate ObjectFactory classes in each package.
This issue is opened to investigate possible solutions. Here are some ideas:
A) Write a test that deliberately removes the ObjectFactory and packageinfo from a JAXB package and verify that (2) does not work.
B) Change the code to look for ObjectFactory and packageinfo in each package. If they exist use approach (2) otherwise fallback to approach (1).
was:
There are two ways to construct a JAXBContext..
1) newInstance constructor that takes an Class[] of all of the JAXB classes.
2) newInstance constructor tha takes a String that is a colon separted list of packages.
Currently jaxws does (1), which is error prone.
However we encountered problems in the past using (2). We think the problems with (2) were due to the fact that wsgen does not generate ObjectFactory classes in each package.
This issue is opened to investigate possible solutions. Here are some ideas:
A) Write a test that deliberately removes the ObjectFactory and packageinfo from a JAXB package and verify that (2) does not work.
B) Change the code to look for ObjectFactory and packageinfo in each package. If they exist use approach (2) otherwise fallback to approach (1).
> JAX-WS JAXBContext construction with package contextPath
> --------------------------------------------------------
>
> Key: AXIS2-1805
> URL: http://issues.apache.org/jira/browse/AXIS2-1805
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Rich Scheuerle
>
> There are two ways to construct a JAXBContext..
> 1) newInstance constructor that takes an Class[] of all of the JAXB classes.
> 2) newInstance constructor tha takes a String that is a colon separated list of packages.
> Currently jaxws does (1), which is error prone.
> However we encountered problems in the past using (2). We think the problems with (2) were due to the fact that wsgen does not generate ObjectFactory classes in each package.
> This issue is opened to investigate possible solutions. Here are some ideas:
> A) Write a test that deliberately removes the ObjectFactory and packageinfo from a JAXB package and verify that (2) does not work.
> B) Change the code to look for ObjectFactory and packageinfo in each package. If they exist use approach (2) otherwise fallback to approach (1).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1805) JAX-WS JAXBContext construction with
package contextPath
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1805?page=all ]
Rich Scheuerle updated AXIS2-1805:
----------------------------------
Attachment: JAXBUtils.java
Committed to SVN Revision=481394
> JAX-WS JAXBContext construction with package contextPath
> --------------------------------------------------------
>
> Key: AXIS2-1805
> URL: http://issues.apache.org/jira/browse/AXIS2-1805
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Rich Scheuerle
> Attachments: JAXBUtils.java
>
>
> There are two ways to construct a JAXBContext..
> 1) newInstance constructor that takes an Class[] of all of the JAXB classes.
> 2) newInstance constructor tha takes a String that is a colon separated list of packages.
> Currently jaxws does (1), which is error prone.
> However we encountered problems in the past using (2). We think the problems with (2) were due to the fact that wsgen does not generate ObjectFactory classes in each package.
> This issue is opened to investigate possible solutions. Here are some ideas:
> A) Write a test that deliberately removes the ObjectFactory and packageinfo from a JAXB package and verify that (2) does not work.
> B) Change the code to look for ObjectFactory and packageinfo in each package. If they exist use approach (2) otherwise fallback to approach (1).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-1805) JAX-WS JAXBContext construction with
package contextPath
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1805?page=all ]
Rich Scheuerle resolved AXIS2-1805.
-----------------------------------
Resolution: Fixed
> JAX-WS JAXBContext construction with package contextPath
> --------------------------------------------------------
>
> Key: AXIS2-1805
> URL: http://issues.apache.org/jira/browse/AXIS2-1805
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Rich Scheuerle
> Attachments: JAXBUtils.java
>
>
> There are two ways to construct a JAXBContext..
> 1) newInstance constructor that takes an Class[] of all of the JAXB classes.
> 2) newInstance constructor tha takes a String that is a colon separated list of packages.
> Currently jaxws does (1), which is error prone.
> However we encountered problems in the past using (2). We think the problems with (2) were due to the fact that wsgen does not generate ObjectFactory classes in each package.
> Solution: Change the code to look for ObjectFactory and packageinfo in each package. If they exist use approach (2) otherwise fallback to approach (1).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1805) JAX-WS JAXBContext construction with
package contextPath
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1805?page=all ]
Rich Scheuerle updated AXIS2-1805:
----------------------------------
Description:
There are two ways to construct a JAXBContext..
1) newInstance constructor that takes an Class[] of all of the JAXB classes.
2) newInstance constructor tha takes a String that is a colon separated list of packages.
Currently jaxws does (1), which is error prone.
However we encountered problems in the past using (2). We think the problems with (2) were due to the fact that wsgen does not generate ObjectFactory classes in each package.
Solution: Change the code to look for ObjectFactory and packageinfo in each package. If they exist use approach (2) otherwise fallback to approach (1).
was:
There are two ways to construct a JAXBContext..
1) newInstance constructor that takes an Class[] of all of the JAXB classes.
2) newInstance constructor tha takes a String that is a colon separated list of packages.
Currently jaxws does (1), which is error prone.
However we encountered problems in the past using (2). We think the problems with (2) were due to the fact that wsgen does not generate ObjectFactory classes in each package.
This issue is opened to investigate possible solutions. Here are some ideas:
A) Write a test that deliberately removes the ObjectFactory and packageinfo from a JAXB package and verify that (2) does not work.
B) Change the code to look for ObjectFactory and packageinfo in each package. If they exist use approach (2) otherwise fallback to approach (1).
> JAX-WS JAXBContext construction with package contextPath
> --------------------------------------------------------
>
> Key: AXIS2-1805
> URL: http://issues.apache.org/jira/browse/AXIS2-1805
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Rich Scheuerle
> Attachments: JAXBUtils.java
>
>
> There are two ways to construct a JAXBContext..
> 1) newInstance constructor that takes an Class[] of all of the JAXB classes.
> 2) newInstance constructor tha takes a String that is a colon separated list of packages.
> Currently jaxws does (1), which is error prone.
> However we encountered problems in the past using (2). We think the problems with (2) were due to the fact that wsgen does not generate ObjectFactory classes in each package.
> Solution: Change the code to look for ObjectFactory and packageinfo in each package. If they exist use approach (2) otherwise fallback to approach (1).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org