Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Building a non-file based Eclipse plug-in

 
Jeff Pierce
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't want to be required to have a project that maps to a directory on the file system. The resources that I want to navigate/edit/manage don't exist on the file system either, they exist in my "app server". An example of this type of application could be a web site browser where you point your Eclipse project at a URL and what appears is a navigator view of the web site, a simple properties page, and an HTML editor. Another example might be if you have a J2EE application and your model is a bunch of EJBs you want access to from Eclipse.

Is this possible? If so, where is a good place to start? What objects within Eclipse should I be focusing on?

Thanks.
 
Morten Moeller
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Actually, Eclipse isn't built very well to handle this. Most of the resource framework, the resource navigator etc is tightly coupled to a file based system.

You can still create views and editors of course that isn't file based. You just have to create your own IEditorInput etc. But it is hard/impossible to leverage existing plug-ins in your systems.

But, if you want better non-file support, go vote for:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=37723
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic