[ http://jira.jboss.com/jira/browse/JBSEAM-247?page=comments#action_12408547 ] Ales Justin commented on JBSEAM-247: ------------------------------------ With the new JBossXB.builder code finished, this is what you can now easily do: - have custom xml: http://anonsvn.jboss.org/repos/jbossas/trunk/testsuite/src/resources/hibe... - write matching metadata: http://anonsvn.jboss.org/repos/jbossas/trunk/hibernate-int/src/main/org/j... - provide deployer that understands that custom xml: http://anonsvn.jboss.org/repos/jbossas/trunk/hibernate-int/src/resources/... - have a deployer that understands that custom metadata: http://anonsvn.jboss.org/repos/jbossas/trunk/hibernate-int/src/main/org/j... Having custom parser should be just that jbossxb-parser element, need to look into why it doesn't work yet. Custom metadata deployer is not (always) needed, since it can be picked up inside existing MC beans (wildcard matching). For Seam this would mean that it could easily keep the existing components.xml, just requiring to write matching metadata, and then delegate work to MC. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira