[jboss-dev-forums] [Design of POJO Server] - Re: Allowing multiple AbstractParsingDeployer to work with t

[adrian@jboss.org]

Ok, FYI I'm currently working on reworking the JavaEE parsing.

I started this so I could get a real idea of what we need
to create the ManagedObjects, but when I looked
I got more deeply involved.

I looked at what EJB3 is doing and it is basically broken
for the following main reasons (there are others):

1) It is incomplete and the error handling is rubbish (non-existent)
2) It is not backward compatible so a user written EJB2 interceptor/plugin
won't work because BeanMetaData, etc. is a different type.
3) It is EJB centric, but there has been some work recently to
copy parts of back into the original model for the injection stuff.

I'm working on a schema based deployer for JavaEE5 where
EJB2,3, RAR, WAR, CAR, EAR can share the same metamodel.

To make this simpler, I've created a layer on top of JBossXB
that uses annotations to bind the model to the schema.
I'll describe this is a different JBossXB thread.

I've also started a refactoring of the current metamodel
(with a backwards compatibilty layer that basically wraps the new model) 
so we can improve the model. 
I have lots of ideas in this direction, but I been blocked from 
implementing them because of the compatibity consideration.

One of them, is being able to override anything in ejb-jar.xml
with the jboss.xml

Another, which I haven't looked at yet in the current refactoring,
is to reuse the annotations in the model.
Which will obviously make it more consistent
and also integrates better with the metadata repository.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976258#3976258

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976258