Re: DefaultObjectStreamFactory | Re: AccessControlException with Wicket on Google App Engine (GAE)

2009-11-03 Thread Igor Vaynberg
application init should be fine. -igor On Tue, Nov 3, 2009 at 5:02 AM, A. Maza wrote: > Thanks Igor, > > > I have seen that the Objects class provides a static setter in order to use > a different Implementation of IObjectStreamFactory instead of the > DefaultObjectStreamFactory. > > Where would

Re: DefaultObjectStreamFactory | Re: AccessControlException with Wicket on Google App Engine (GAE)

2009-11-03 Thread A. Maza
Thanks Igor, I have seen that the Objects class provides a static setter in order to use a different Implementation of IObjectStreamFactory instead of the DefaultObjectStreamFactory. Where would you recommend to place the code to set my own implementation of IObjectStreamFactory using the s

Re: DefaultObjectStreamFactory | Re: AccessControlException with Wicket on Google App Engine (GAE)

2009-11-02 Thread Igor Vaynberg
that should most likely work without problems. -igor On Mon, Nov 2, 2009 at 1:47 AM, Andreas Maza wrote: > just to circumvent the problem for a while, I am thinking of the following > workaround: > > what would be the implications if I change the implementation of > IObjectStreamFactor.DefaultOb

DefaultObjectStreamFactory | Re: AccessControlException with Wicket on Google App Engine (GAE)

2009-11-02 Thread Andreas Maza
just to circumvent the problem for a while, I am thinking of the following workaround: what would be the implications if I change the implementation of IObjectStreamFactor.DefaultObjectStreamFactory so that newObjectInputStream() and newObjectOutputStream return the regular JDK ObjectInputSt