Then I don't see the point of the SchemaBindingInitializer. An XSD is simply mapped to a SchemaBinding via the XsdBinder class, what I want is to bypass the XSD and just tell the binding layer here is how to handle the urn:jboss:simplejavabean:1.0 namespace elements.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Alexey Loubyansky > Sent: Tuesday, March 07, 2006 7:50 AM > To: jboss-development@lists.sourceforge.net > Subject: Re: [JBoss-dev] minOccurs=0 not being used > > There must be a resolvable XSD for urn:jboss:simplejavabean:1.0. > > Scott M Stark wrote: > > So I'm not understanding what triggers a > SchemaBindingInitializer to > > be loaded. For a configuration of a marshaller such as the > following: > > > > DefaultSchemaResolver resolver = new DefaultSchemaResolver(); > > JavaBeanSchemaInitializer si = new > JavaBeanSchemaInitializer(); > > > resolver.addSchemaInitializer("urn:jboss:simplejavabean:1.0", si); > > resolver.addSchemaLocation("urn:jboss-test:xmbean:2.0", > > "xml/mbeanserver/jboss_xmbean_2_0.xsd"); > > > > I'm expecting that both the "urn:jboss-test:xmbean:2.0" and > > "urn:jboss:simplejavabean:1.0" namespaces can be handled. The > > "urn:jboss:simplejavabean:1.0" has a code centric > SchemaBinding while > > the "urn:jboss-test:xmbean:2.0" has a SchemaBinding derived > from the > > jboss_xmbean_2_0.xsd annotations. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
