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/11/11 16:22:37 UTC
[jira] Created: (AXIS2-1678) JAX-WS Block representation of JAXB
JAX-WS Block representation of JAXB
-----------------------------------
Key: AXIS2-1678
URL: http://issues.apache.org/jira/browse/AXIS2-1678
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Rich Scheuerle
The JAXB Message contains objects called Blocks.
A block is a representation of an xml document , which means that it must have a single instance element defined by a root element.
A block can have a number of different backing representations.
One of these representations is a JAXB object.
I am adding assertions and code to ensure that the JAXB Object that is used for a block can be rendered as an "element".
(i.e. the JAXBObject must either be a JAXBElement or it must be an object that has @XmlRootElement defined).
The second change is to the JAXBBlockContext. You create a JAXBBlockContext from either the JAXBContext from the user (only dispatch case) or you give the JAXBBlockContext a set of "context packages"....which are then used to create or get an appropriate JAXBContext.
This change is needed to ensure that we are popluating the context with the appropriate packages.
These changes lead to changes in the classes the reference this constructs: Dispatch and MethodMarshaller classes.
These changes revealed some inconsistencies between "element rendered" JAXB Objects and "type rendered" JAXBObjects.
For example, a JAXB Object with @XMLRootElement represents both a "element and a type" rendering.
A JAXBElement Object represents the "element" rendering, and the JAXBElement's getValue() method returns the "type" rendering.
There are several places in the code where it wants the "element" rendering...and other places want the "type" rendering. I tried
to correct these as I found them. We are considering some redesign here to address these kinds of concerns.
--
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] Assigned: (AXIS2-1678) JAX-WS Block representation of JAXB
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1678?page=all ]
Rich Scheuerle reassigned AXIS2-1678:
-------------------------------------
Assignee: Rich Scheuerle
> JAX-WS Block representation of JAXB
> -----------------------------------
>
> Key: AXIS2-1678
> URL: http://issues.apache.org/jira/browse/AXIS2-1678
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assigned To: Rich Scheuerle
>
> The JAXB Message contains objects called Blocks.
> A block is a representation of an xml document , which means that it must have a single instance element defined by a root element.
> A block can have a number of different backing representations.
> One of these representations is a JAXB object.
> I am adding assertions and code to ensure that the JAXB Object that is used for a block can be rendered as an "element".
> (i.e. the JAXBObject must either be a JAXBElement or it must be an object that has @XmlRootElement defined).
> The second change is to the JAXBBlockContext. You create a JAXBBlockContext from either the JAXBContext from the user (only dispatch case) or you give the JAXBBlockContext a set of "context packages"....which are then used to create or get an appropriate JAXBContext.
> This change is needed to ensure that we are popluating the context with the appropriate packages.
> These changes lead to changes in the classes the reference this constructs: Dispatch and MethodMarshaller classes.
> These changes revealed some inconsistencies between "element rendered" JAXB Objects and "type rendered" JAXBObjects.
> For example, a JAXB Object with @XMLRootElement represents both a "element and a type" rendering.
> A JAXBElement Object represents the "element" rendering, and the JAXBElement's getValue() method returns the "type" rendering.
> There are several places in the code where it wants the "element" rendering...and other places want the "type" rendering. I tried
> to correct these as I found them. We are considering some redesign here to address these kinds of concerns.
--
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-1678) JAX-WS Block representation of JAXB
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1678?page=all ]
Rich Scheuerle updated AXIS2-1678:
----------------------------------
Component/s: jaxws
> JAX-WS Block representation of JAXB
> -----------------------------------
>
> Key: AXIS2-1678
> URL: http://issues.apache.org/jira/browse/AXIS2-1678
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
>
> The JAXB Message contains objects called Blocks.
> A block is a representation of an xml document , which means that it must have a single instance element defined by a root element.
> A block can have a number of different backing representations.
> One of these representations is a JAXB object.
> I am adding assertions and code to ensure that the JAXB Object that is used for a block can be rendered as an "element".
> (i.e. the JAXBObject must either be a JAXBElement or it must be an object that has @XmlRootElement defined).
> The second change is to the JAXBBlockContext. You create a JAXBBlockContext from either the JAXBContext from the user (only dispatch case) or you give the JAXBBlockContext a set of "context packages"....which are then used to create or get an appropriate JAXBContext.
> This change is needed to ensure that we are popluating the context with the appropriate packages.
> These changes lead to changes in the classes the reference this constructs: Dispatch and MethodMarshaller classes.
> These changes revealed some inconsistencies between "element rendered" JAXB Objects and "type rendered" JAXBObjects.
> For example, a JAXB Object with @XMLRootElement represents both a "element and a type" rendering.
> A JAXBElement Object represents the "element" rendering, and the JAXBElement's getValue() method returns the "type" rendering.
> There are several places in the code where it wants the "element" rendering...and other places want the "type" rendering. I tried
> to correct these as I found them. We are considering some redesign here to address these kinds of concerns.
--
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-1678) JAX-WS Block representation of JAXB
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1678?page=all ]
Rich Scheuerle updated AXIS2-1678:
----------------------------------
Attachment: patch.txt
> JAX-WS Block representation of JAXB
> -----------------------------------
>
> Key: AXIS2-1678
> URL: http://issues.apache.org/jira/browse/AXIS2-1678
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assigned To: Rich Scheuerle
> Attachments: patch.txt
>
>
> The JAXB Message contains objects called Blocks.
> A block is a representation of an xml document , which means that it must have a single instance element defined by a root element.
> A block can have a number of different backing representations.
> One of these representations is a JAXB object.
> I am adding assertions and code to ensure that the JAXB Object that is used for a block can be rendered as an "element".
> (i.e. the JAXBObject must either be a JAXBElement or it must be an object that has @XmlRootElement defined).
> The second change is to the JAXBBlockContext. You create a JAXBBlockContext from either the JAXBContext from the user (only dispatch case) or you give the JAXBBlockContext a set of "context packages"....which are then used to create or get an appropriate JAXBContext.
> This change is needed to ensure that we are popluating the context with the appropriate packages.
> These changes lead to changes in the classes the reference this constructs: Dispatch and MethodMarshaller classes.
> These changes revealed some inconsistencies between "element rendered" JAXB Objects and "type rendered" JAXBObjects.
> For example, a JAXB Object with @XMLRootElement represents both a "element and a type" rendering.
> A JAXBElement Object represents the "element" rendering, and the JAXBElement's getValue() method returns the "type" rendering.
> There are several places in the code where it wants the "element" rendering...and other places want the "type" rendering. I tried
> to correct these as I found them. We are considering some redesign here to address these kinds of concerns.
--
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-1678) JAX-WS Block representation of JAXB
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1678?page=all ]
Rich Scheuerle resolved AXIS2-1678.
-----------------------------------
Resolution: Fixed
Checked into SVN
> JAX-WS Block representation of JAXB
> -----------------------------------
>
> Key: AXIS2-1678
> URL: http://issues.apache.org/jira/browse/AXIS2-1678
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assigned To: Rich Scheuerle
> Attachments: patch.txt
>
>
> The JAXB Message contains objects called Blocks.
> A block is a representation of an xml document , which means that it must have a single instance element defined by a root element.
> A block can have a number of different backing representations.
> One of these representations is a JAXB object.
> I am adding assertions and code to ensure that the JAXB Object that is used for a block can be rendered as an "element".
> (i.e. the JAXBObject must either be a JAXBElement or it must be an object that has @XmlRootElement defined).
> The second change is to the JAXBBlockContext. You create a JAXBBlockContext from either the JAXBContext from the user (only dispatch case) or you give the JAXBBlockContext a set of "context packages"....which are then used to create or get an appropriate JAXBContext.
> This change is needed to ensure that we are popluating the context with the appropriate packages.
> These changes lead to changes in the classes the reference this constructs: Dispatch and MethodMarshaller classes.
> These changes revealed some inconsistencies between "element rendered" JAXB Objects and "type rendered" JAXBObjects.
> For example, a JAXB Object with @XMLRootElement represents both a "element and a type" rendering.
> A JAXBElement Object represents the "element" rendering, and the JAXBElement's getValue() method returns the "type" rendering.
> There are several places in the code where it wants the "element" rendering...and other places want the "type" rendering. I tried
> to correct these as I found them. We are considering some redesign here to address these kinds of concerns.
--
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