This week's book giveaway is in the Jobs Discussion forum.
We're giving away four copies of Java Interview Guide and have Anthony DePalma on-line!
See this thread for details.
The moose likes IDEs, Version Control and other tools and the fly likes Building a non-file based Eclipse plug-in Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "Building a non-file based Eclipse plug-in" Watch "Building a non-file based Eclipse plug-in" New topic

Building a non-file based Eclipse plug-in

Jeff Pierce

Joined: Jan 04, 2002
Posts: 13
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?

Morten Moeller
Ranch Hand

Joined: Nov 26, 2001
Posts: 30
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:
I agree. Here's the link:
subject: Building a non-file based Eclipse plug-in
It's not a secret anymore!