Updating JSP causes Workspace to auto rebuild.. causing Tomcat to
restart :(
I'm now turning off auto build when working in jsp's, obviously
forgetting to switch it on when doing java class changes
Any other way this can be solved?
Jacob Willig
ING Bank
Europe Web Team
OPSIT/ADC GS/AM COSS/EWT
I probably should not respond, but obviously I could not stop myself
from doing so..
1: How sure can we be that Mark wrote the message about him being fired
over this
2: If he did write this, AND the message is true, it seems far fetched
that one gets fired over just posting in this thread
I very much like the ease of use of struts (yes it need some
improvements still) and everytime I encounter a lack of functionality
building my JSP I will have to ask myself if this is lack of
functionality or simply an attempt of me to put too much logic into the
JSP...
Sofar I could handle all
btw I use Eclipse 3.0.1 with several cool plugins for building and
testinf my webapplications... Sofar it rocks. The new features in 3.2
make it even more user friendly and easier to work with..
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: donderdag 30 juni
Jeroen,
I would put a try catch block around the getBlogItem method:
public Iterator getBlogItem()
{
try {
Session session =
HibernateUtil.currentSession();
Transaction tx = session.beginTransaction();
Query query = session.createQuery(select b
from
First: It seems wrong to tell the user that an id does not exist! It
goesd against security conventions!
Second.. I think you should do something like this:
errors.add(Application.GLOBAL_ERRORS, new
ActionError(err.app.login.invalid,txtLoginId ));
With your ,messageresource having a line:
First thing that comes to mind is that you likely forgot to add the key
to the resource..
Try adding the null=true option to your resource declarations in
struts-config.xml
-Original Message-
From: Gilbert, Antoine [mailto:[EMAIL PROTECTED]
Sent: donderdag 23 juni 2005 15:41
To: Struts
7 matches
Mail list logo
