[jboss-dev-forums] [Design of EJB 3.0] - Re: EJBContainer Validation on Deployment/Start

[ALRubinger]

These are only preconditions if they prevent Proxy generation or lead to non-deterministic results upon lookup/invocation.  For example, if @Remote specifies a class that is not an interface, Proxy component should throw the error.

Adding a validation component to aspectize deployment rules based on available metadata can cover all cases and provide a pluggable mechanism looking forward.  Less code in the Containers (EJB3 Core), less code in the Proxy stuff (where some of it doesn't belong).

S,
ALR

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

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