[JBoss-user] [Installation Configuration] - Re: Securing access to JNDI tree

2004-12-06 Thread gavinho
Great, I have set up access control to JNDI tree. Thx. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3857646#3857646 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3857646

[JBoss-user] [Installation Configuration] - Re: Securing access to JNDI tree

2004-12-02 Thread [EMAIL PROTECTED]
No. The org.jnp.interfaces.Naming interface is the interface exposed by the NamingService xmbean. All Naming interface invocations ultimately go through the NamingService xmbean and its associated interceptors. View the original post :

[JBoss-user] [Installation Configuration] - Re: Securing access to JNDI tree

2004-12-02 Thread gavinho
[EMAIL PROTECTED] wrote : No. The org.jnp.interfaces.Naming interface is the interface exposed by the NamingService xmbean. All Naming interface invocations ultimately go through the NamingService xmbean and its associated interceptors. Browsed thru the source code tree jboss-3.2.5-src\naming

[JBoss-user] [Installation Configuration] - Re: Securing access to JNDI tree

2004-12-02 Thread [EMAIL PROTECTED]
Ok, I see your confusion now and its due to not showing how to expose the NamingService via the detached invoker framework as a Naming proxy. Go reread the wiki which I have updated to show all of the details for changing the conf/jboss-service.xml NamingService to use a custom security

[JBoss-user] [Installation Configuration] - Re: Securing access to JNDI tree

2004-12-01 Thread gavinho
Yeah, the ctor not found message is not fatal. I managed to start JBoss successfully with the interceptor attached. But I am still interesting to know how can we remove such noisy message. I tested using a external client program to do JNDI lookup but the invoke() method of interceptor had not

[JBoss-user] [Installation Configuration] - Re: Securing access to JNDI tree

2004-12-01 Thread gavinho
Browsed thru the source codes. The interceptor as described in URL: http://www.jboss.org/wiki/Wiki.jsp?page=XMBeansforSecurity only intercept calls to object org.jboss.naming.NamingService But according to the class diagram in URL

[JBoss-user] [Installation Configuration] - Re: Securing access to JNDI tree

2004-11-29 Thread gavinho
[EMAIL PROTECTED] wrote : http://www.jboss.org/wiki/Wiki.jsp?page=XMBeansforSecurity | I followed the examples but encountered NoSuchMethodException when startup JBoss. The problem is JBoss startup sequence tried to use org.jboss.mx.server.MBeanInvoker interface to lookup a constructor for

[JBoss-user] [Installation Configuration] - Re: Securing access to JNDI tree

2004-11-29 Thread [EMAIL PROTECTED]
That is an irrelevant debug level msg simply saying the interceptor does not have a ctor that takes an MBeanInvoker. The default ctor will be used instead. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3856744#3856744 Reply to the post :

[JBoss-user] [Installation Configuration] - Re: Securing access to JNDI tree

2004-11-23 Thread gavinho
Yes, I am also looking for this topic. Anyway has update about it? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3856114#3856114 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3856114

[JBoss-user] [Installation Configuration] - Re: Securing access to JNDI tree

2004-11-23 Thread [EMAIL PROTECTED]
http://www.jboss.org/wiki/Wiki.jsp?page=XMBeansforSecurity View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3856180#3856180 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3856180