> The correct
> method of obtaining the JNDI context when operating outside the
container is
> not well documented, but I worked it out as follows:
no kidding, found the same thing here. jndi.properties also works if you get
the file location right, and I got the impression that it should be possible
to pass the exact variables that are in jndi.properties in as system
properties on the command line, but I couldn't get that to work.
A burning question though: how does this fit together though when your
remote application runs as many users, prompting them for a username /
password? You need to dynamically set the context then at runtime, and it
can change throughout the lifetime of the client application. I'm pretty new
to all of this, so that's probably a pretty stupid question, but it strikes
me that there needs to be some mechanism of doing this... all the examples
I've seen expect remote apps to run as one, well-known, named user which
won't change until the app exits.
cheers
Jules
