Bug 268140 - ext point org.eclipse.wst.common.modulecore.componentimpl
Summary: ext point org.eclipse.wst.common.modulecore.componentimpl
Status: NEW
Alias: None
Product: WTP Common Tools
Classification: WebTools
Component: wst.common (show other bugs)
Version: 3.0.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Chuck Bridgham CLA
QA Contact: Konstantin Komissarchik CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2009-03-11 11:48 EDT by Dimo Stoilov CLA
Modified: 2009-10-07 09:13 EDT (History)
3 users (show)

See Also:

Attachments
our case discribed in this mail (posted on the WTP mailing list) (24.00 KB, application/octet-stream)
2009-03-11 11:48 EDT, Dimo Stoilov CLA 		no flags Details
our case (text format) (2.26 KB, text/plain)
2009-03-11 11:50 EDT, Dimo Stoilov CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dimo Stoilov CLA 2009-03-11 11:48:08 EDT 
Created attachment 128384 [details]
our case discribed in this mail (posted on the WTP mailing list)

How can we use org.eclipse.wst.common.modulecore.componentimpl ext.p to provide virtual component implementation. It seems only one client can extend this ext.p. (no priority option defined) and it is already extended by org.eclipse.jst.j2ee.

Our case is described in the attached mail
Comment 1 Dimo Stoilov CLA 2009-03-11 11:50:50 EDT 
Created attachment 128387 [details]
our case (text format)
Comment 2 Carl Anderson CLA 2009-10-07 09:13:54 EDT 
The confusing part here is that org.eclipse.wst.common.modulecore.componentimpl can be (and is) extended many times.  However, what you appear to be asking here is that the extension point allow for some sort of prioritization for multiple extensions that specify the same type.  For example, in org.eclipse.jst.j2ee, there is:

   <extension
         point="org.eclipse.wst.common.modulecore.componentimpl">
      <componentimpl
            typeID="jst.ejb"
            class="org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent">
      </componentimpl>
   </extension>

And you are asking if the extension point can be modified to allow an adopter product to specify its own virtual component extension for an already defined type.  Is that correct?