[wtp-dev] WTP Project Explorer migrated to Eclipse Common Navigator Fram

[John Lanuti <jlanuti@xxxxxxxxxx>]

Extended Team,

First, let me remind you that the Eclipse
Common Navigator framework remains a work in progress and with that said,
the resulting explorer in WTP based on the eclipse framework is also a
work in progress.  On the whole, the functionality of WTP 1.0.1 has
basically been restored so I am at a good point to release to an integration
build to start allowing adopters to react.  The changes for extenders
should not be as drastic as they might be fearing and there is a logical
replacement for everything.  The eclipse framework extension point
schema documentation is really quite full and up to date so my advice is
to go there, read it, become familiar with it, and use it as a reference.
 There are some key things to note about the migration process:

There is a new plugin which defines
the WTP extension to the eclipse common navigator: org.eclipse.wst.common.explorer.
 This is done so that JST is not required.

Essentially, the new framework paradigm
can be summed as you bind navigator contents to navigator viewers.  So
you can add any existing content extensions to your viewer by just adding
a binding to the content extensions id.

You will need to remove dependencies
to the 3 old navigator plugins:
org.eclipse.jst.common.navigator.java
org.eclipse.wst.common.navigator.views
org.eclipse.wst.common.navigator.workbench

These plugins will be deprecated and
removed in WTP 1.5 M6.  The new plugins are:
org.eclipse.ui.navigator
org.eclipse.ui.navigator.resources
 and  hopefully also one from
JDT, (the java content extension has not been implement yet!)

The extension point org.eclipse.wst.common.navigator.workbench.commonWizard
is replaced by commonWizard under org.eclipse.ui.navigator.navigatorContent


The WTP viewer ID =  org.eclipse.wst.navigator.ui.WTPWorkingSetCommonNavigator
was replaced by org.eclipse.wst.common.explorer.CommonProjectExplorer 

Enablement expressions converted to
org.eclipse.core.expressions.   "objectClass name=" goes
to "instanceof value="  especially in common wizard extensions.
 For example:
<test
property="org.eclipse.core.resources.projectNature"
    value="org.eclipse.wst.common.modulecore.ModuleCoreNature"/>

You can also test facet
enablement by using
<instanceof
value="org.eclipse.core.resources.IProject"/>
         
         <test
property="org.eclipse.wst.common.project.facet.core.projectFacet"
           
               
     value="jst.ejb"/>

You must switch your dynamic adapter
factories to reference this new viewer ID to display content properly:
org.eclipse.wst.common.explorer.CommonProjectExplorer.

The j2ee project creation/import/export
wizard ids were changed to be the name of the wizard class for consistency
as API.

Once again, the java content is also
not ready from base eclipse JDT.  For now, make use of the java perspective
in tandem.

Also, you will notice we have gotten
rid of the groupings.  This is a preliminary decision as many users
did not find them useful.  We may add back an option later when we
have the working set support from eclipse.

This is targetted for the WTP 1.5 I
build for Thursday February 16th.  Please plan accordingly.  If
you have any questions, caveats, and concerns, feel free to contact me.
 

Thanks,

John Lanuti
Software Engineer, IBM Rational
jlanuti@xxxxxxxxxx
t/l 441-7861

"I know this lady way down in my country.
She is so pretty that my eyes throw disguises at me.
Now we will sit and we'll wonder about our future,
But now I'm thinking that today sounds fine to me."  - Of A Revolution