"ALRubinger" wrote : "anil.saldhana(a)jboss.com" wrote : Added to that,
IMO the interceptors (including the security interceptors) should not be in the
externalized project. They should be sitting in the ejb3 module in the AS workspace.
|
| So what about EJB3 Standalone and Embedded? They don't need interceptors? This
isn't an AS integration point.
|
The security aspect (to give it its correct name ;-) is a product of the security
project. It's an implementation detail.
Only the runtime metadata it uses is "shared" and then only if it needs to be,
e.g. converting ejb3 metadata to jboss-security's internal model.
"anil.saldhana(a)jboss.com" wrote : If you inculcate this, there is no need for
any magical plugin that you envision and that has been a barrier to people like me, who
have wasted a few man hours.
Though good, the Plugin isn't "magical". It's a mechanism to allow EJB3
upgrades without having to upgrade AS. When I was developing EJB3 apps the last thing I
wasn't to do was upgrade all of AS to get a feature I needed from a new release of
EJB3. Now that the AS default build brings in EJB3 code via thirdparty, you'll no
longer need to run it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135002#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...