Thank you for your help. I got the client to run remotely by installing
jbossall-client.jar on the client machine and adding it to the classpath. The only
other thing I needed to do was to change jndi.properties from localhost to the remote
machine name. Ex04_1 is a very simple java client - no swing or awt. I will look at
Vamp HQ site also. It looks like a good reference site.
Since I got the client working by manually installing the client on the remote
machine, it was a good learning experience, but not very satisfying as a soluton. The
problem to fix is to get the Cabin EJB to deploy if is not deployed when I run the
client. If you run ant run.client_41a on the local machine, it has a dependency on
the deployment of the necessary EJBs. To get my client to work using the manual
process, I had to go to the server machine and copy the titan.jar (jar that contains
the Cabin EJBs) into the deploy directory to deploy the Cabin EJBs so that the JNDI
lookup would work. My question is, How do you deploy the necessary EJBs remotely if
they aren't already? Perhaps this isn't something clients should be allowed to do.
Unfortunately, that's how it works in the example.
Conclusion: I learned how things work, which is the point of running the tutorial. I
wouldn't want to actually install clients this way, especially if they were more than
this trivial case.
Doug
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3837329#3837329
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837329
---
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
