[JBoss JIRA] Created: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
by Magnus Mogren (JIRA)
Automatic detection of server ports cannot handle changing configuration from default
-------------------------------------------------------------------------------------
Key: JBIDE-8355
URL: https://issues.jboss.org/browse/JBIDE-8355
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR1
Reporter: Magnus Mogren
Assignee: Rob Stryker
I create a new server for JBoss AS 6.0.
I select the "default" configuration in the "New server" dialog.
JNDI port is detected as 1099 as it should be.
Now i open the "Edit server runtime environment" dialog and change from "default" to "all" configuration.
I have edited the conf/bindingservice.beans\META-INF\bindings-jboss-beans.xml file to use JNDI port 11099 instead of 1099 for the "all" configuration.
Now the autodetected JNDI port is still 1099?
If i click the "Configure..." next to the auto detect checkbox and then "Edit XPath" i see that the root directory is still pointing to the default configuration.
If i click the browse button and try to change the root directory it does not take the change. It still points to the default directory the next time i open the "Edit XPath" dialog.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9399) JBoss 7.1 not usable
by Juergen Zimmermann (JIRA)
JBoss 7.1 not usable
--------------------
Key: JBIDE-9399
URL: https://issues.jboss.org/browse/JBIDE-9399
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.3.0.M2
Environment: build 3203
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
JBoss 7.1 (snapshots) are not directly usable. When creating such a server, then a warning appears (screenshot will be attached). After the creating the "launch configuration properties" are wrong regarding the "Program arguments":
* --configuration=default
* instead of: -mp "c:/Software/jboss/modules" -logmodule org.jboss.logmanager -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone
It would be could if this issue could be fixed. Thank you.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9455) Errors due to unsatisfied JSF constraints should be handled more gracefully
by Fred Bricon (JIRA)
Errors due to unsatisfied JSF constraints should be handled more gracefully
---------------------------------------------------------------------------
Key: JBIDE-9455
URL: https://issues.jboss.org/browse/JBIDE-9455
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 3.3.0.M3
While testing appfuse-light-jsf-archetype:2.1.0, Error popups show up during project creation.
The problem is the archetype depends on JSF 2.0 but uses web.xml version 2.4.
JavaEE6 spec requires servlet version >= 2.5 to use JSF 2.0, and WTP is very strict about that.
Instead of displaying an error popup, it'd be more appropriate to add error markers :
* "JavaServer Faces 2.0 can not be installed : One or more constraints have not been satisfied."
* "JavaServer Faces 2.0 requires Dynamic Web Module 2.5 or newer."
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months