Re: Tomcat Netbeans Project... WildCat
On 5/30/07, Johnny Kewl <[EMAIL PROTECTED]> wrote: Yes I did see this... problem I had was trying to figure out how the code goes into packages. That ant script pulls stuff out of jars, compiles little bits all over the place, and assembles other jars. I'm sure all with good reason, but it makes it a mission to match code and jar. Now that the Tomcat jars are in the central Maven repo, a nice enhancement request would be to ask the developers to provide matching -sources and -javadoc jars. *ducking and running from Filip* -- Wendy - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Netbeans Project... WildCat
- Original Message - From: "Mark Thomas" <[EMAIL PROTECTED]> To: "Tomcat Users List" Sent: Tuesday, May 29, 2007 7:31 AM Subject: Re: Tomcat Netbeans Project... WildCat Johnny Kewl wrote: + One can dump the src into a Netbeans project, click compile and you have a working Tomcat. Great. But you have no guarantee it will behave the same way as Tomcat built with the standard build script. It should be the same but be prepared for some odd, unexpected errors - probably around classloader issues. This is true but it makes it so easy to watch Tomcat working and play with it... its worth the risk I think... after all its just for experimentation and who knows if the users find it easy, worthy contributions to tomcat must follow... like this for example, I think the way bootstrap classloads in 6.0.X is overly complex and now redundant. See what happens when a user starts playing with the code, cool hey. + That means one can run it in debug, and watch it working from the inside. You can do this with the standard build. Both Eclispe and NetBeans support this. see http://tomcat.apache.org/faq/development.html Providing you configure the appropriate source files you can debug any combination of Tomcat, you app or any library used by Tomcat or your app. Yes I did see this... problem I had was trying to figure out how the code goes into packages. That ant script pulls stuff out of jars, compiles little bits all over the place, and assembles other jars. I'm sure all with good reason, but it makes it a mission to match code and jar. If left to their own devices a user will probably do what I did... jam all the code in and make their own packages. But its a good idea, be nice if you added an ant script that creates the source and libs needed for each netbeans project, so that it matches Tomcat exactly... call it Dev-Cat... Clinicly... I agree with you... but I luv playing with WildCat Its up... can get it at http://coolese.100free.com/wildcat.htm - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Netbeans Project... WildCat
> -Original Message- > From: Mark Thomas [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 29, 2007 1:31 AM > To: Tomcat Users List > Subject: Re: Tomcat Netbeans Project... WildCat > > Johnny Kewl wrote: > > + One can dump the src into a Netbeans project, click compile and you > have a working Tomcat. > Great. But you have no guarantee it will behave the same way as Tomcat > built with the standard build script. It should be the same but be > prepared for some odd, unexpected errors - probably around classloader > issues. > > > + That means one can run it in debug, and watch it working from the > inside. > You can do this with the standard build. Both Eclispe and NetBeans > support this. see http://tomcat.apache.org/faq/development.html > Providing you configure the appropriate source files you can debug any > combination of Tomcat, you app or any library used by Tomcat or your app. I do this every day. You want a remote application / attach launch configuration for Eclipse. Be sure to start the Tomcat JVM with the -Xdebug... parameters. Tim > > > I havent had a chance to test it yet, but where I'm trying to get to is > the ability to debug from servlet straight into Tomcat source. > This should be standard out of the box functionality. You shouldn't > need any extras to get this working. You don't with Eclipse as your > dev environment and I see no reason for Netbeans to be any different. > > Mark > > - > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Netbeans Project... WildCat
On 5/29/07, Mark Thomas <[EMAIL PROTECTED]> wrote: Johnny Kewl wrote: > I havent had a chance to test it yet, but where I'm trying to get to is the ability to debug from servlet straight into Tomcat source. This should be standard out of the box functionality. You shouldn't need any extras to get this working. You don't with Eclipse as your dev environment and I see no reason for Netbeans to be any different. It's not quite out-of-the-box IME, but quite easy to debug into Tomcat code using Eclipse + Web Standard Tools. You have to point Eclipse at the source code whenever prompted (just browse to apache-tomcat-?.?.?-src.zip). Also, you may find that Eclipse doesn't know about all the Tomcat JARs that you run into. I created a library for these JARs in my Eclipse project, and add them as required. Note that I'm not talking about compiling Tomcat from source, just debugging my own apps with an existing Tomcat release. And understanding what's going on once you're inside Tomcat is something else entirely. :-) -- Len - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Netbeans Project... WildCat
Johnny Kewl wrote: > + One can dump the src into a Netbeans project, click compile and you have a > working Tomcat. Great. But you have no guarantee it will behave the same way as Tomcat built with the standard build script. It should be the same but be prepared for some odd, unexpected errors - probably around classloader issues. > + That means one can run it in debug, and watch it working from the inside. You can do this with the standard build. Both Eclispe and NetBeans support this. see http://tomcat.apache.org/faq/development.html Providing you configure the appropriate source files you can debug any combination of Tomcat, you app or any library used by Tomcat or your app. > I havent had a chance to test it yet, but where I'm trying to get to is the > ability to debug from servlet straight into Tomcat source. This should be standard out of the box functionality. You shouldn't need any extras to get this working. You don't with Eclipse as your dev environment and I see no reason for Netbeans to be any different. Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Netbeans Project... WildCat
Sounds great Sadly I don't have the linux experience you need to help. On 5/26/07, Johnny Kewl <[EMAIL PROTECTED]> wrote: Everyone probably knows by now that I think Tomcat is pure magic. I been trying to find a way to bridge the gap between the super keen user and the developer. One can become and expert user, and still find those guru's in the dev list intimidating. It probably isnt as big a deal for the linux user... linux itself is a development tool, but to the windows user, getting from expert user to someone that can find their way around the code is not so easy. So what I've been up to is converting (as little as possible) Tomcat to a pure Netbeans project. I call it Wild Cat... because it should never be confused with the professional Tomcat. Its turning out to be a magic play zone and an excellent way to get to know the code. This is where I'm at + One can dump the src into a Netbeans project, click compile and you have a working Tomcat. + That means one can run it in debug, and watch it working from the inside. + Its tomcat 6.0.13... but is wears a Tomcat 5.5 mask... the reason I did that is so that to netbeans (remember netbeans is a servlet dev environment)... is so that if you tell Netbeans that the DIST folder or BUILD folder of WildCat is a Tomcat 5.5 server... it thinks it is, and Tomcat (Wildcat) works just the same from inside netbeans, and from the servlet dev env. + So... you can run your servlets against the Tomcat source... now that is cool. I havent had a chance to test it yet, but where I'm trying to get to is the ability to debug from servlet straight into Tomcat source. + Can also start and stop it from the Bin scripts... and one can also just double click on WildCat, and you get a GUI... and you can control it from their... the GUI also has a teminal window so you can watch the Tomcat messages. + Its not meant to be a slick package like tomcat... its a huge jar with 2 libs... but its a magic way to watch Tomcat working. Thats as far as I've got... but I need a little help before sticking the source on a site for everyone to play with. I develop on windows... and I'm looking for a linux person that is super keen on Tomcat and also runs Netbeans. Someone that wants to play with Tomcats source and that will pick up linux problems... like scripts and I may have used a \ somewhere in the code. Thanks... I'll stick it on a site as soon as I got it all tested. Johnny Kewl eMail: Johnkewlstuff.co.za -- replace with @ -- Cell: +027-72- 473-9331 Java Developer (Tomcat Aficionado) Free Tomcat software at http://coolese.100free.com/
Tomcat Netbeans Project... WildCat
Everyone probably knows by now that I think Tomcat is pure magic. I been trying to find a way to bridge the gap between the super keen user and the developer. One can become and expert user, and still find those guru's in the dev list intimidating. It probably isnt as big a deal for the linux user... linux itself is a development tool, but to the windows user, getting from expert user to someone that can find their way around the code is not so easy. So what I've been up to is converting (as little as possible) Tomcat to a pure Netbeans project. I call it Wild Cat... because it should never be confused with the professional Tomcat. Its turning out to be a magic play zone and an excellent way to get to know the code. This is where I'm at + One can dump the src into a Netbeans project, click compile and you have a working Tomcat. + That means one can run it in debug, and watch it working from the inside. + Its tomcat 6.0.13... but is wears a Tomcat 5.5 mask... the reason I did that is so that to netbeans (remember netbeans is a servlet dev environment)... is so that if you tell Netbeans that the DIST folder or BUILD folder of WildCat is a Tomcat 5.5 server... it thinks it is, and Tomcat (Wildcat) works just the same from inside netbeans, and from the servlet dev env. + So... you can run your servlets against the Tomcat source... now that is cool. I havent had a chance to test it yet, but where I'm trying to get to is the ability to debug from servlet straight into Tomcat source. + Can also start and stop it from the Bin scripts... and one can also just double click on WildCat, and you get a GUI... and you can control it from their... the GUI also has a teminal window so you can watch the Tomcat messages. + Its not meant to be a slick package like tomcat... its a huge jar with 2 libs... but its a magic way to watch Tomcat working. Thats as far as I've got... but I need a little help before sticking the source on a site for everyone to play with. I develop on windows... and I'm looking for a linux person that is super keen on Tomcat and also runs Netbeans. Someone that wants to play with Tomcats source and that will pick up linux problems... like scripts and I may have used a \ somewhere in the code. Thanks... I'll stick it on a site as soon as I got it all tested. Johnny Kewl eMail: Johnkewlstuff.co.za -- replace with @ -- Cell: +027-72- 473-9331 Java Developer (Tomcat Aficionado) Free Tomcat software at http://coolese.100free.com/
