Right! Sorry for the delay. It turns out I didnt have an account here associated with my email address and thus I never got your response - no matter.
1. Simply put, JAX-B is very limited in how much of the XML Schema it actually understands (or is willing to bind). JAX-B also uses its own annotations within the XML Schema document to help in binding. My solution, however, solves those things JAX-B chose to leave behind. My solution is a complete, working generator of classes from XSD documents for almost any plausible XSD type declaration. The XSD documents do not require any modifications to have classes be generated for them. I still need to establish a feature list for this project, but here it is simpler to state what is _not supported_: a. <union/>, b. <list/> simpleTypes or attributes inheriting from non-list simpleTypes c. <restriction/> containing <enumeration/>s that are excluded from a parent type. 2. True, the documentation is limited. Please visit http://www.safris.com and follow the XML Toolkit link for a more in-depth explanation (still needs a lot more content, but I hope this will do). Again, I am very interested in the opportunity to maintain my own metadata on the public repos. The XML Bind project has also been folded into a larger XML Toolkit framework that is currently under busy development. Please see http://www.safris.com for more information. hermod.opstvedt wrote: > > Hi > > 1. How is this different from JaxB? > 2. The documentation at http://xml.safris.org/bind/ leaves something to be > desired > > Hermod > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > seva safris > Sent: Tuesday, January 23, 2007 11:08 AM > To: dev@maven.apache.org > Subject: maintain own metadata > > > Hi, I have a project that I would like to be available on Maven's > central repository. I have already had a preliminary version of my > project deployed to repo1.maven.org, but it seems inefficient to keep > asking you guys to have new versions deployed as time goes on. The > project can be identified by the org.safris.xml groupId. > > I would like to request that I take responsibility for maintaining my > own metadata and set up an automated rsync system for deployment. > Please tell me what needs to be done to make this work. > > Brief description of my project: > > "The XML Bind solution is an alternative approach at XML binding for > Java. The Generator solution is capable of generating source code from > an XSD, allowing the Runtime to marshal and unmarshal those objects > into XML. The builders are responsible for defining task and plugin > classes for with Ant and Maven. Builder-ant is for Ant, and > Builder-maven is for Maven." > > Project page: > > http://xml.safris.org/bind/ > > Thank you, > > seva safris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * > > This email with attachments is solely for the use of the individual or > entity to whom it is addressed. Please also be aware that the DnB NOR > Group > cannot accept any payment orders or other legally binding correspondence > with > customers as a part of an email. > > This email message has been virus checked by the anti virus programs used > in the DnB NOR Group. > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/maintain-own-metadata-tf3063273s177.html#a9727257 Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]