views:

372

answers:

1

I am trying to set up a development environment to test Spring Portlet MVC for development of JSR 168 conforming portlets. I have the latest STS installed, which included Spring 2.5 and Eclipse (Catalina). This has been my environment to develop with Spring MVC, and that works fine using Apache as a local server for debugging.

I found some instructions on the Pluto portal site on using Pluto as a remote debugging host for portlets. I have implemented those instructions. I am sending Eclipse into debug mode by right clicking on one of the JSPs and going into "debug as". My problem is that when I log into Pluto, it is not sending me into debug mode. I am seeing the default Pluto page as opposed to my portlet. My portlet has not been installed onto Pluto, and the instructions do not seem to require the portlet to be installed.

To help, I have a screen shot at http://www.ceruleaninc.ca/pluto%5Fproblem.jpg, showing the following:

  • Eclipse showing the remote debugging to localhost:8000
  • Tomcat showing the "Listening for transport dt_socket at address: 8000
  • The Catalina.bat jpda start command
  • The Pluto Portal screen after log in

Thanks much! I would welcome any advice on approaches to debugging portlets. I am not tied to pluto. There does seem to be a lack of detailed instructions on this topic.

A: 
Rich Seller
Yes, thank you. If you could take a look at my description of what I did, I had already right clicked on "Remote Java Application", and had done exactly your recommendation. If you could check the screen shot that I provided in my post, it shows that Eclipse has connected to the remote testing host successfully. Unfortunately I still seem to be missing something... Any further advice would be much appreciated.
mikep