[JBoss JIRA] Created: (JBIDE-2627) Add "Server Locations" option to JBoss WTP Adapter to prevent JBoss contamination
by Francisco Jose Peredo Noguez (JIRA)
Add "Server Locations" option to JBoss WTP Adapter to prevent JBoss contamination
---------------------------------------------------------------------------------
Key: JBIDE-2627
URL: https://jira.jboss.org/jira/browse/JBIDE-2627
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 2.1.2
Reporter: Francisco Jose Peredo Noguez
When doing development of serveral independent applications over the JBoss AS, that JBoss AS installation get contaminated by those applications
If I create workspaces1, and inside it I create dynamic webproject 1, and run it on JBoss, then I switch to workspace2, and create dynamic webproject 2, and run it on JBoss, since it is the same JBoss instance, both dynamic webproject 1 and dynamic webproject 2 will start (and there is no way, from inside eclipse to undeploy dynamic webproject 1 unless I go back to workspaces1 and undeploy it.
But, if one is working with Tomcat, there is no problem, applications do not "contaminate" the shared Tomcat, why is that? well the Tomcat WTP Adapter has a configuration option enabled by default under "Server Location", that reads: "Use workspace metadata (does not modify Tomcat installation)". I would like to have an option like that for JBoss AS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBIDE-1967) Editor do not recognize .jsf extension for the JSF files
by Antoine Herzog (JIRA)
Editor do not recognize .jsf extension for the JSF files
--------------------------------------------------------
Key: JBIDE-1967
URL: http://jira.jboss.com/jira/browse/JBIDE-1967
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 2.0.1
Environment: Eclipse 3.3.2 and JB Tools 2.0.1
Reporter: Antoine Herzog
Fix For: 2.1.0.beta1
in JBoss Tools : the .jsf files are recognized for global editor features.
Every things works fine with .xhtml , but not with .jsf.
Even if the file association is set.
What does not work ? : With a .jsf file, I do not get the toolTips, the code completion, the drag and drop of new components...
(but all these features works fine with .xhtml files)
See the forum post.
To check this problem :
- I create a new file (simple new file), with .jsf extension
- I copy into it the exact whole content of a .xhtml file that works well.
=> the file is set as a JSP (the icon is jsp, the default editor is JBoss Tool JSP editor).
if I open it with "open with", and choose JBoss Tool HTML editor.
idem : no code completion, no code validation etc...
note : the icon of the editor window is "green with htm"... and not "blue with jsp". So it is really the JBoss Tool HTML editor.
so, it seems there is something that prevent the editor to run with this file (".jsf") as a jsf file.
The editor do not take into account the .jsf file, as a JSF...
--
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
17 years, 4 months