JSP deploy with J2EE WebModule REALLY REALLY bad! (JetBrains please read)

I think there is a feature request for this, but after working with JSPs
all week here with 1050, we really really need to get this resolved it's
horrible!

In the current setup, since we have to deploy to an exploded directory,
every time I change a jsp page, even minute change, I have to click make
in order for that jsp to get copied over, so I can run and debug it.
YIKES! I was thinking it wouldn't be too bad, so I started pushing and
trying to ignore it, but that just because a real burden.

The problem is that clicking make will cause the container to reload,
because you seem to copy the web.xml on every make, in order to force a
reload of the web container. Well, that's all fine and dandy, but when
working with changes to a jsp page, you rarely if ever need to touch
web.xml.

We need to have a way where if a jsp page is modified, that idea will
automatically hotswap it for us and all we need is to click reload.

This is a pretty nasty usability issue which has to be resolved for 4.0.
Besides that, everything was running real well.

Thanks
R

7 comments
Comment actions Permalink

Hello,

because of having different configurations for development, testing and production (mail addresses, databases, a.s.o). I 'm using Ant for deploying. When just web components have changed wich doesn't need a reloading, i invoke a task which just copies *.html, *.js, *.css, *.jsp, ... into the appropriate directories. Works fine for me and works in every environment.

Regards
Reto

0
Comment actions Permalink

Reto Badertscher wrote:

Hello,

because of having different configurations for development, testing and production (mail addresses, databases, a.s.o). I 'm using Ant for deploying. When just web components have changed wich doesn't need a reloading, i invoke a task which just copies *.html, *.js, *.css, *.jsp, ... into the appropriate directories. Works fine for me and works in every environment.


Of course that works, my comment was regarding what idea does, and even
clicking ant to copy files over is not appropriate since we never had to
do this in 3.0.5. I am trying to get the process to be a bit more
fluid, where idea on its own should just know that the jsp page changed,
and it should therefore use the new version on the next browser reload.

I believe it can be done since when I'm debugging I debug the jsp file
that is part of the web module, not the one in the exploded directory,
so that tells me they know where the file is, and hence they should know
to re read it when it changes.

R

0
Comment actions Permalink

I desperately hope it'll be possible to run without building a war or have an exploded dir, for those of us who are sane enough to layout their webapp correctly (ie, just the way the container expects them)

0
Comment actions Permalink

Is it asking too much to be able to develop against the actual webapp
directory like 3.0.5? I usually run a separate instance of tomcat, while
developing underneath it. This way, tomcat will pick up JSP changes on it's
own.


"Hani Suleiman" <hani@formicary.net> wrote in message
news:13019180.1073232503388.JavaMail.itn@is.intellij.net...

I desperately hope it'll be possible to run without building a war or have

an exploded dir, for those of us who are sane enough to layout their webapp
correctly (ie, just the way the container expects them)


0
Comment actions Permalink

Norris Shelton wrote:

Is it asking too much to be able to develop against the actual webapp
directory like 3.0.5? I usually run a separate instance of tomcat, while
developing underneath it. This way, tomcat will pick up JSP changes on it's
own.


That would be the same as what I mention. Also in 4.0 when you save
changes to classes or xml files, IDEA is very good about reloading the
web container, it even does it for struts-config.xml and tiles-def.xml,
which Tomcat won't do when run on its own without pushing it to somehow.

R

0
Comment actions Permalink

+ one million trillion zillion etc...

"Norris Shelton" <nshelton@appriss.com> wrote in message
news:btc0k8$h77$1@is.intellij.net...

Is it asking too much to be able to develop against the actual webapp
directory like 3.0.5? I usually run a separate instance of tomcat, while
developing underneath it. This way, tomcat will pick up JSP changes on

it's

own.

>
>

"Hani Suleiman" <hani@formicary.net> wrote in message
news:13019180.1073232503388.JavaMail.itn@is.intellij.net...

I desperately hope it'll be possible to run without building a war or

have

an exploded dir, for those of us who are sane enough to layout their

webapp

correctly (ie, just the way the container expects them)

>
>


0
Comment actions Permalink

Argh. Now I see the problem. Build 1050 does not support non-/WEB-INF tld
files.



"Robert S. Sfeir" <robert@codepuccino.com> wrote in message
news:btc1ch$ldb$1@is.intellij.net...

Norris Shelton wrote:

Is it asking too much to be able to develop against the actual webapp
directory like 3.0.5? I usually run a separate instance of tomcat,

while

developing underneath it. This way, tomcat will pick up JSP changes on

it's

own.

>

That would be the same as what I mention. Also in 4.0 when you save
changes to classes or xml files, IDEA is very good about reloading the
web container, it even does it for struts-config.xml and tiles-def.xml,
which Tomcat won't do when run on its own without pushing it to somehow.

>

R



0

Please sign in to leave a comment.