On Fri, Mar 19, 2010 at 2:45 PM, Kalle Korhonen
<[email protected]> wrote:
> On Fri, Mar 19, 2010 at 2:10 PM, Les Hazlewood <[email protected]> wrote:
>> On Fri, Mar 19, 2010 at 12:37 PM, Kalle Korhonen
>> <[email protected]> wrote:
>>> Very good. Yes, using the property was really the only reason why they
>>> needed to be signed. I'd rather not if that can be avoided. It's been
>>> awhile since I've last worked on webstart apps myself. I'll see if I
>>> can easily get it working by using an argument instead.
>> Cool. This should help:
>
> 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.
Something like this:
<property name="sessionId">
<util:constant
static-field="org.apache.shiro.samples.spring.ui.WebStartDriver.LAUNCH_SESSION_ID"/>
</property>
Or whatever you want to call the static attribute...
Does that make sense?
- Les
