anonymous wrote : | What is clear to me is that this type of thing (whether it xml or annotations) needs to be transformed into some form of dependency injection on a metadata object otherwise the microcontainer isn't go to know the correct startup order: | | | <bean ...> | | Security | | Id | | | | |
The internalized behavior that the ejb container performs with respect to the security domain needs to be externalized as a depenendency on the service supporting the interface(s) that the ejb container looks up from jndi. Its not that there is really a dependency on the binding existing in JNDI, there is a need for the authentication and authorization interfaces to be injected, and the implementing service is what there needs to be a dependency on. The unusual detail of this particular case is that the service is the JaasSecurityManagerService, but it does not actually create a binding at the location referenced by the java:/jaas/MyRealm value. It just creates an ObjectFactory at java:/jaas such that the lookup of java:/jaas/MyRealm returns the security service implementation associated with the MyRealm configuration. So depenendcy is not on the existence of the JNDI binding, its on the state of the JaasSecurityManagerService that manages the supports the JNDI binding. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861223#3861223 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861223 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
