JNDI and EJB over *Proxied* HTTP. How?

[mgaert]

Hello,

we have set up HTTP and JNDI tunneled over http all right for a Swing-based fat client.

The last piece would be to allow the client to not use HTTP directly but to connect through an HTTP proxy on the client side (i.e. squid or pound).

Any idea where I can specify a HTTP Proxy in the invoker configuration?

TIA

[mgaert]

Sorry, that should be "EJB access and JNDI" that we have set up all right.

[didi1976]

You can specify a proxy on startup of your fat-client using:

java -Dhttp.proxyHost=yourproxy -Dhttp.proxyPort=8080 YourClass

[mgaert]

Thanks for the pointer, but, hmmm, it does not work that easily for me yet.

We are starting the fat client through Java WebStart, which allows to add system properties in the JNLP file such as:




(Adding "proxySet", "true", does not help either)

I guess this works for plain URLConnections, but does the client-side of the EJB invoker chain use URLConnection?

Or maybe the JNLP settings don't get there? I will have to see whether the behaviour differs when I start the fat client from the command line...

[mgaert]

Should be
property name="http.proxyHost" value="host"/
property name="http.proxyPort" value="8080"/

in pointy HTML brackets

(Great BB system where preview differs from actual display :-( )