I think it is to specific. You can override the Session on your app an catch
this situation like:
private void writeObject(java.io.ObjectOutputStream out) throws
IOException {
if (Application.get() != null &&
Application.get().getConfigurationType().equals(Application.DEPLOYMENT)) {
log.info("Session is being serialized in the development
environment, which is an not a desirable behavior.");
}}
but than some other developers can complain because they are deliberated
serialializing some session.
On Wed, Nov 17, 2010 at 4:49 PM, Erik van Oosten <[email protected]>wrote:
> Shouldn't serialization fail when it references session/application?
> Perhaps only in development mode.
>
> Regards,
> Erik.
>
> Op 16-11-10 19:03, Igor Vaynberg schreef:
>
> added a log warning to property models when they reference session.
>>
>> -igor
>>
>> On Tue, Nov 16, 2010 at 9:46 AM, Douglas Ferguson
>> <[email protected]> wrote:
>>
>>> We found it.. Finally!!!
>>>
>>> There was a property model that was using the session as the model
>>> object.
>>>
>>> It would be cool if PropertyModel, etc would check for this and blow up
>>> on construction.
>>> i.e. not allow Page, Session, Application as the model object...
>>>
>>
>>
>
> --
> Erik van Oosten
> http://www.day-to-day-stuff.blogspot.com/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Pedro Henrique Oliveira dos Santos
