You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by yo...@apache.org on 2005/03/23 16:52:38 UTC
cvs commit: jakarta-tomcat-site/xdocs-faq development.xml
yoavs 2005/03/23 07:52:38
Modified: docs/faq development.html
docs/faq/printer development.html
xdocs-faq development.xml
Log:
Bugzilla 33767.
Revision Changes Path
1.4 +9 -9 jakarta-tomcat-site/docs/faq/development.html
Index: development.html
===================================================================
RCS file: /home/cvs/jakarta-tomcat-site/docs/faq/development.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- development.html 22 Feb 2005 17:27:41 -0000 1.3
+++ development.html 23 Mar 2005 15:52:38 -0000 1.4
@@ -89,17 +89,17 @@
<div style="padding-left : 20px;">
<p>
This answer assumes that you have correctly set up a NetBeans IDE project and
-that you know how to use its debugger. If not, please go to
+that you know how to use the NetBeans IDE debugger. If not, please go to
<a href="http://www.netbeans.org/kb/using-netbeans/40/debug.html">
http://www.netbeans.org/kb/using-netbeans/40/debug.html</a>
and read up on how to use NetBeans IDE and its debugger.
</p>
<p>
-Make sure that Tomcat is started, that your application is deployed, and that
-the sources are all defined as resources in your application. If you have a
-servlet or JSP file, set a breakpoint where its sure to hit on the next request.
-Go to "Run->Attach Debugger". A dialog pops up to let you specify the following
-options:
+Make sure that Tomcat is started in debug mode as described above, that your
+application is deployed, and that the sources are all defined as resources in
+your application. If you have a servlet or JSP file, set a breakpoint where you
+think a problem might be occurring. Go to "Run->Attach Debugger". A dialog pops
+up to let you specify the following options:
<ul>
<li> Debugger: JPDA Debugger </li>
<li> Connector: SocketAttach </li>
@@ -114,9 +114,9 @@
</p>
<p>
Note that NetBeans IDE has a second option -- you can debug JSP files and
-servlets locally using a Tomcat server that is bundled with the IDE. The bundled
-Tomcat server can be started in debug mode (its default port number is 11555)
-and you can open a remote connection to it from NetBeans IDE as described above.
+servlets locally using a Tomcat server that is bundled with the IDE. When you
+debug a JSP file or servlet in the IDE, the bundled Tomcat server automatically starts
+in debug mode, and the debugger connects to it.
</p>
</div><br>
</p>
1.4 +9 -9 jakarta-tomcat-site/docs/faq/printer/development.html
Index: development.html
===================================================================
RCS file: /home/cvs/jakarta-tomcat-site/docs/faq/printer/development.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- development.html 22 Feb 2005 17:27:41 -0000 1.3
+++ development.html 23 Mar 2005 15:52:38 -0000 1.4
@@ -88,17 +88,17 @@
<div style="padding-left : 20px;">
<p>
This answer assumes that you have correctly set up a NetBeans IDE project and
-that you know how to use its debugger. If not, please go to
+that you know how to use the NetBeans IDE debugger. If not, please go to
<a href="http://www.netbeans.org/kb/using-netbeans/40/debug.html">
http://www.netbeans.org/kb/using-netbeans/40/debug.html</a>
and read up on how to use NetBeans IDE and its debugger.
</p>
<p>
-Make sure that Tomcat is started, that your application is deployed, and that
-the sources are all defined as resources in your application. If you have a
-servlet or JSP file, set a breakpoint where its sure to hit on the next request.
-Go to "Run->Attach Debugger". A dialog pops up to let you specify the following
-options:
+Make sure that Tomcat is started in debug mode as described above, that your
+application is deployed, and that the sources are all defined as resources in
+your application. If you have a servlet or JSP file, set a breakpoint where you
+think a problem might be occurring. Go to "Run->Attach Debugger". A dialog pops
+up to let you specify the following options:
<ul>
<li> Debugger: JPDA Debugger </li>
<li> Connector: SocketAttach </li>
@@ -113,9 +113,9 @@
</p>
<p>
Note that NetBeans IDE has a second option -- you can debug JSP files and
-servlets locally using a Tomcat server that is bundled with the IDE. The bundled
-Tomcat server can be started in debug mode (its default port number is 11555)
-and you can open a remote connection to it from NetBeans IDE as described above.
+servlets locally using a Tomcat server that is bundled with the IDE. When you
+debug a JSP file or servlet in the IDE, the bundled Tomcat server automatically starts
+in debug mode, and the debugger connects to it.
</p>
</div><br>
</p>
1.4 +9 -9 jakarta-tomcat-site/xdocs-faq/development.xml
Index: development.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-site/xdocs-faq/development.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- development.xml 22 Feb 2005 17:27:41 -0000 1.3
+++ development.xml 23 Mar 2005 15:52:38 -0000 1.4
@@ -100,17 +100,17 @@
<answer>
<p>
This answer assumes that you have correctly set up a NetBeans IDE project and
-that you know how to use its debugger. If not, please go to
+that you know how to use the NetBeans IDE debugger. If not, please go to
<a href="http://www.netbeans.org/kb/using-netbeans/40/debug.html">
http://www.netbeans.org/kb/using-netbeans/40/debug.html</a>
and read up on how to use NetBeans IDE and its debugger.
</p>
<p>
-Make sure that Tomcat is started, that your application is deployed, and that
-the sources are all defined as resources in your application. If you have a
-servlet or JSP file, set a breakpoint where its sure to hit on the next request.
-Go to "Run->Attach Debugger". A dialog pops up to let you specify the following
-options:
+Make sure that Tomcat is started in debug mode as described above, that your
+application is deployed, and that the sources are all defined as resources in
+your application. If you have a servlet or JSP file, set a breakpoint where you
+think a problem might be occurring. Go to "Run->Attach Debugger". A dialog pops
+up to let you specify the following options:
<ul>
<li> Debugger: JPDA Debugger </li>
<li> Connector: SocketAttach </li>
@@ -125,9 +125,9 @@
</p>
<p>
Note that NetBeans IDE has a second option -- you can debug JSP files and
-servlets locally using a Tomcat server that is bundled with the IDE. The bundled
-Tomcat server can be started in debug mode (its default port number is 11555)
-and you can open a remote connection to it from NetBeans IDE as described above.
+servlets locally using a Tomcat server that is bundled with the IDE. When you
+debug a JSP file or servlet in the IDE, the bundled Tomcat server automatically starts
+in debug mode, and the debugger connects to it.
</p>
</answer>
</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org