WebApps & Tomcat in 2132 - bugs, bugs, bugs...

Deploying a webapp to Tomcat 5 seems hosed in 2132 - trying to deploy to
a context of "/helloworld" ends up generating a file called
'elloworld.xml' (first character is chopped off), with the context path
attribute specified as "helloworld" instead of "/helloworld". As such,
deployment fails with Tomcat complaining about an invalid context path.

Also, the browser path specified in the 'General' control panel also
seems to be ignored all of a sudden.

These issues are new since 2126, which I was using up until this
morning. The main problem with 2126 was that trying to launch a debug
Tomcat configuration locked the machine up if there were any breakpoints
set. I could mostly work around this by launching the debug session
without breakpoints and setting them once everything was up and running,
but thought I'd see if it was still a problem in 2132 before filing a
bug. Now I can't even get as far as launching because of these new
problems. Unfortunately, and foolishly, I got rid of 2126 and it's
installer before testing 2132. Huh.


And what's with the empty DOS box hanging around all of a sudden?

Rik Gibson

2 comments
Comment actions Permalink

Somewhat related to the 'launch browser' checkbox...why is this checked by default? It's one more thing for the user to do (ie, right now they have to either uncheck it, or enter a url). It'd be nice if it were checked off by default, so someone who wants to just launch their webapp can do so with minimal clicking around.

0
Comment actions Permalink

Rik wrote:

Deploying a webapp to Tomcat 5 seems hosed in 2132 - trying to deploy to
a context of "/helloworld" ends up generating a file called
'elloworld.xml' (first character is chopped off), with the context path
attribute specified as "helloworld" instead of "/helloworld". As such,
deployment fails with Tomcat complaining about an invalid context path.


Found an odd workaround: if I select the web-app in the 'Deployment' tab
of the Tomcat debug configuration and specify the application context as
'//helloworld', then I now get a correctly named 'helloworld.xml' with a
context path of '/helloworld'. Specifying an app context of either
'helloworld' or '/helloworld' generates the unusable file mentioned
previously.

0

Please sign in to leave a comment.