Home » Language IDEs » ServerTools (WTP) » WST 2.0: Server for Tomcat: Enable Tomcat debug mode in WST 1.5
| |
| Re: WST 2.0: Server for Tomcat: Enable Tomcat debug mode in WST 1.5 [message #197079 is a reply to message #197067] |
Tue, 24 July 2007 13:35   |
|
Have you tried doing it the same way? did you get any problems?
Typically you wouldn't have to do any modification to your runtime to run
in debug mode.
To debug a servlet all I do is create a runtime, then a server, then launch
the server in debug mode, and that is it.
user@domain.invalid wrote in news:f84hh2$d7e$1@build.eclipse.org:
> Hello,
>
> in WST 1.5 I've used Enable Tomcat debug mode in my Tomcat server
> settings. So I was able to debug my installed tomcat without any
> changes.
>
> How can I do this with WST 2.0?
>
> Regards
>
> Georg
Regards,
--
Angel Vera
WTP Server Tools Developer
|
|
|
| Re: WST 2.0: Server for Tomcat: Enable Tomcat debug mode in WST 1.5 [message #197122 is a reply to message #197072] |
Tue, 24 July 2007 15:20 |
Eclipse User |
|
|
|
Originally posted by: user.domain.invalid
I would like to debug Tomcat (Version 5.0.x) with its web application
like it is installed and without modifications from WTP.
In WTP 1.5 it works with Enable Tomcat debug mode fine.
In WTP 2.0 I do not understand the server settings and the help is not
working (showing a xml phars error cause of not ended <div>).
org.xml.sax.SAXParseException: The element type "div" must be terminated
by the matching end-tag "</div>" on page "Creating a Tomcat server".
at
com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(D OMParser.java:264)
at
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl. parse(DocumentBuilderImpl.java:292)
at
org.eclipse.help.internal.dynamic.DocumentReader.read(Docume ntReader.java:56)
at
org.eclipse.help.internal.dynamic.XMLProcessor.process(XMLPr ocessor.java:49)
Larry Isaacs schrieb:
> In WTP 2.0, this option is still in the server editor like it is in WTP
> 1.5. However, in WTP 2.0, it has been more correctly labeled "Enable
> Tomcat debug logging". If your Tomcat is version 5.0 or later, the
> label will include "(not supported by this Tomcat version)" and the
> check box will be disabled. Logging in these Tomcat versions is
> controlled by a completely different approach and this option has little
> or no impact on the Tomcat server.
>
> What from of "debugging" were you doing in WTP 1.5 that you aren't able
> to do in WTP 2.0 without this option?
>
> Cheers,
> Larry
>
> user@domain.invalid wrote:
>> Hello,
>>
>> in WST 1.5 I've used Enable Tomcat debug mode in my Tomcat server
>> settings.
>> So I was able to debug my installed tomcat without any changes.
>>
>> How can I do this with WST 2.0?
>>
>> Regards
>>
>> Georg
|
|
|
| Re: WST 2.0: Server for Tomcat: Enable Tomcat debug mode in WST 1.5 [message #197129 is a reply to message #197122] |
Tue, 24 July 2007 16:26 |
 Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
Just so I'm clear on what you are expecting, if you turn off "Enable
Tomcat debug mode" in WTP 1.5, what "debugging" stops working?
Cheers,
Larry
user@domain.invalid wrote:
> I would like to debug Tomcat (Version 5.0.x) with its web application
> like it is installed and without modifications from WTP.
>
> In WTP 1.5 it works with Enable Tomcat debug mode fine.
>
> In WTP 2.0 I do not understand the server settings and the help is not
> working (showing a xml phars error cause of not ended <div>).
>
> org.xml.sax.SAXParseException: The element type "div" must be terminated
> by the matching end-tag "</div>" on page "Creating a Tomcat server".
> at
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(D OMParser.java:264)
>
> at
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl. parse(DocumentBuilderImpl.java:292)
>
> at
> org.eclipse.help.internal.dynamic.DocumentReader.read(Docume ntReader.java:56)
>
> at
> org.eclipse.help.internal.dynamic.XMLProcessor.process(XMLPr ocessor.java:49)
>
>
>
> Larry Isaacs schrieb:
>> In WTP 2.0, this option is still in the server editor like it is in
>> WTP 1.5. However, in WTP 2.0, it has been more correctly labeled
>> "Enable Tomcat debug logging". If your Tomcat is version 5.0 or
>> later, the label will include "(not supported by this Tomcat version)"
>> and the check box will be disabled. Logging in these Tomcat versions
>> is controlled by a completely different approach and this option has
>> little or no impact on the Tomcat server.
>>
>> What from of "debugging" were you doing in WTP 1.5 that you aren't
>> able to do in WTP 2.0 without this option?
>>
>> Cheers,
>> Larry
>>
>> user@domain.invalid wrote:
>>> Hello,
>>>
>>> in WST 1.5 I've used Enable Tomcat debug mode in my Tomcat server
>>> settings.
>>> So I was able to debug my installed tomcat without any changes.
>>>
>>> How can I do this with WST 2.0?
>>>
>>> Regards
>>>
>>> Georg
|
|
|
| Re: WST 2.0: Server for Tomcat: Enable Tomcat debug mode in WST 1.5 [message #197151 is a reply to message #197129] |
Tue, 24 July 2007 20:48 |
| Eclipse User |
|
|
|
Originally posted by: gthuelly.web.de
I've tried this flag. I was suprised that it is not neccessary for
debugging the web apps in the Tomcat!
I had to disable the flag "Run modules directly from the workspace" in
WPT 1.5.
How do I configure 2.0 to get the same result?
Thanks
Georg
Larry Isaacs schrieb:
> Just so I'm clear on what you are expecting, if you turn off "Enable
> Tomcat debug mode" in WTP 1.5, what "debugging" stops working?
>
> Cheers,
> Larry
>
> user@domain.invalid wrote:
>> I would like to debug Tomcat (Version 5.0.x) with its web application
>> like it is installed and without modifications from WTP.
>>
>> In WTP 1.5 it works with Enable Tomcat debug mode fine.
>>
>> In WTP 2.0 I do not understand the server settings and the help is not
>> working (showing a xml phars error cause of not ended <div>).
>>
>> org.xml.sax.SAXParseException: The element type "div" must be
>> terminated by the matching end-tag "</div>" on page "Creating a Tomcat
>> server".
>> at
>> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(D OMParser.java:264)
>>
>> at
>> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl. parse(DocumentBuilderImpl.java:292)
>>
>> at
>> org.eclipse.help.internal.dynamic.DocumentReader.read(Docume ntReader.java:56)
>>
>> at
>> org.eclipse.help.internal.dynamic.XMLProcessor.process(XMLPr ocessor.java:49)
>>
>>
>>
>> Larry Isaacs schrieb:
>>> In WTP 2.0, this option is still in the server editor like it is in
>>> WTP 1.5. However, in WTP 2.0, it has been more correctly labeled
>>> "Enable Tomcat debug logging". If your Tomcat is version 5.0 or
>>> later, the label will include "(not supported by this Tomcat
>>> version)" and the check box will be disabled. Logging in these
>>> Tomcat versions is controlled by a completely different approach and
>>> this option has little or no impact on the Tomcat server.
>>>
>>> What from of "debugging" were you doing in WTP 1.5 that you aren't
>>> able to do in WTP 2.0 without this option?
>>>
>>> Cheers,
>>> Larry
>>>
>>> user@domain.invalid wrote:
>>>> Hello,
>>>>
>>>> in WST 1.5 I've used Enable Tomcat debug mode in my Tomcat server
>>>> settings.
>>>> So I was able to debug my installed tomcat without any changes.
>>>>
>>>> How can I do this with WST 2.0?
>>>>
>>>> Regards
>>>>
>>>> Georg
|
|
|
| Re: WST 2.0: Server for Tomcat: Enable Tomcat debug mode in WST 1.5 [message #197190 is a reply to message #197151] |
Wed, 25 July 2007 13:09 |
Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
GT wrote:
> I've tried this flag. I was suprised that it is not neccessary for
> debugging the web apps in the Tomcat!
Thanks. That clears things up. The "-debug" option in Tomcat 4.0.x and
4.1.x was a quick way to enable debug logging in Tomcat's server related
classes. It Tomcat 5.x and later, logging is configured differently and
this option has little or no effect.
> I had to disable the flag "Run modules directly from the workspace" in
> WPT 1.5.
>
> How do I configure 2.0 to get the same result?
In WTP 2.0, the "Use Tomcat installation (takes control of Tomcat
installation)" selection in the Server Locations section is the
equivalent of unchecking "Run modules directly..." in WTP 1.5. The "Use
workspace metadata (does not modify Tomcat installation)" is equivalent
to checking "Run modules directly...".
The WTP 2.0 Tomcat plug-ins don't support moving projects from one
Tomcat server instance to another. As a result, all projects need to be
removed from the server and the server published before these selections
are enabled and changes can be made. Once the desired changes are made,
re-add the desired projects.
For an explanation of the "(takes control of Tomcat installation)", see:
http://www.eclipse.org/webtools/faq/TomcatServerFAQ.php#gett ing_started_4
I'm still working on updating this FAQ with WTP 2.0 information, but
this aspect is relevant to WTP 2.0 as well as WTP 1.5.
Cheers,
Larry
>
> Thanks
>
> Georg
>
> Larry Isaacs schrieb:
>> Just so I'm clear on what you are expecting, if you turn off "Enable
>> Tomcat debug mode" in WTP 1.5, what "debugging" stops working?
>>
>> Cheers,
>> Larry
>>
>> user@domain.invalid wrote:
>>> I would like to debug Tomcat (Version 5.0.x) with its web application
>>> like it is installed and without modifications from WTP.
>>>
>>> In WTP 1.5 it works with Enable Tomcat debug mode fine.
>>>
>>> In WTP 2.0 I do not understand the server settings and the help is
>>> not working (showing a xml phars error cause of not ended <div>).
>>>
>>> org.xml.sax.SAXParseException: The element type "div" must be
>>> terminated by the matching end-tag "</div>" on page "Creating a
>>> Tomcat server".
>>> at
>>> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(D OMParser.java:264)
>>>
>>> at
>>> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl. parse(DocumentBuilderImpl.java:292)
>>>
>>> at
>>> org.eclipse.help.internal.dynamic.DocumentReader.read(Docume ntReader.java:56)
>>>
>>> at
>>> org.eclipse.help.internal.dynamic.XMLProcessor.process(XMLPr ocessor.java:49)
>>>
>>>
>>>
>>> Larry Isaacs schrieb:
>>>> In WTP 2.0, this option is still in the server editor like it is in
>>>> WTP 1.5. However, in WTP 2.0, it has been more correctly labeled
>>>> "Enable Tomcat debug logging". If your Tomcat is version 5.0 or
>>>> later, the label will include "(not supported by this Tomcat
>>>> version)" and the check box will be disabled. Logging in these
>>>> Tomcat versions is controlled by a completely different approach and
>>>> this option has little or no impact on the Tomcat server.
>>>>
>>>> What from of "debugging" were you doing in WTP 1.5 that you aren't
>>>> able to do in WTP 2.0 without this option?
>>>>
>>>> Cheers,
>>>> Larry
>>>>
>>>> user@domain.invalid wrote:
>>>>> Hello,
>>>>>
>>>>> in WST 1.5 I've used Enable Tomcat debug mode in my Tomcat server
>>>>> settings.
>>>>> So I was able to debug my installed tomcat without any changes.
>>>>>
>>>>> How can I do this with WST 2.0?
>>>>>
>>>>> Regards
>>>>>
>>>>> Georg
|
|
|
| Re: WST 2.0: Server for Tomcat: Enable Tomcat debug mode in WST 1.5 [message #197291 is a reply to message #197190] |
Thu, 26 July 2007 07:08 |
| Eclipse User |
|
|
|
Originally posted by: gthuelly.web.de
Thank you for your informations.
I'll read your FAQ and your mails and I am sure to find a way to
configre WST 2.0 to do what I want.
Special thanks for your help
Larry Isaacs schrieb:
> GT wrote:
>> I've tried this flag. I was suprised that it is not neccessary for
>> debugging the web apps in the Tomcat!
>
> Thanks. That clears things up. The "-debug" option in Tomcat 4.0.x and
> 4.1.x was a quick way to enable debug logging in Tomcat's server related
> classes. It Tomcat 5.x and later, logging is configured differently and
> this option has little or no effect.
>
>> I had to disable the flag "Run modules directly from the workspace" in
>> WPT 1.5.
>>
>> How do I configure 2.0 to get the same result?
>
> In WTP 2.0, the "Use Tomcat installation (takes control of Tomcat
> installation)" selection in the Server Locations section is the
> equivalent of unchecking "Run modules directly..." in WTP 1.5. The "Use
> workspace metadata (does not modify Tomcat installation)" is equivalent
> to checking "Run modules directly...".
>
> The WTP 2.0 Tomcat plug-ins don't support moving projects from one
> Tomcat server instance to another. As a result, all projects need to be
> removed from the server and the server published before these selections
> are enabled and changes can be made. Once the desired changes are made,
> re-add the desired projects.
>
> For an explanation of the "(takes control of Tomcat installation)", see:
>
> http://www.eclipse.org/webtools/faq/TomcatServerFAQ.php#gett ing_started_4
>
> I'm still working on updating this FAQ with WTP 2.0 information, but
> this aspect is relevant to WTP 2.0 as well as WTP 1.5.
>
> Cheers,
> Larry
>
>>
>> Thanks
>>
>> Georg
>>
>> Larry Isaacs schrieb:
>>> Just so I'm clear on what you are expecting, if you turn off "Enable
>>> Tomcat debug mode" in WTP 1.5, what "debugging" stops working?
>>>
>>> Cheers,
>>> Larry
>>>
>>> user@domain.invalid wrote:
>>>> I would like to debug Tomcat (Version 5.0.x) with its web
>>>> application like it is installed and without modifications from WTP.
>>>>
>>>> In WTP 1.5 it works with Enable Tomcat debug mode fine.
>>>>
>>>> In WTP 2.0 I do not understand the server settings and the help is
>>>> not working (showing a xml phars error cause of not ended <div>).
>>>>
>>>> org.xml.sax.SAXParseException: The element type "div" must be
>>>> terminated by the matching end-tag "</div>" on page "Creating a
>>>> Tomcat server".
>>>> at
>>>> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(D OMParser.java:264)
>>>>
>>>> at
>>>> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl. parse(DocumentBuilderImpl.java:292)
>>>>
>>>> at
>>>> org.eclipse.help.internal.dynamic.DocumentReader.read(Docume ntReader.java:56)
>>>>
>>>> at
>>>> org.eclipse.help.internal.dynamic.XMLProcessor.process(XMLPr ocessor.java:49)
>>>>
>>>>
>>>>
>>>> Larry Isaacs schrieb:
>>>>> In WTP 2.0, this option is still in the server editor like it is in
>>>>> WTP 1.5. However, in WTP 2.0, it has been more correctly labeled
>>>>> "Enable Tomcat debug logging". If your Tomcat is version 5.0 or
>>>>> later, the label will include "(not supported by this Tomcat
>>>>> version)" and the check box will be disabled. Logging in these
>>>>> Tomcat versions is controlled by a completely different approach
>>>>> and this option has little or no impact on the Tomcat server.
>>>>>
>>>>> What from of "debugging" were you doing in WTP 1.5 that you aren't
>>>>> able to do in WTP 2.0 without this option?
>>>>>
>>>>> Cheers,
>>>>> Larry
>>>>>
>>>>> user@domain.invalid wrote:
>>>>>> Hello,
>>>>>>
>>>>>> in WST 1.5 I've used Enable Tomcat debug mode in my Tomcat server
>>>>>> settings.
>>>>>> So I was able to debug my installed tomcat without any changes.
>>>>>>
>>>>>> How can I do this with WST 2.0?
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Georg
|
|
|
Goto Forum:
Current Time: Fri Apr 19 08:01:00 GMT 2024
Powered by FUDForum. Page generated in 0.02372 seconds |
] 
Search
Help
Register
Login
Home
