- This topic has 68 replies, 43 voices, and was last updated 15 years, 1 month ago by
.
-
Posts
-
It would just be enough to have the Application start mechanism moved from its own button to the Run/Debug system. Then it would be easy to see the invocation and copy it to a Profiler entry. Right now I am stuck with the Eclipse Profiler and no idea about how to invoke Tomcat manually.
Given that almost everybody wants a profiler integration – I think the next question to ask is which one to integrate with. Maybe a poll on this would be useful?
Regards,
YeeI’m not aware of many choices, just 1 or 2 of the original profiler pluigins to come out that I’m not aware of either being under active development, and then Hyades.
So Hyades is the choice then? That is is actually good news to me. I am not using profile yet, and it means I won’t have to crack my head deciding which one to choose from.
Thanks
YeeWith the Eclipse top project ” Test & Performance Tools Platform (TPTP)” (http://www.eclipse.org/tptp/index.html) I don’t see a need for MyEclipseIDE to incorporate this (I rather see other features).
J
Yea but by that reasoning why should MyEclipse have bothered to do anything that the WTP provides for….?
The fact is that MyEclipse not only agregates these projects but *improves* on them…
I think it would be *extremely* useful to bundle TPTP with my eclipse to provide the following benefits
1. Ensure compatiblity of shared libraries (EMF etc.)
2. Integration with server startupTPTP is a good profiler, but is very fiddly to start up. You have to run the rac agent as a seperate process, then include -XrunpiAgent in the startup of your app server, and make sure the piAgent.dll is your path.
I can never seem to make this work through the my eclipse app server preferences, and end up running tomcat outside of eclipse.
It would be very nice if myeclipse bundled all this so all you had to do was click on “Profile Server” instead of “Start Server”. Alternatively, make it an extra option in the app server prefs additional to debug mode etc.
Cheers,
Jon
@daorriss wrote:
Yea but by that reasoning why should MyEclipse have bothered to do anything that the WTP provides for….?
The fact is that MyEclipse not only agregates these projects but *improves* on them…
I hear what you’re saying, but I don’t agree in all cases. I don’t want MyEclipse to handle everything for a numerous of reasons.
Don’t want it to be this huge thing that comes with five, six features that I really use and dozens of feature that I don’t use.
Especially not when I can’t inactivate features in a easy way.I thought MyEclipse would focus on J2EE and do it all the way. New features are added all the time, but I still really don’t use more than the syntax highlighted editor. Number one enhancement I would like to see is a flexible way of definied your MyEclipse project (I haven’t looked lately, but I believe that the exploded war file still rules).
Totally agree, TPTP is going to be integrated in Eclipse 3.2 so I would like myeclipse to concentrate on more important stuff. By the way, Myeclipse is way older then wtp so it is why they have implemented all the J2EE features.
you guys who think a profiler should not be included are right .. however:
i think it would be a good idea to include integration at the application server launch configuration level. myeclipse should not include a profiler, but choose one (tptp) and support integration if it is present in the ide already.
i can’t wait for TPTP to be integrated, as the installation is rediculously complicated and i couldn’t get it to work. i’ve started using jprofiler and it’s not bad but not as good as what the screenshots for TPTP look. the installation however is a sinch.
We’ve now setup TPTP to be used in myEclipse 4.1.1GA and Tomcat 5.0.
As a help for all who where unable to get TPTP running, we compiled a Step-By-Step Guide to set TPTP up for myEclipse/Tomcat usage.See http://www.symentis.com/w-howTo/Eclipse-TPTP-Tomcat-HowTo.pdf
Any comments are appreciated.
Robert
