|
I'm new to jboss (and not too old with EJB in
general <gr>). I'm using jbosstest to get up to speed. Once I
got hellotest working locally, I wanted to get it working across the
network. So I exploded hellotest.jar and added the following line to
jndi.properties:
java.naming.provider.url=192.168.1.100
where the address is the computer running
jboss. I then added this back in to the jar, copied to the client computer
and it ran fine.
Thinking about our upcoming application, obviously
exploding jar files and modifying their contents is not a manageable approach to
deployment. I'm reading now about JNDI, but I wanted to ask for some
pointers regarding the proper way to achieve location independence in a jboss
framework. I would think I'd want some way to identify when I'm deploying
a client where it should look for a JNDI server (or lacking that, the EJB
objects themselves) by running some command line or GUI configuration tool, or
even just supplying configuration parameters to the client itself, either
directly or through a properties file. How are people doing
this?
|
