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

[adrian@jboss.org]

"scott.stark at jboss.org" wrote : 
  | Where is the metadata model going and how is it relating to the current org.jboss.metadata?
  | 

Not sure what you are asking. Let me answer both questions :-)

1) I'm creating a JavaEE deployer project that does all the
standard/comon stuff then there will be EJBDeployer/WebDeployer
projects, etc. This is to seperate the deployer from the container
so it can a) do "on demand", b) the metadata model is shared where
appropriate, c) the container doesn't need to know anything about
how the model is created.

2) The metadata model will be a shared sanitised and refactored
model, e.g. I'm splitting BeanMetaData into security, persistence,
transactions, methods, etc
The org.jboss.metadata will still exist for read only by old
container plugins (e.g. user written interceptors). But it
will just be a wrapper/mapper to the real metadata model.

e.g.

  | org.jboss.metadata.BeanMetaData
  | 
  |    /** The delegate */
  |    private EJBeanMetaData delegate;
  |    
  |    /**
  |     * Create a new BeanMetaData.
  |     *
  |     * @param delegate the delegate
  |     * @throws IllegalArgumentException for a null delegate
  |     */
  |    public BeanMetaData(EJBeanMetaData delegate)
  |    {
  |       if (delegate == null)
  |          throw new IllegalArgumentException("Null delegate");
  |       this.delegate = delegate;
  |    }
  | 
  | <snip/>
  | 
  |    /**
  |     * Get the container managed transactions
  |     * 
  |     * @return the container managed transactions
  |     */
  |    public boolean isContainerManagedTx()
  |    {
  |       EJBTransactionMetaData result = delegate.getTransactionConfig();
  |       if (result == null)
  |          return EJBTransactionMetaData.DEFAULT_CONTAINER_MANAGED_TX;
  |       return result.isContainerManagedTx();
  |    }
  | 

Of course EJBTransactionMetaData should be an annotation
with it really coming from the metadata repository so it can
be overridden at different levels, e.g. deployment level
transaction defaults.

anonymous wrote : 
  |  I have merged the web tier parsing into population of the root org.jboss.metadata.WebMetaData instance by writing ObjectModelFactory.
  | 
I'm using annotations to bind to the schema.
See the link I posted to a JBossXB forum post in a comment by itself
above.

EJB3 has their own factory(ies) as well.

anonymous wrote : 
  | It should be schema based however.
  | 

Correct.

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

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