[jboss-dev-forums] [Design of POJO Server] - Re: ENC Deployment

[adrian@jboss.org]

"bill.burke at jboss.com" wrote : 
  | That's nice for basic beans, but as I showed before, it is just not so simple for Java EE land where the ENC -> Global JNDI binding cannot be determine by the available metadata.  To put it in other terms, the available metadata may not be enough to construct a Kernel identity or exact JNDI binding.  The referenced component will need to be searched for based on the position of the component in the deployment and based on the little of metadata that was made available by the application developer.

Whatever mechanism is used needs to be validatable via a "dry run"
through the deployers.
i.e. It should be possible to create a profile (list of deployments)
and then say "does it make sense?", "what is missing/unresolved?", etc.

If that is not possible then the modal is broken.

Implicit rules like "position in the file" are supportable but
inherently prone to error/breakage when the file is changed.
e.g. a conflicting definition is interpolated 
or the order is changed by some user/tool/ide that doesn't understand
the importance.

But that's not my problem. :-)
I've always hated such "scripting" as being brittle.

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

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