facebook

Remote debugging with Resin [Closed]

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #201052 Reply

    gilesp
    Member

    Hi there

    Hope this hasn’t been asked before. (doesn’t seem to be anywhere obvious)… ohh and great product too ! I’m trying to sort out remote debugging with resin-2.1.4. I’ve looked on the resin webite and can’t see any thing straight forward. I presume one can just pass the jvm that starts resin the usual cebug parameter? (are these parameters specific to each container?)

    I’ve also seen that resin is started with an httpd.exe… is there an explicit way to start resin and pass it command line parameters ?

    Is there a way to configure this in myeclipse?

    Has anyone does this before…. must have !

    Gheers
    Giles

    #201059

    Riyad Kalla
    Member

    Windows->Preferences->MyEclipse->Application Servers(name?)->Resin->Launch (or JDK, I froget the node name)->Run in debug mode

    Does this not run Resin in debug mode for you?

    #201068

    Scott Anderson
    Participant

    Giles,

    As Riyad pointed out, there’s nothing much to do. Just navigate to the Resin2 preference configuration page, enable it, fill in the requested parameters, and configure the JDK on the JDK page. Then you can launch it off the MyEclipse server toolbar button as shown in the webapp tutorial in the user guide. By the way, the FAQ has some notes on configuring Resin 2 here: http://www.myeclipseide.com/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=25&categories=Resin2&parent_id=14

    –Scott
    MyEclipse Support

    #201178

    gilesp
    Member

    Hey Scott and rkalla

    Short answer : move back a version of myeclipse, create a new myeclipse project : sorted.

    Long answer ….

    Thanks for the reply. This is wot happened:

    On running resin from within myeclipse – things are fine. The Server starts up and i can set break points. It even stops on a break point set in the resin code. (??) However as soon as i try and hit a break point in my own code i get a java error (pop up) saying the compiled code doesn’t have any line numbers – which are required for debugging. I took it that this was an issue with the compiler compiling my code.

    I tryed passing the -g argument to the resin container (explicitly generate code with debugging line options)… but this was not the place to put it. It’s my code and not resin that needs line numbers. I couldn’t find anywhere in eclipse or myeclipse that allows you to pass command line parameters to the jdk compiling your source code.

    I thought it may be an installation issue, as i’ve just put EnterpriseWorkbenchInstaller_020700RC1 on. My source code was initially just a normal eclipse project. (ie: not generated or initiated with myeclipse. To try and get the debugging working, i tryed to create a new myEclipse project. While pointing myeclipse to my relevant source folders and webContext i get the following error as it trys to compile my code: “Null pointer exception while runningcom.genuitec.eclipse.j2eedt.core.builder.DeploymentDescriptorValidator” ….

    Then some really weird stuff starts to happen. Certain folders in my project can’t be seen (although they are still in my file system), and on trying to do more and more tasks (compile, run my own ant tasks) i get the above error more and more…. heavy stuff !

    So… to cut it short… i put back my previous version of myeclipse on (EnterpriseWorkbenchInstaller_020604) … re-created a myEclipse project with my original source…. and bobs your aunty… everything works… syn-on-demand and debugging.

    Does the latest version of myeclipse has problems? Is it just me, could it be my enviroment?.. and i just dumb ?

    Any Ideas… thanks ?

    #201183

    Scott Anderson
    Participant

    Giles,

    Thanks for the explaination of what you’re experiencing.

    “Null pointer exception while runningcom.genuitec.eclipse.j2eedt.core.builder.DeploymentDescriptorValidator” ….

    This is a known bug in RC1 as documented in this post:
    https://www.genuitec.com/forums/topic/rebuild-project-deployment-descriptor-npe-closed/

    We’ve fixed the issue internally and it will be available in RC2 next week. The current workaround is to turn off XML validation. This should stop the exception from occuring and get you going again. However, since you’ve already gone back to 2.6.4, I’d personally hang tight until the next release. Sorry for the inconvenience.

    –Scott
    MyEclipse Support

    #201229

    gilesp
    Member

    Hi Scott

    Thanks for the reply. I’ll hang tight till the next version then….

    Ohh… and the thing about my jars dissapearing…. uhmm… well – i forgot i had set my ide to hide jars from my package structure….

    Wot an idiot ! 😳

Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: Remote debugging with Resin [Closed]

You must be logged in to post in the forum log in