[ http://issues.apache.org/jira/browse/JAXME-66?page=comments#action_12318754 ]
Jochen Wiedmann commented on JAXME-66: -------------------------------------- xjc:dom is a really tough job, because most likely you have to modify almost all parts of JaxMe. Let's begin with the first step: The parser must accept the xjc:dom element. The right place to implement this is the JaxMeSchemaReader. I assume, that the xjc:dom element will be added to an xs:any element. You have to implement a subclass JaxMeAny (or whatever you want to name it) of XsEAny This subclass must have a method getBeanByParent. (See JaxMeSchemaReader.JaxMeGlobalBindingsImpl for an example.) The purpose of this method is to set a flag "domSerialization" (or whatever in JaxMeAny) to true. Besides, you have to overwrite the method JaxMeXsObjectFactory.newXsEAny to return an instance of your subclass, rather than the default XsEAny. > Add support for xjc:dom extension > --------------------------------- > > Key: JAXME-66 > URL: http://issues.apache.org/jira/browse/JAXME-66 > Project: JaxMe > Type: New Feature > Components: JaxMe Core > Versions: future (enh) > Reporter: Fredrik Vraalsen > > Add support for xjc:dom extension to map a certain part of the schema into a > DOM tree: > http://java.sun.com/webservices/docs/1.6/jaxb/vendorCustomizations.html#dom -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
