Re: It is not a good idea to reference the Session instance in models directly as it may lead to serialization problems.
Sorry not second, first.
2012/1/4 Rahman USTA
> Second answer is ok, very thanks.
>
>
> 2012/1/4 Wilhelmsen Tor Iver
>
>> // Indirection for PropertyModel object
>> public class MySessionModel extends AbstractReadOnlyModel {
>>
>>public MySession getObject() {
>>return (MySession) Session.get();
>>}
>> }
>>
>> - Tor Iver
>>
>> -Original Message-
>> From: Rahman USTA [mailto:rahman.usta...@gmail.com]
>> Sent: 4. januar 2012 10:45
>> To: users@wicket.apache.org
>> Subject: It is not a good idea to reference the Session instance in
>> models directly as it may lead to serialization problems.
>>
>> Hi, i have a MySession.
>>
>> form.add(new TextField("name",new
>> PropertyModel(((MySession)getSession()),"
>> user.name")));
>>
>> I have a User user; in MySession, then initialized in constructor.
>>
>> my Goal is to save name and surname user's own session. i did it above,
>> but
>> warning ide me so that ;
>>
>> *WARN - AbstractPropertyModel - It is not a good idea to reference
>> the Session instance in models directly as it may lead to serialization
>> problems. If you need to access a property of the session via the model
>> use
>> the page instance as the model object and 'session.attribute' as the
>> path.*
>>
>> How can i handle this normally.
>>
>>
>>
>>
>> --
>> Rahman USTA
>> Computer & Control Education Technologist
>> 0-(531)-922-28-05
>> www.kodcu.com
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
> --
> Rahman USTA
> Computer & Control Education Technologist
> 0-(531)-922-28-05
> www.kodcu.com
>
>
--
Rahman USTA
Computer & Control Education Technologist
0-(531)-922-28-05
www.kodcu.com
Re: It is not a good idea to reference the Session instance in models directly as it may lead to serialization problems.
Second answer is ok, very thanks.
2012/1/4 Wilhelmsen Tor Iver
> // Indirection for PropertyModel object
> public class MySessionModel extends AbstractReadOnlyModel {
>
>public MySession getObject() {
>return (MySession) Session.get();
>}
> }
>
> - Tor Iver
>
> -Original Message-
> From: Rahman USTA [mailto:rahman.usta...@gmail.com]
> Sent: 4. januar 2012 10:45
> To: users@wicket.apache.org
> Subject: It is not a good idea to reference the Session instance in models
> directly as it may lead to serialization problems.
>
> Hi, i have a MySession.
>
> form.add(new TextField("name",new PropertyModel(((MySession)getSession()),"
> user.name")));
>
> I have a User user; in MySession, then initialized in constructor.
>
> my Goal is to save name and surname user's own session. i did it above, but
> warning ide me so that ;
>
> *WARN - AbstractPropertyModel - It is not a good idea to reference
> the Session instance in models directly as it may lead to serialization
> problems. If you need to access a property of the session via the model use
> the page instance as the model object and 'session.attribute' as the path.*
>
> How can i handle this normally.
>
>
>
>
> --
> Rahman USTA
> Computer & Control Education Technologist
> 0-(531)-922-28-05
> www.kodcu.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Rahman USTA
Computer & Control Education Technologist
0-(531)-922-28-05
www.kodcu.com
RE: It is not a good idea to reference the Session instance in models directly as it may lead to serialization problems.
// Indirection for PropertyModel object
public class MySessionModel extends AbstractReadOnlyModel {
public MySession getObject() {
return (MySession) Session.get();
}
}
- Tor Iver
-Original Message-
From: Rahman USTA [mailto:rahman.usta...@gmail.com]
Sent: 4. januar 2012 10:45
To: users@wicket.apache.org
Subject: It is not a good idea to reference the Session instance in models
directly as it may lead to serialization problems.
Hi, i have a MySession.
form.add(new TextField("name",new PropertyModel(((MySession)getSession()),"
user.name")));
I have a User user; in MySession, then initialized in constructor.
my Goal is to save name and surname user's own session. i did it above, but
warning ide me so that ;
*WARN - AbstractPropertyModel - It is not a good idea to reference
the Session instance in models directly as it may lead to serialization
problems. If you need to access a property of the session via the model use
the page instance as the model object and 'session.attribute' as the path.*
How can i handle this normally.
--
Rahman USTA
Computer & Control Education Technologist
0-(531)-922-28-05
www.kodcu.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: It is not a good idea to reference the Session instance in models directly as it may lead to serialization problems.
Just translate the warning into code:
form.add(new TextField("name",new PropertyModel(this, "session.user.name")));
Sven
Am 04.01.2012 10:44, schrieb Rahman USTA:
Hi, i have a MySession.
form.add(new TextField("name",new PropertyModel(((MySession)getSession()),"
user.name")));
I have a User user; in MySession, then initialized in constructor.
my Goal is to save name and surname user's own session. i did it above, but
warning ide me so that ;
*WARN - AbstractPropertyModel - It is not a good idea to reference
the Session instance in models directly as it may lead to serialization
problems. If you need to access a property of the session via the model use
the page instance as the model object and 'session.attribute' as the path.*
How can i handle this normally.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
It is not a good idea to reference the Session instance in models directly as it may lead to serialization problems.
Hi, i have a MySession.
form.add(new TextField("name",new PropertyModel(((MySession)getSession()),"
user.name")));
I have a User user; in MySession, then initialized in constructor.
my Goal is to save name and surname user's own session. i did it above, but
warning ide me so that ;
*WARN - AbstractPropertyModel - It is not a good idea to reference
the Session instance in models directly as it may lead to serialization
problems. If you need to access a property of the session via the model use
the page instance as the model object and 'session.attribute' as the path.*
How can i handle this normally.
--
Rahman USTA
Computer & Control Education Technologist
0-(531)-922-28-05
www.kodcu.com
