Problem using Tomcat 4.1.24
I get this error trying to start Tomcat 4.1.24:
I did some searching and found this page that claims to fix it, but am having trouble understanding how to do this: http://kinabalu.blog-city.com/readblog.cfm?BID=31846
Please sign in to leave a comment.
Tomcat 4.1.x is not supported by the plugin. Please check out relevant discussions in this group.
--
Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"
When will Tomcat 4.1.24 be supported? Is this a planned enhancement?
Thanks
There is no way to support 4.1.xx because they've removed any JSP
debugging and that would make the plugin useless. Wait until Tomcat 5
with JSR45 support and then they will update the plugin, or one of us
will create one. IN the mean time develop with 4.0.6 (like everyone
else on the planet does) and deploy on 4.1.24... no difference betweent
the two for what you want to do.
R
Jay Sissom wrote:
It's interesting that you can't develop under 4.1.24. We do it in JBuilder all the time. Some people on the planet can use Tomcat 4.1.24.
I don't care about debugging JSP's under it. I just want IntelliJ to be able to start and stop Tomcat when I do run. JBuilder can do that fine. JBuilder can also debug JSP's under 4.1.24.
I have been evaluating IntelliJ thinking we may switch from JBuilder, but it seems that JBuilder can do the impossible and IntelliJ can't... :)
Too bad.
Jay
able to start and stop Tomcat when I do run. JBuilder can do that fine.
JBuilder can also debug JSP's under 4.1.24.
If it's just a question about starting/stopping tomcat, why don't you use
the start/stop service ?
Or use the tomcat ant task for that ? And assign it a shortcut ?
it seems that JBuilder can do the impossible and IntelliJ can't... :)
If you stop evaluating IntelliJ because JBuilder can start/stop Tomcat when
IntelliJ can't, it means that you havent evaluated both tools well. You
forget to compare all the features that enable you to improve your
productivity by a factor of two.
That's a pity.
Guillaume
+1 Guillaume
Also if you're so hard up on developing with Tomcat 4.1.x why don't you
look at the source code for the Tomcat plugin and change the 2-3 lines
of code which prevent it from starting up, and then you're done. The
Tomcat plugin source can be found in the Tomcat plugin from IntelliJ
inside the jar file.
Will JBuilder give you the source code to their magical plugin?
R
Guillaume Laforge wrote:
>>I don't care about debugging JSP's under it. I just want IntelliJ to be
>>I have been evaluating IntelliJ thinking we may switch from JBuilder, but
Jay Sissom wrote:
No JBuilder spends lots of useless money to do something which is really
not a necessity and charge you a lot of money for it... but hey it's not
MY money and time...
Too bad that's all it takes for you to pick an IDE.
R
I also forgot to say that it is also possible to define a tool for using any
program.
For instance, I did that for starting Word, and I used a macro to pass the
selected file as argument.
So you can define a tool for starting/stopping tomcat using the
startup/shutdown scripts.
If you don't care about JSP debugging, you can easily define a shortcut to a
"tool" you've just defined.
So, before bashing IntelliJ, try to evaluate it more thouroughly.
Guillaume
Wow! All of the "nice" people on this thread giving me help. I just can't believe how "nice" people are around here. Really makes me want to use this product.
For your information, I am not finished evaluating the product. I asked a simple question and got flamed and was told no one in the planet would even want to do what I want to do. Obviously others on this planet are interested because I replied to someone else asking a similar question. The flamer told me that it was totally impossible to have IntelliJ start up tomcat 4.1. It sounds like this "expert" might not be such an expert after all?
If I just need to change 3-4 lines of code in this plugin, can you please tell me where the source code is and point me to the 3-4 lines of code that need to be changed? I'm not an expert on IntelliJ like all of you obviously are.
I guess when I keep evaluating the product, I'll try not to ask questions here because obviously, this forum isn't for people who aren't experts. Is this the only place for support for the product? If so, that is much more troubling than the tomcat issue.
I didn't come here to start a fight. I just wanted an a simple answer.
I think you're completely right. There is no use to get so upset about your question.
After all, I think the optimal way to go would be, JetBrains implementing the start/stop behaviour, but flagging a message "JSP debugging does not work as Tomcat 4.1.x contains a careless rewritten Jasper version bla bla ..." or similar evertime I try to set a JSP breakpoint.
I think this will be best because of:
- it's a regular question if the plugin supports 4.1.xxx, and most of those who ask don't care about JSP debugging
- as the plugin is contained in the product and to be considered a moving target, it is tiresome to reapply a handmade patch on every new build
And lastly, does anybody know how JBuilder achieves the debugging aspect? Do they cheat by silently using Jasper 1?
We didn't jump on you, this question comes up often and JetBrains often
responds the same way and so do the users. Generally the inforamtion is
in the list.
I described in my email where the source code was, in the plugin jar
file inside the IDEA Plugin directory. Look there.
Generally when people ask to use Tomcat they do so not because they need
to start and stop it only, but for JSP debugging. If you wanted to
start and stop it, you can do so with just about any process in IDEA,
the only part you need to know is the main class. You can even remote
debug.
There is a separate tech support address you can use for 'official' tech
support, and that's listed on the main site, I don't know what it is.
Which lines need to be changed, I don't remember, but you might want to
check www.intellij.org, the wiki site, there are lots of plugins there
and someone might have already done it...
There... does that help, am I being "nicer" now?
R
P.S. I used to be a JBuilder user, 'nice' is not even in the vocab over
there. Complain a little too much and you get tossed out.
Jay Sissom wrote:
Jay,
here because obviously, this forum isn't for people who aren't experts. Is
this the only place for support for the product? If so, that is much more
troubling than the tomcat issue.
This is community forum dedicated to early access preview of the version in
development. It is not moderated by JetBrains anyhow. On other side please
do not hesitate to contact the support team (link came with your evaluation
licesnse e-mail) whoes purpoes is exactly answering your questions.
--
Best regards,
Maxim Shafirov
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"
"Jay Sissom" <no_mail@jetbrains.com> wrote in message
news:32254775.1058722745612.JavaMail.itn@is.intellij.net...
can't believe how "nice" people are around here. Really makes me want to
use this product.
>
simple question and got flamed and was told no one in the planet would even
want to do what I want to do. Obviously others on this planet are
interested because I replied to someone else asking a similar question. The
flamer told me that it was totally impossible to have IntelliJ start up
tomcat 4.1. It sounds like this "expert" might not be such an expert after
all?
>
tell me where the source code is and point me to the 3-4 lines of code that
need to be changed? I'm not an expert on IntelliJ like all of you obviously
are.
>
here because obviously, this forum isn't for people who aren't experts. Is
this the only place for support for the product? If so, that is much more
troubling than the tomcat issue.
>
>
Since noone really seems to be helping you, here is how we develop under Tomcat 4.1.24:
1.) Add a Tomcat Library to your project classpath. Include all of the jars in the following dirs:
- $TOMCAT_HOME/common/lib
- $TOMCAT_HOME/common/endorsed
- $TOMCAT_HOME/bin
- $TOMCAT_HOME/server/lib
2.) Then, create a new class called TomcatLoader and put it in your classpath somewhere. I've attached the one that we use.
3.) Create a new Application Debug Configuration. Call it Tomcat, or whatever you want. Set the Main class to TomcatLoader, set any VM -D params that you need in the VM parameters box, and put the word start into the Program Parameters box.
3a.) The Working directory can be anywhere you want, as long as you copy in Tomcat's conf directory so that you have a valid server.xml, etc.
That should be it! Hit Debug on this config and all should start up normally. I'll try to help you out if you have any questions.
Attachment(s):
TomcatLoader.java
I'm not sure how JBuilder does it. I've never needed to know because it does it all for you.
Here's information on how Eclipse can do it:
http://www.sysdeo.com/eclipse/tomcatPlugin.html
Jay