[
https://issues.apache.org/jira/browse/GERONIMO-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated GERONIMO-4899:
-----------------------------------
Fix Version/s: (was: 2.2)
Wish List
I wish we had fixed this for 2.2. It isn't very hard, a patch would be great!.
On the other hand 3.0 will need a rather different solution.
> Make the client container run on machines remote to the server
> --------------------------------------------------------------
>
> Key: GERONIMO-4899
> URL: https://issues.apache.org/jira/browse/GERONIMO-4899
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: application client
> Environment: 2.2-SNAPSHOT
> Build 2009.09.16-14:12:22.112-0400
> Reporter: Jürgen Weber
> Fix For: Wish List
>
>
> see
> http://www.nabble.com/How-does-the-Client-Container-work--td25632603s134.html
> Right now the Client Container only seems work on the same machine as the
> server.
> It should work on remote machines, too (or rather especially there ;-)
> There must be a way to specify the server address.
> I suggest to support all of these ways:
> a) look for jndi.properties (in current working directory) and use its
> PROVIDER_URL ...
> b) add client command line argument -url PROVIDER_URL [+ command line
> arguments for user/pass]
> c) add the deploy.sh command line arguments for host/url/user/pass
> It would be nice if the client wouldn't need too many libs (or could download
> them from the server)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
