You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "Ajith Harshana Ranabahu (JIRA)" <xm...@xml.apache.org> on 2006/04/24 07:50:06 UTC
[jira] Created: (XMLBEANS-269) provider wrapper for xsd:any
provider wrapper for xsd:any
----------------------------
Key: XMLBEANS-269
URL: http://issues.apache.org/jira/browse/XMLBEANS-269
Project: XMLBeans
Type: Improvement
Reporter: Ajith Harshana Ranabahu
This issue has been reported in the Axis2 Jira regarding Axis2 XMLBeans databinding. We feel it is worth reporting this in the XMLBeans Jira since it is directly a XMLBeans issue. The original text from the issue follows
==========
In the generated client code, there's no getters or setters that represent an xsd:any in the schema, you're left to grunge around with xmlCursors yourself, this is a PIA because the xmlCursor is not aware of where the xsd:any is declared in the sequence, so suddenly the client programmer has to be aware of the structure of the container of the xsd:any, not just the xsd:any elements themselves.
============
The original issue would be attached to this
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Resolved: (XMLBEANS-269) provider wrapper for xsd:any
Posted by "Cezar Andrei (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cezar Andrei resolved XMLBEANS-269.
-----------------------------------
Resolution: Duplicate
Duplicate of XMLBEANS-138.
> provider wrapper for xsd:any
> ----------------------------
>
> Key: XMLBEANS-269
> URL: https://issues.apache.org/jira/browse/XMLBEANS-269
> Project: XMLBeans
> Issue Type: Improvement
> Reporter: Ajith Harshana Ranabahu
>
> This issue has been reported in the Axis2 Jira regarding Axis2 XMLBeans databinding. We feel it is worth reporting this in the XMLBeans Jira since it is directly a XMLBeans issue. The original text from the issue follows
> ==========
> In the generated client code, there's no getters or setters that represent an xsd:any in the schema, you're left to grunge around with xmlCursors yourself, this is a PIA because the xmlCursor is not aware of where the xsd:any is declared in the sequence, so suddenly the client programmer has to be aware of the structure of the container of the xsd:any, not just the xsd:any elements themselves.
> ============
> The original issue would be attached to this
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-269) provider wrapper for xsd:any
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488123 ]
Jacob Danner commented on XMLBEANS-269:
---------------------------------------
I'm curious, what kind of method signature are you thinking for this wrapping?
XmlObject[] getAny()
void setAny(XmlObject[])
?
> provider wrapper for xsd:any
> ----------------------------
>
> Key: XMLBEANS-269
> URL: https://issues.apache.org/jira/browse/XMLBEANS-269
> Project: XMLBeans
> Issue Type: Improvement
> Reporter: Ajith Harshana Ranabahu
>
> This issue has been reported in the Axis2 Jira regarding Axis2 XMLBeans databinding. We feel it is worth reporting this in the XMLBeans Jira since it is directly a XMLBeans issue. The original text from the issue follows
> ==========
> In the generated client code, there's no getters or setters that represent an xsd:any in the schema, you're left to grunge around with xmlCursors yourself, this is a PIA because the xmlCursor is not aware of where the xsd:any is declared in the sequence, so suddenly the client programmer has to be aware of the structure of the container of the xsd:any, not just the xsd:any elements themselves.
> ============
> The original issue would be attached to this
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-269) provider wrapper for xsd:any
Posted by "Ivan Balashov (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488083 ]
Ivan Balashov commented on XMLBEANS-269:
----------------------------------------
Apparently it's been a year since this issue was reported. To be honest, it's not quite clear how to "grunge about" with XmlCursor.
> provider wrapper for xsd:any
> ----------------------------
>
> Key: XMLBEANS-269
> URL: https://issues.apache.org/jira/browse/XMLBEANS-269
> Project: XMLBeans
> Issue Type: Improvement
> Reporter: Ajith Harshana Ranabahu
>
> This issue has been reported in the Axis2 Jira regarding Axis2 XMLBeans databinding. We feel it is worth reporting this in the XMLBeans Jira since it is directly a XMLBeans issue. The original text from the issue follows
> ==========
> In the generated client code, there's no getters or setters that represent an xsd:any in the schema, you're left to grunge around with xmlCursors yourself, this is a PIA because the xmlCursor is not aware of where the xsd:any is declared in the sequence, so suddenly the client programmer has to be aware of the structure of the container of the xsd:any, not just the xsd:any elements themselves.
> ============
> The original issue would be attached to this
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-269) provider wrapper for xsd:any
Posted by "Ivan Balashov (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488384 ]
Ivan Balashov commented on XMLBEANS-269:
----------------------------------------
In JAXB, in order to assign element to xsd:any, you need to call
element.getAny().add(child);
This is how getAny() is implemented:
public List<Object> getAny() {
if (any == null) {
any = new ArrayList<Object>();
}
return this.any;
}
I wonder why such interface wasn't added in XmlBeans in the first place. I believe there must be some issues with adding setAny(XmlObject).
> provider wrapper for xsd:any
> ----------------------------
>
> Key: XMLBEANS-269
> URL: https://issues.apache.org/jira/browse/XMLBEANS-269
> Project: XMLBeans
> Issue Type: Improvement
> Reporter: Ajith Harshana Ranabahu
>
> This issue has been reported in the Axis2 Jira regarding Axis2 XMLBeans databinding. We feel it is worth reporting this in the XMLBeans Jira since it is directly a XMLBeans issue. The original text from the issue follows
> ==========
> In the generated client code, there's no getters or setters that represent an xsd:any in the schema, you're left to grunge around with xmlCursors yourself, this is a PIA because the xmlCursor is not aware of where the xsd:any is declared in the sequence, so suddenly the client programmer has to be aware of the structure of the container of the xsd:any, not just the xsd:any elements themselves.
> ============
> The original issue would be attached to this
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-269) provider wrapper for xsd:any
Posted by "Cezar Andrei (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553471 ]
Cezar Andrei commented on XMLBEANS-269:
---------------------------------------
In addition to XmlCursor and DOM, one can also use XmlObject.selectChildren(qnameSet) to get to the right elements.
> provider wrapper for xsd:any
> ----------------------------
>
> Key: XMLBEANS-269
> URL: https://issues.apache.org/jira/browse/XMLBEANS-269
> Project: XMLBeans
> Issue Type: Improvement
> Reporter: Ajith Harshana Ranabahu
>
> This issue has been reported in the Axis2 Jira regarding Axis2 XMLBeans databinding. We feel it is worth reporting this in the XMLBeans Jira since it is directly a XMLBeans issue. The original text from the issue follows
> ==========
> In the generated client code, there's no getters or setters that represent an xsd:any in the schema, you're left to grunge around with xmlCursors yourself, this is a PIA because the xmlCursor is not aware of where the xsd:any is declared in the sequence, so suddenly the client programmer has to be aware of the structure of the container of the xsd:any, not just the xsd:any elements themselves.
> ============
> The original issue would be attached to this
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org