"Rickard �berg" wrote:
> Ole Husgaard wrote:
> > A new problem with finding the default datasource has
> > popped up on me today.
> > Unfortunately it seems JNDI related, and I an no expert
> > on JNDI.
> <snip>
>
> Indeed, it was a couple of bugs related to JNDI.
>
> Fixed:
> * Default datasource is now always "java:/DefaultDS". No more JNDI
> scanning
Great. I never like this JNDI scanning.
> * "jbosstest" beans now correctly look up TransactionManager from
> "java:/Transactionmanager" instead of "TransactionManager"
> * "jbosstest" deployment descriptors now reference "java:/DefaultDS"
> instead of "Hypersonic"
Nice. And with the dynamic classloading I guess we have
less worries about up-to-date jars.
> "jbosstest" runs without problems now. Above is in current CVS.
Well, I still have problems. Now _all_ tests fail with:
javax.naming.CommunicationException.
Root exception is java.lang.ClassNotFoundException:
org.jboss.ejb.plugins.jrmp13.interfaces.HomeProxy
I've tried deleting all and grapping fresh copies off
CVS. Still same problem with the default build.
But if I hack dist/conf/default/jboss.properties to
have the lines:
java.rmi.server.useLocalHostName=true
java.rmi.server.hostname=localhost
java.rmi.server.codebase=http://localhost:8083/
everything runs fine. Note the portnumber is changed
from what is in the commented line.
Not quite sure if this is the correct think to do...
Thanks for your help.
Best Regards,
Ole Husgaard.
