Title: RE: [JBoss-user] Developing and debuging
The worst part of J2EE in general,not only jboss specific, is debugging and testing. It is so difficult to set up environment in which you could change a line, hit compile and test it, and the whole process would take say 10 seconds. Impossilble
on development and I am only a lowly practitioner of
the craft, certainly no master.
Regards,
JonB
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ivan Bolcina
Sent: Friday, 20 June 2003 8:12 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Developing
You could always move to WebSphere. I've seen that take upwards
of an hour to deploy things! :-)
--
Danny Yates
-Original Message-
From: Peng Zhao [mailto:[EMAIL PROTECTED]
Sent: 17 June 2003 22:40
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Developing and debuging
I met a big
You could always move to WebSphere. I've seen that take upwards
of an hour to deploy things! :-)
--
Danny Yates
Or you could go back to the good old days, when Tomcat was in a separate
VM and you either coded in a deployment kicker or stopped, deleted the WAR
and restarted Tomcat.
I also
If I deploy the application as a directory (e.g. app.war), the .jsp can
be reloaded when I replace a .jsp file in the directory. But the .class
file can not be updated once it has run. It seems the jboss has a cache
for the loaded .class file.
I think:
If you try to re-deploy the application
On Wed, 18 Jun 2003 07:39, Peng Zhao wrote:
I met a big problem when developing and debuging.
If I deploy the application as a war file, the jboss needs about 30
seconds to deploy it. Although it is not too long, for developing and
debuging it is not affordable! The time for waiting is longer
