On Fri, Mar 19, 2010 at 3:19 PM, Les Hazlewood <[email protected]> wrote: >> Well, actually the problem is not the jnlp file but >> SecureRemoteInvocationFactory itself as it tries to do >> System.getProperty(SESSION_ID_SYSTEM_PROPERTY_NAME) - are you >> suggesting I change that whole approach to handle it differently? > Ah, yes, I see the problem now. Yeah, we should probably find a > different approach entirely, but I think the solution could be pretty > simple: > A probably sufficient solution would be to set a static property in > WebStartDriver's main method before instantiating the > ApplicationContext. Then you can reference that property from within > the Spring xml when defining the SecureRemoteInvocationFactory bean.
Yeah, that's nice and simple - I'll get it implemented thanks! In fact, it would almost obsolete catching the exception, since it should likely prefer a session id that is explicitly set. Almost, not completely though - the code still would reach the part the gets it from the sessionid if the previous exception is caught and ignored. Kalle
