Im working on the same issue and I don't have success either. Is this another class-path problem ? The session-bean can be looked up, but when trying to cast the Proxy to the right LocalHome-interface I get a ClassCastException. Anybody has a hint ?
Hunter resolved this a while ago, so I know it can be done.
Are you deploying your war and ejb-jar in the same ear ? They must be deployed 'locally' to each other, if you want to use local interfaces..... (AFAIK!)
Yes, my setup is working fine...
First off, I would recommend getting the latest JBoss3 code from CVS, since there have been MANY changes since the pre-packaged alpha release...
Next, the WAR(s) and JAR(s) need to be in the same EAR. That is the magic that makes everything work.
Let me know if you have more trouble. I should be able to help.
After packaging all into one ear everything works fine right now. Luck has it that I designed my application to use ConnectionFactories, so that I can use it with either the remote- or local-API with just changing one line of code (for now, later this will be configurable). Well, I will have a look how big the impact on the performane is ...
Thanks for your help,