Not acceptable in whose eyes, ejb spec, god, country?

For the most part the ejb spec restrictions are meaningless unless you are 
running with a security manager and have configured the server to restrict 
application deployments from access to the spec stated operations. Other 
containers run with a security manager by default so using a pojo in a seperate 
jar that can be assigned the required security permissions is the usual route 
of providing restricted functionality to the ejb.

Exposing an interface in jndi via the NonSerializableFactory does not prevent 
access via the detached invoker mechanism via the same or a different interface 
as well.

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

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


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to