Somewhat I cannot run a webapp configuration anymore on 1151

Tomcat 5.0 starts but my webapp is not deployed. The working directory under IDEA_HOME/system is empty.
I converted my project that was working fine under 1147 to 1151.

Anybody seen that behavior?

Jacques

8 comments

Jacques Morel wrote:

Tomcat 5.0 starts but my webapp is not deployed. The working directory under IDEA_HOME/system is empty.
I converted my project that was working fine under 1147 to 1151.

Anybody seen that behavior?


HA! I thought it was me last night freaking out and not seeing what was
going on. The problem seems that there is a change in that plugin, as I
discovered while trying to write the resin plugin based on this one, and
noticed that idea is trying to look for files in the
.Intellij/system/tomcat(numbers here)/webroot/webroot, and those dirs
don't exist.

So in fact it's NOT me. I'd better revert to 1147 before I open any
project with 1151 and go busting everything.

R

0

Jacques Morel wrote:

Tomcat 5.0 starts but my webapp is not deployed. The working directory under IDEA_HOME/system is empty.
I converted my project that was working fine under 1147 to 1151.

Anybody seen that behavior?


Hey Jacques,

I filed a bug on this with my own stack trace which Tomcat chucks up
when it fails. I'm thinking this is a regression in the plugin itself
since it seems some classes are still being removed/refactored in the
J2EE api. I just ran across this because of my resin 3.x plugin (under
development) failing hard. Seems some classes don't exist anymore, I
think what ever is being changed includes some new code which is
throwing a fit.

Weird to have all this at this stage of the game, I hope it's for good
reasons... like auto deploy of JSPs, opening of the j2ee api or
something real useful like that.

R

0

I have too regressed to 1147. Unfortunately my project did not work anymore! I takes me 10mn to setup everything!

I agree also that it is rather disturbing that a so central feature of web application development could regress at this point in the game. This seems to be under the category of "happy path" testing but obviously I must be mistaken.
It would be interesting to hear JetBrains position on this.

Anyway, what is the bug you filed? Was it specific to your resin plugin? I was going to file a bug based on the feedback I got in this thread.

Jacques

0

Jacques Morel wrote:

I have too regressed to 1147. Unfortunately my project did not work anymore! I takes me 10mn to setup everything!

I agree also that it is rather disturbing that a so central feature of web application development could regress at this point in the game. This seems to be under the category of "happy path" testing but obviously I must be mistaken.
It would be interesting to hear JetBrains position on this.

Anyway, what is the bug you filed? Was it specific to your resin plugin? I was going to file a bug based on the feedback I got in this thread.


I filed 2, one to find out what the heck happened to the api and the
other for Tomcat.

This is my Tomcat bug:
http://www.intellij.net/tracker/idea/viewSCR?publicId=29414

Seems there was a similar issue fixed, but this one is a bit different
(of course... seems everything I do is different...)

The Resin issue, turns out the files I was using in the API are no
longer there... hence my frustration with the fact that the API is still
a moving target during RC, and wondering if there was any good reason
for it.

R

0

These are all issues specific to tomcat, rather than the webapp support (so it isn't quite as bad as it seems). I've been able to get the orion plugin working with every version so far with minimal hassle.

0

All you need to do is to try to fix the plugin, or you may use the one I
fixed, worked well with Tomcat 4 and 5.


"Jacques Morel" <jacmorel@yahoo.com> wrote in message
news:10284014.1076399904464.JavaMail.itn@is.intellij.net...

Tomcat 5.0 starts but my webapp is not deployed. The working directory

under IDEA_HOME/system is empty.

I converted my project that was working fine under 1147 to 1151.

>

Anybody seen that behavior?

>

Jacques






Attachment(s):
tomcatIntegration.jar
0

You are right Hani. This is specific to Tomcat. As I just discovered the problem I describe earlier seems to be related to an incorrect clean up of tomcat config files by the integration plugin.
However I cannot but laugh at the fact that 1154 tomcat integration has a missing class and 1154 is supposed to be RC II! You have to appreciate the irony.

Jacques

0

Hani Suleiman wrote:

These are all issues specific to tomcat, rather than the webapp support (so it isn't quite as bad as it seems). I've been able to get the orion plugin working with every version so far with minimal hassle.


Hani, did you base yours on the Tomcat configs or did you somehow manage
to get through the undocumented API?

(just curious because I backed off finishing up the resin plugin until
they get the refactoring they seem to be doing done)

R

0

Please sign in to leave a comment.