Community
Participate
Working Groups
Please take this enhancement into consideration during the (re)desgin of flexible projects for 1.0. Contributors of Web service runtimes provide a list of component type ids to indicate what kinds of components their particular Web service runtime supports. The Web service wizards create projects/components for users when they don't exist based on the component type id selected by the user. Currently, the wizard is limited to creating components of the following 4 types: IModuleConstants.JST_WEB_MODULE (using WebComponentCreationDataModelProvider) IModuleConstants.JST_EJB_MODULE (using EjbComponentCreationDataModelProvider) IModuleConstants.JST_APPCLIENT_MODULE (using AppClientComponentCreationDataModelProvider) IModuleConstants.JST_EAR_MODULE (using EarComponentCreationDataModelProvider) When an extender comes along and contributes their own component type (e.g. bea.web), the wizards do not have a way of creating the component for the user since knowing the component type id is not sufficient to determine which operation to use. If there is anything is the existing design that would allow to do this, please advise.
*** Bug 108132 has been marked as a duplicate of this bug. ***
Slightly modifying the requested enhancement ... With features in the picture, the Web services wizard needs to be able to drive the creation of components, not based on component type id, but rather based on a set of features/feature categories.
I would like to add something to this. There is one more scenario that could occur. Suppose I have defined 2 different projects into which a web service feature can go. e.g. Web Project -- this takes the Feature - "Std. web service feature". Plus some other features WebService Project -- this also takes Feature - "Std. web service feature" So here the deciding factor would be the Project type and the deciding factor for allowed Project types would be Feature. Or am I missing something?
Perhaps this defect could be dupped against the new feature framework, as "features" will replace the notion of component "type". We will have a notion of features which are mutually exclusive, and will become the new "core" features, such as web/ejb/ear etc....
This enhancement should be solved by the features framework. I'll add more comments there. Comments from Konstantin: The features framework will definitely address the original scenario raised in this bugzilla entry. Basically, knowing the feature id and version is sufficient in order to be able to install it. The framework will figure out what “operation” to run. - Konstantin *** This bug has been marked as a duplicate of 94608 ***
Verified / Closing
