[
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
