[Design of Security on JBoss] - Re: Security EJB2 and dependencies
by anil.saldhana@jboss.com
Adrian, I tried adding the following piece of code into start() of SecurityInterceptor for the pooled tests,
|
| // Container implementation --------------------------------------
| public void start() throws Exception
| {
| ....
|
| //Take care of hot deployed security domains
| if(container != null)
| {
| securityManager = container.getSecurityManager();
| if(securityManager != null)
| {
| appSecurityDomain = securityManager.getSecurityDomain();
| appSecurityDomain = SecurityUtil.unprefixSecurityDomain(appSecurityDomain);
| }
| }
| }
|
I see basically deployment issues.
| 2008-04-22 11:55:28,593 DEBUG [org.jboss.ejb.StatelessSessionContainer] (RMI TCP
| Connection(6)-127.0.0.1) End java:comp/env for EJB: StatelessSessionWithPooledSSL
| 2008-04-22 11:55:28,593 DEBUG [org.jboss.ejb.plugins.local.BaseLocalProxyFactory
| ] (RMI TCP Connection(6)-127.0.0.1) StatelessSessionWithPooledSSL cannot be Bound, doesn't have local and local home interfaces
| 2008-04-22 11:55:28,593 DEBUG [org.jboss.ejb.StatelessSessionContainer] (RMI TCP
| Connection(6)-127.0.0.1) Starting failed jboss.j2ee:jndiName=StatelessSessionWi
| thPooledSSL,service=EJB
| java.lang.RuntimeException: invoker is null: jboss:service=invoker,type=pooled,socketType=SSLSocketFactory,wantsClientAuth=true at org.jboss.proxy.ejb.ProxyFactory.setupInvokers(ProxyFactory.java:254)
|
| at org.jboss.proxy.ejb.ProxyFactory.start(ProxyFactory.java:238) at org.jboss.ejb.SessionContainer.startInvokers(SessionContainer.java:44
| 0)
| at org.jboss.ejb.SessionContainer.startService(SessionContainer.java:398
| )
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
|
So there seem to be other issues as well.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145946#4145946
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145946
16 years, 5 months
[Design of EJB 3.0] - Re: Deprecating Ejb3Deployment
by scott.stark@jboss.org
The metadata project covers the standard metadata models we support in jbossas.
If new annotations affect the existing metadata, we need to add the dependency on the annotations and update the annotation creators to incorporate them.
If these are just pass through annotations on javaee component classes that should be available in a generic manner on the JBossEnterpriseBeanMetaData (which is the metadata input for the EjbContainer which is where getAnnotation(Class) exists). There is already a JBossEnterpriseBeanMetaData.getAnnotations which returns a mapping of annotation class to AnnotationMetaData. This is not populated for unknown annotations though.
If we add pass through support for annotations to the component metadata for class, field and method annotations, is that going to be sufficient?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145945#4145945
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145945
16 years, 5 months