-
1. Re: Unifying metadata
anil.saldhana Sep 13, 2007 9:36 AM (in response to starksm64)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.
-
2. Re: Unifying metadata
starksm64 Sep 13, 2007 9:37 AM (in response to 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 -
3. Re: Unifying metadata
anil.saldhana Sep 13, 2007 9:44 AM (in response to starksm64)http://jira.jboss.com/jira/browse/EJBTHREE-1048
is the EJB3 JACC alignment issue with unified metamodel. -
4. Re: Unifying metadata
slaboure Sep 13, 2007 9:57 AM (in response to starksm64)AFAICT this is the work Alexey is currently doing, right?
-
-
6. Re: Unifying metadata
aloubyansky Sep 13, 2007 10:03 AM (in response to 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. -
7. Re: Unifying metadata
adrian.brock Sep 13, 2007 10:11 AM (in response to starksm64)"scott.stark@jboss.org" wrote:
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. -
8. Re: Unifying metadata
starksm64 Sep 13, 2007 10:20 AM (in response to starksm64)"alex.loubyansky@jboss.com" wrote:
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/"adrian@jboss.org" wrote:
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? -
9. Re: Unifying metadata
aloubyansky Sep 13, 2007 6:06 PM (in response to starksm64)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. -
10. Re: Unifying metadata
starksm64 Sep 14, 2007 12:43 PM (in response to 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.
-
11. Re: Unifying metadata
aloubyansky Sep 16, 2007 6:01 PM (in response to starksm64)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. -
12. Re: Unifying metadata
bill.burke Sep 17, 2007 3:08 PM (in response to starksm64)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.
-
13. Re: Unifying metadata
starksm64 Sep 18, 2007 3:46 PM (in response to 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.
-
14. Re: Unifying metadata
starksm64 Sep 19, 2007 2:36 AM (in response to 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?