[henk]

In order to provide a more ‘intergrated’ feeling when working with web apps, wouldn’t it be an idea to use Eclipse’s intergrated web browser in a run/debug configuration in order to run and debug web applications?

Instead of starting the server, loading the browser, pointing in to the correct (local) address, it would be much nicer to just select run or debug, and have the web application appear in a new window ( as the eclipse help system does ).

Closing this window would also automatically stop the server. Unless I’m totally missing something. it seems to me that all this should not be terribly hard to implement. Of course, the old setup should still be supported, but such a ‘quick run’ feature would be really handy.

When using this intergrated browser, it would also be possible to provide a button in its interface to jump directly back to the source-code of the displayed page. I think this is an often occuring patern when you’re debugging a web application; you browse through the pages, spot an error, and would like to go right to the source code of it. When running the web app through the intergrated browser you know where the page comes from, and thus can let the developper jump back to it quite easily.

Also, it might be nice to couple http request debugging with this. I.e. allow the developper to set a special break-point at a post or get request. When that break-point is hit, you could show the request headers.

[Riyad Kalla]

henk, great overall suggests. Here are a few things:

1) You can open the MyEclipse Web Browser via Window > Open View > Other… > MyEclipse > Web browser
2) You can use the HTTP monitor now included to view the state of requests

I like your quick run and jump-to ideas though, thanks!

[Author]

Posts