Hello Daniel, I tried it out. What would be nice is that once you double click on an item, it should open corresponding file on the right.
Regards, Kiran Gawde Senior Software Architect Object Edge Inc (925) 943 5558 x108 "There are two kind of people: Those who do the work and those who take the credit. Try to be in the first group because there is less competition there." "Never give up on what you really want to do. The person with big dreams is more powerful than one with all the facts". From: Daniel McAllister <[email protected]> To: [email protected] Date: 10/05/2011 09:46 AM Subject: Ofbiz explorer plugin Hello, I want to give you an update on my ongoing project the Ofbiz Eclipse Explorer. The code is not "production ready" yet. That means there are still features that are not turned on, or not fully implemented. The project site is here: https://github.com/rasztasd/ofbiz-eclipse-project-explorer I would recommend you to checkout the code. Import the org.ofbiz.plugin project in eclipse as a Java project (You can use Git plugin too). Open plugin.xml with the Plug-in manifest editor (default) and on the top right corner press Export "Deployable plugins and fragments". By default you only need a stock 3.6 Java Eclipse. After you installing the plugin, you can turn on the Ofbiz explorer view, by clicking: Window->Show view->Other->Ofbiz explorer Current feature sets. A view that shows a Tree of Ofbiz artifacts. -Projects -Directories (hotdeploy subdirectories, framework, application, etc) -Components -Webapps -Services -Entites -Controller.xml entries There is a filter on top of the Tree where you can search for: -service names -uri's like /admin/control/doSomething (note that the "control" is hard-coded and not calculated from web.xml) -entites There are popup menus associated to these Tree item's. Service, Controller.xml entries and Entites has go to definition in the Xml file (shows up the editor and selects the corresponding line number) Java service has a go to Java implementation. If you click on Analyze all in the View then every Java Services are parsed (by static code parsing). It will mark lines in the Java editor with errors where you use a Service input or output parameter that you didn't define in the service's Xml definition. The implementation is very basic, it will only find those places where you use a string literal for the Map's key.
