[jboss-dev-forums] [Design of POJO Server] - Unifying metadata

[Adrian]

The code that I gave to Alex rewrites the old 2.x metadata
as a bridge to the new stuff.

On Thu, 2007-09-13 at 09:33 -0400, scott.stark at jboss.org wrote:
> A problem showing up in 1.4 container to 5 container interop, as well as merging duplicate behavior into common deployers is the lack of a unified metadata view. The metadata view is also not authoritative. For example, the jndi name under which home proxies are bound is not simply the org.jboss.ejb3.metamodel.EnterpriseBean.getJndiName or transport derived variation like the org.jboss.metadata.BeanMetaData.getInvokerBinding. We have to have a consistent and complete metadata view so that proxy factory x obtains the name to bind the proxy under is a simple lookup against the metadata. There cannot be container specific logic if this is the be manageable and refactorable.
> 
> In terms of the unified metadata work:
> https://svn.jboss.org/repos/common/jbossxb-builder/trunk/src/test/java/org/jboss/ejb/metadata/spec/
> 
> what exists in terms of backward compatibility with the old models? I thought Adrian said he had something that would allow coding using the old models to write through to the new model.
> 
> The metadata model should also be in a separate project. I suppose this should be under the https://svn.jboss.org/repos/jbossas/projects/integration/trunk/ as a jboss-metadata project.
> 
> 
> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083940#4083940
> 
> Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083940
> _______________________________________________
> jboss-dev-forums mailing list
> jboss-dev-forums at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-dev-forums
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx