[adrian.brock]

The idea that a javabean property editor does a jndi lookup seems like a stupid
idea to me anyway. ;-)

[anil.saldhana]

The idea that a javabean property editor does a jndi lookup seems like a stupid
idea to me anyway. ;-)

Please dial the Complaints center located at Snoqualmie Pass near Seattle for feedback on all the complaints on this thread, Adrian.

Regarding the pooling tests, I think I have the solution for it. I will be checking it some bug fixes from my end today.

[anil.saldhana]

Adrian, I have made the PooledInvoker depend on the SecurityDomain (ie. JaasSecurityDomain). After this, the CCE does not arise while looking up the security domain. But the tests are still failing mainly because the jndi names for the ejb look up does not seem to be right.

Global JNDI Namespace

 +- StatelessSessionWithPooledSSL (proxy: $Proxy114 implements interface org.jboss.test.pooled.interfaces.StatelessSessionHome,interface javax.ejb.Handle)
 ...
 +- PooledStatelessSession (proxy: $Proxy114 implements interface org.jboss.test.pooled.interfaces.StatelessSessionHome,interface javax.ejb.Handle)

I did find some bugs ( like copy/paste error)
http://jira.jboss.org/jira/browse/JBAS-5480 while analyzing the SSLContextUnitTestCase. Will check in tomorrow.

[anil.saldhana]

Adrian, based on my current run, for the pooled tests - BaseStressTestCase fails with some JNDI related lookup issues (probably JNDI names are wrong) and the SSLContextUnitTestCase is passing fine.

[starksm64]

I'll take a look at it in case its a side-effect of the resolver work I'm doing.