IMO, the only thing that should go in this shared module is shared
metamodels. i.e. <ejb-ref>. web.xml metamodel should go in the tomcat
module. ejb-jar.xml metamodel in ejb3, etc., but the share integration
interfaces. I also want to put the ENC population code within this
shared module too as it is going to be shared between web/ejb and other
modules that share ENC injection.
So, I was wrong, j2ee was not a good please.
Bill
Scott M Stark wrote:
I mean all of the org.jboss.metadata.* classes. These are really part of
the deployment layer and this is where the shared usage is showing up:
tomcat, jbossws, ejb3, ...
What we need is the shared deployment metadata model sans the current
xml dependency. The binding of the the metadata source, be it xml,
annotations, etc should be part of the implementation using these
classes. The big issue with making this a truly reusable codebase is
along the lines of the j2ee/jboss specific features. Bill suggested
using the j2ee module as the location for this code. If it was split up
into j2ee specific bindings and deployer specific bindings that could
make sense.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Adrian Brock
Sent: Wednesday, May 24, 2006 8:47 AM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] Breaking out the server/metadata classes
You mean the org.jboss.metadata.MetaData class?
There already is a sort of clone of it in common see
org.jboss.util.xml.XmlHelper
It doesn't look like it is used though?
It's almost certainly out-of-date?
The real MetaData does need changing like you describe, but
it does have the problem of mixing J2EE defined stuff with
jboss specific stuff from jboss-xxx.xml in the same class.
Sometimes the jboss specific stuff is defined by the plugin
i.e. "XmlLoadable", so you don't even have a metadata class as such.
I've always thought that this stuff should be part of the
deployment layer. But then there are advantages and
disadvantages for the metadata, deployer and
container/runtime to live in the same project.
Advantage: It is easy to maintain.
Disadvantage: It is difficult to expose the model to a client
because runtime dependencies inevitably leak into it.
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=k&kid7521&bid$8729&dat1642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
--
Bill Burke
Chief Architect
JBoss Inc.
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
