1 2 3 4 Previous Next 49 Replies Latest reply on Sep 26, 2007 8:03 AM by Carlo de Wolf

    Unifying metadata

    Scott Stark Master

      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:

      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.

        1 2 3 4 Previous Next