Bugzilla – Full Text Bug Listing
| Summary: | ext point org.eclipse.wst.common.modulecore.componentimpl | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Common Tools | Reporter: | Dimo Stoilov <Dimo.Stoilov> | ||||||
| Component: | wst.common | Assignee: | Chuck Bridgham <cbridgha> | ||||||
| Status: | NEW --- | QA Contact: | Konstantin Komissarchik <konstantin> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | ccc, dimitar.giormov, kaloyan | ||||||
| Version: | 3.0.3 | Keywords: | helpwanted | ||||||
| Target Milestone: | Future | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 128387 [details]
our case (text format)
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?
|
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