Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Goal: Show EMF Resource contents as subtree in Workbench Navigator.

Hi Mark,

The Common Navigator actually has no knowledge of the content providers for the specific models, but the J2EE nodes use a factory class named "DynamicAdapterFactory" that collects registered content providers for each EMF package.

For instance in the jst.j2ee plugin.xml the following extension point is implemented:


This is a common mechanism for registering content providers for different EMF packages.  Currently much of this mechanism is internal , and doesn't have formal documents explaining these ext points.

Hope this gets you further.   Maybe I can help more if you provide a specific usecase or requirement?

Thanks - Chuck

Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Email:  cbridgha@xxxxxxxxxx
Phone: 919-254-1848 (T/L: 444)

Mark Diggory <mdiggory@xxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

04/12/2005 11:48 AM

Please respond to
mdiggory and "General discussion of project-wide or architectural issues."

"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
Re: [wtp-dev] Goal: Show EMF Resource contents as subtree in        Workbench        Navigator.


From what I see, it is more a part of the J2EE Navigator. But has hooks
into CommonNavigator somehow.

After some digging, here is what I think is a strong example of its
usage in the J2EE navigator*checkout*/jst/components/j2ee/plugins/org.eclipse.jst.j2ee.navigator.ui/plugin.xml?rev=HEAD&cvsroot=WebTools_Project&content-type=text/xml*checkout*/jst/components/j2ee/plugins/org.eclipse.jst.j2ee.webservice.ui/plugin.xml?rev=HEAD&cvsroot=WebTools_Project&content-type=text/xml

From what I understand the Common Navigator has some default handlers
for EMF.

Is there anyone you can recommend I talk with about this design and how
to approach using it?

Thanks again ,
-Mark Diggory

Saurabh Agarwal wrote:

> Hi,
> You can use to enable on EObject instead of using emfEnablement. The
> common workbench navigator does not know about the EMF
> and hence the emfEnablement is not part of the Common Navigator. What
> u could do is enable on eobject in the <enablement> section
> <objectClass
>                 name="org.eclipse.emf.ecore.EObject">
> </objectClass>
> thanks
> Saurabh Agarwal
> Staff Engineer
> Rational Software, IBM Software Group
> 4205 S. Miami Blvd
> Durham NC 27703
> Tel: 919  254 7089
> Email: agarwasa@xxxxxxxxxx
wtp-dev mailing list

Back to the top