I'll repeat my plea for patience as I'm new to Java and Wicket, but have some
minimal experience with ASP.net forms (not MVC). I've reached that point in the
learning process where I want to interact with a database and I wish to use
entities and Hibernate to make it easier. From what I've
describe, since (1) the entity does not need to
be reloaded on subsequent requests, and since it's object reference is
transient (2) it goes away as soon as another page is accessed, and (3) it
does not get replicated among the cluster.
Best of luck,
Dan
On Fri, May 4, 2012 at 2:40 PM, JASON
I'm new to Java and Wicket. My only previous experince with web applications
has been with Asp.net forms (not MVC). Please be patient; coming from the
postback event paradigm, I'm struggling to grasp the concepts in Wicket. In my
simple scenario, assume there is no AJAX. I need to build the
Thanks for your help. I included the properties file in a separate jar.
From: toriv...@arrive.no
To: users@wicket.apache.org
Date: Thu, 29 Mar 2012 08:38:57 +0200
Subject: RE: log4j.properties
Additionally you can put log4j.properties in its own jar and put it in
$tomcat/lib.
I'm new to Java, Tomcat, and Wicket. I apologize in advance for asking the
obvious.
Tomcat logs complain that log4j is not properly configured. I placed my
log4j.properties file in the /WEB-INF/classes folder and errors stop.
I would like ALL Wicket applications to share a single