Yes, of course, but I'm in the same position as the one who posed the
question: looking for the answer. I inferred from what was written that
de-/serialization was handled by @SpringBean, but since I haven't had time
to do a full code review, I don't know the details of how it all works, and
Serialization/deserialization is handled for you automatically.
On Thu, Sep 25, 2008 at 9:33 PM, Ari M [EMAIL PROTECTED] wrote:
I see nothing on the wiki page under Annotation-based Approach concerning
serialization. The other approaches discuss serialization issues, but not
this one. Am I
I see nothing on the wiki page under Annotation-based Approach concerning
serialization. The other approaches discuss serialization issues, but not
this one. Am I missing something? If it said something like
serialization/de-serialization handled automatically, that would be clear.
Thanks,
BTW, I did note that it said It's possible to have your annotated
dependencies automatically injected on construction. By this I inferred
that de-/serialization was handled, but it could be made more explicit, as
it is for the other approaches.
Ari
Ari M wrote:
I see nothing on the wiki
its a wiki, you can always update it...
-igor
On Thu, Sep 25, 2008 at 6:38 PM, Ari M [EMAIL PROTECTED] wrote:
BTW, I did note that it said It's possible to have your annotated
dependencies automatically injected on construction. By this I inferred
that de-/serialization was handled, but it
jwcarman wrote:
Why are you doing this again? @SpringBean already takes care of
re-establishing the connection upon deserialization.
Are you sure ?
Sebastiaan van Erk wrote:
The myService field is filled with a proxy to the service which is
serializable and can look up
the service
You don't have to mark your field as transient. The proxy is indeed
serializable (at least the object that it writeReplaces itself with
is) and will re-establish itself upon deserialization.
On Tue, Jul 29, 2008 at 4:11 AM, Gerald Reinhart [EMAIL PROTECTED] wrote:
jwcarman wrote:
Why are
On Tue, Jul 29, 2008 at 1:11 AM, Gerald Reinhart [EMAIL PROTECTED] wrote:
jwcarman wrote:
Why are you doing this again? @SpringBean already takes care of
re-establishing the connection upon deserialization.
Are you sure ?
read the spring page on the wiki
-igor
Sebastiaan van Erk
We use Findbugs on our build process, with this
@SpringBean(name = mySpringBean)
private MyPOJO config;
Findbugs Warning :
Class com...MyPage defines non-transient non-serializable instance
field config Bug type SE_BAD_FIELD (click for details)
In class com...MyPage Field
so you decrease the efficiency of your application so that your static
analysis tool stops reporting false positives?
-igor
On Tue, Jul 29, 2008 at 8:10 AM, Gerald Reinhart [EMAIL PROTECTED] wrote:
We use Findbugs on our build process, with this
@SpringBean(name = mySpringBean)
private
Hi Gerald,
Don't forget Findbugs is a static code analysis tool, so it can't
figure out everything. To get rid of these (false) warnings you could
for instance disable these specific warnings in FindBugs for wicket
classes that are injected by Spring using FindBugs filters. See
I've implemented a little solution to inject SpringBean of Wicket Pages on
the un-serialization event :
1 - Make the SpringContext available in a static way :
public class MyWebApplication extends SpringWebApplication {
private static ApplicationContext springApplicationContext = null ;
Why are you doing this again? @SpringBean already takes care of
re-establishing the connection upon deserialization.
On Mon, Jul 28, 2008 at 11:49 AM, Gerald Reinhart
[EMAIL PROTECTED] wrote:
I've implemented a little solution to inject SpringBean of Wicket Pages on
the un-serialization
Hi Daniel
I've marked it transient, so looking forward to the replies you get..
regards Nino
dfernandez wrote:
Hello everyone,
I have a question regarding the relation between the @SpringBean annotation
and the serialization of objects being referenced in a Page. If I have:
hi daniel,
May I suppose that the proxy object that @SpringBean will create for
myService will handle serialization properly? (this is, forgetting about
the reference to the Spring object when serializing, and retrieving it again
when de-serializing...)
that's how it works AFAIK, so marking it
dfernandez wrote:
Hello everyone,
I have a question regarding the relation between the @SpringBean annotation
and the serialization of objects being referenced in a Page. If I have:
@SpringBean(name=myBean)
protected MyService myService;
May I suppose that the proxy object that @SpringBean
correct
-igor
On Feb 7, 2008 4:43 AM, Sebastiaan van Erk [EMAIL PROTECTED] wrote:
dfernandez wrote:
Hello everyone,
I have a question regarding the relation between the @SpringBean annotation
and the serialization of objects being referenced in a Page. If I have:
the custom serialization is already off by default for quite some time
the
org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
only kicks in (so also for the default) when an IOException happens with
writeObject
So that you get a nice trace which field it exactly is of
18 matches
Mail list logo
