AW: Avoid serialization troubles with static members

2009-02-19 Thread Christian Helmbold
Thanks for your answer. Wouldn't it be sufficient to use a static member to hold a reference to a service? i.e. public class SomeWicketComponent{ private static MyService service; // ... } How would you intialize these? Would you have a static getter, and force yourself

Re: AW: Avoid serialization troubles with static members

2009-02-19 Thread Michael Sparer
if the org.apache is missing, you're using an old version of wicket. check your dependencies for 1.2 versions (the version before wicket moved to apache) for the DI stuff: I'm using the annotation approach throughout my applications and never had any problems regards, Michael

AW: AW: Avoid serialization troubles with static members

2009-02-19 Thread Christian Helmbold
if the org.apache is missing, you're using an old version of wicket. I use Wicket 1.4 RC2. Maybe I use an old version (1.2.7) of the Spring integration. Where can I get the current version? http://cwiki.apache.org/WICKET/spring.html says nothing about where to download it (without maven)..

Re: AW: AW: Avoid serialization troubles with static members

2009-02-19 Thread Michael Sparer
then I'd recommend using maven (or similar) :-) managing all dependencies manually seems to me quite masochistically and yepp, you're using an old version of spring integration then ... christian.helmbold wrote: if the org.apache is missing, you're using an old version of wicket. I use

Re: AW: AW: Avoid serialization troubles with static members

2009-02-19 Thread James Carman
Yes, but if the frameworks and tools can make you actually more productive, why not use them? The @SpringBean annotation-based approach just works. I've never had any troubles with it and I really don't have to think about it. There's a very shallow learning curve, especially if you're already

Re: AW: Avoid serialization troubles with static members

2009-02-19 Thread Martijn Dashorst
If you don't want to use maven, then download the distribution of Wicket, and look in the lib folder. All the wicket jars are there. How did you get wicket-1.4-rc2.jar then? Martijn On Thu, Feb 19, 2009 at 12:10 PM, Christian Helmbold christian.helmb...@yahoo.de wrote: if the org.apache is

Re: AW: AW: Avoid serialization troubles with static members

2009-02-19 Thread Jeremy Thomerson
vi is not only a tool, but a whole platform, so that would exclude it. Personally, I find that echo import org.apache.wicket.* MyClass.java echo import java.util.* MyClass.java works best. :) j/k j/k -- Jeremy Thomerson http://www.wickettraining.com On Thu, Feb 19, 2009 at 10:40 AM, Igor

Re: AW: AW: Avoid serialization troubles with static members

2009-02-19 Thread John Krasnay
javac is kinda redundant too. Real men sling raw bytecode. jk On Thu, Feb 19, 2009 at 12:02:36PM -0600, Jeremy Thomerson wrote: vi is not only a tool, but a whole platform, so that would exclude it. Personally, I find that echo import org.apache.wicket.* MyClass.java echo import