Just like you would hunt down a problem in G or any other project.
Use the debugger. Eclipse/WTP provides sdk distributions so all the
source is available. You can put breakpoints in the geronimo code to
see the method call hierarchy in the debug view in Eclipse to get an
understanding of who calls what.
Another common practice is to verify problems against other server
adapters. This would be a good indication that the bug is in WTP and
not the implementation of a given adapter. Then you can use the
debugger to evaluate further.
- sachin
On Feb 27, 2006, at 10:33 PM, Lin Sun wrote:
Hi Sachin,
Thanks this information is very useful. I am relatively new to the
plugin
development... Could you shed some light on how to tell if a defect
is in
WTP or Geronimo devtools?
Thanks,
Lin
-----Original Message-----
From: Sachin Patel [mailto:[EMAIL PROTECTED]
Sent: Monday, February 27, 2006 11:24 AM
To: [email protected]; [email protected]
Subject: WTP/Eclipse questions/defects
With the release of the Eclipse plugin, here are a list of helpful
resources where WTP/Eclipse specific questions can be asked and where
you'll be able to search for answers to many common questions.
http://www.eclipse.org/newsgroups/index_project.php
The newsgroup URL is news.eclipse.org and the WTP specific list is
eclipse.webtools.
The bug reporting tool for all Eclipse projects is https://
bugs.eclipse.org/bugs/
If you feel you find a defect in WTP that you feel affects the
functionality of the Geronimo plugin, for tracking purposes open a
Jira in Geronimo and link it to the bugzilla number. This way the
project is aware and thus can ensure that the defect gets added to
the WTP adopter list and can take a higher priority.
Thanks.
- sachin
