[
http://jira.jboss.com/jira/browse/JBIDE-2262?page=comments#action_12416965 ]
Max Rydahl Andersen commented on JBIDE-2262:
--------------------------------------------
Im not sure what you are asking for, but I saw there were code commited with startup
initialization forcing jbossws for all ? That is wrong.
No plugin should enforce these kind of global things - that is for product builds (e.g.
JBDS), not standalone plugins.
What I meant with set as default is that I assumed that when a project has WS enabled on a
project that the WTP wizards would somehow be able to know what is the default webservice
provider for that project - are you saying that is not the case and there are only a
global setting ?
WSFacet should have an ui with options for libraries and setup
JBossWS as default in WS dialogs
------------------------------------------------------------------------------------------------
Key: JBIDE-2262
URL:
http://jira.jboss.com/jira/browse/JBIDE-2262
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Webservices
Reporter: Max Rydahl Andersen
Assigned To: Denny Xu
Fix For: 3.0.alpha
Similar to JSF facet ui.
Two options:
* Server supplies runtime
* List of runtimes which classpath to add
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira