Unifying metadata

[starksm64]

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.

[anil.saldhana]

Scott, what is the JIRA issue associated with the unified metamodel? I want to link the ejb3 jacc work that needs to be done after that.

[starksm64]

Related threads and issues:

Parsing deployer, original unification discusssion:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111567

Example resolver deployer needing unified metadata:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083555

JIRA issue:
http://jira.jboss.com/jira/browse/JBAS-4506

[anil.saldhana]

http://jira.jboss.com/jira/browse/EJBTHREE-1048
is the EJB3 JACC alignment issue with unified metamodel.

[slaboure]

AFAICT this is the work Alexey is currently doing, right?

[starksm64]

Yes.

[aloubyansky]

The metadata project was created by Carlo some time ago and initially included the current EJB3 metadata, AFAIK.
Recently, I moved the metadata from the jbossxb-builder to this project as well.

[adrian.brock]

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 code that I gave to Alex rewrites the old metadata as a bridge to the new stuff.

[starksm64]

The metadata project was created by Carlo some time ago and initially included the current EJB3 metadata, AFAIK.
Recently, I moved the metadata from the jbossxb-builder to this project as well.

Ok, the project is here:
https://svn.jboss.org/repos/jbossas/projects/metadata/

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

Its not jumping out at me in the https://svn.jboss.org/repos/jbossas/projects/metadata. Is it there Alexey?

[aloubyansky]

I committed only the new classes. The packages are

/projects/metadata/trunk/src/main/java/org/jboss/metadata/javaee/
/projects/metadata/trunk/src/main/java/org/jboss/metadata/ejb

I'll add the integration part too.

[starksm64]

The first step I want to do to get a unified metadata view is to simply pull all of the metadata classes into /projects/metadata/trunk/src/main/java/org/jboss/metadata. I want to pull out any jbossxb/xml parser factories into a metadata-parser project as well so there is a clean separation of metadata, metadata parsing and metadata consumers.

[aloubyansky]

I've just committed the integration part with the old metadata.

The binding is done with Java annotations. There is nothing XB/XML specific to pull out.

[bill.burke]

FYI, we are not changing the JNDI naming scheme again. It really pissed off users the last time we did it. Not against changing the API though or having a unified metamodel view.

[starksm64]

The first thing I'm doing today is moving all of the metadata with the existing duplication into the https://svn.jboss.org/repos/jbossas/projects/metadata/trunk/ project, and deleting the metadata from the jbossas projects. That will at least get a unified artifact on which the deployers depend.

[starksm64]

The org.jboss.metadata from the metadata project, for example:
https://svn.jboss.org/repos/jbossas/projects/metadata/trunk/src/main/java/org/jboss/metadata/MethodMetaData.java

is not usable as a replacement for the server project version, because its abstract. Its also not a complete replacement for the existing version. How was this generated, and why is the MethodMetaData abstract?