[JBoss JIRA] Created: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
8:09 a.m.
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
3:56 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-8355:
---------------------------------------
Fix Version/s: 3.2.1
3.3.x
Rob - are we still using hardcoded paths to these locations instead of relative to the
configuration ?!
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
Fix For: 3.2.1, 3.3.x
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
5:37 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-8355:
------------------------------------
we sure are!
XPaths was one of the things that really really were difficult for me to change and use
relative, and I kept delaying it. It would require really really heavy changes (last time
I checked, which I don't expect to have changed). I can give it another look of
course, but, yeah. XPaths was one of the things i evaluated and kept putting off as too
difficult.
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
Fix For: 3.2.1, 3.3.x
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
2:18 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-8355:
-------------------------------
Fix Version/s: 3.3.0.M2
(was: 3.3.x)
(was: 3.2.1.M1)
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
Fix For: 3.3.0.M2
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
9:09 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Rob Cernich commented on JBIDE-8355:
------------------------------------
I just discovered this problem myself, which manifested itself as:
Error adding deployment folder to deployment scanner
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
I was able to work around the problem by:
1. Close Eclipse
2. Modify xpaths.xml file to point to my configuration folder.
3. Start Eclipse
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
Fix For: 3.3.0.M2
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
10:45 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Rob Cernich commented on JBIDE-8355:
------------------------------------
I don't know if this is related (or should be a new issue), but another thing I've
noticed is that the jar files in the library entries (e.g. JBoss ESB Runtime, JBoss
Enterprise Application Platform) point to the "default" jars instead of the
specified configuration's jars.
My workaround: (I don't know if the first step is necessary)
1. update the runtime: select a different config, then the desired config, press finish.
2. close the project
3. open the project
4. the jars listed in the library are now from the desired configuration
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
Fix For: 3.3.0.M2
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
4:15 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-8355:
------------------------------------
I believe it does use the proper config's jars, however, it does not automatically
update after modifying the runtime configuration name. So... that would have to be a
separate issue, but still an important use-case.
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
Fix For: 3.3.0.M2
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
5:30 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-8355:
--------------------------------------------
Rob, was that issue ever created ? link?
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
Fix For: 3.3.0.M3
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
5:30 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-8355:
---------------------------------------
Fix Version/s: 3.3.0.M3
(was: 3.3.0.M2)
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
Fix For: 3.3.0.M3
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
10:03 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Rob Cernich commented on JBIDE-8355:
------------------------------------
Max,
I'm unable to reproduce the classpath/library container issue and I don't fully
remember what I may have done to get my workspace into that state.
Rob,
I was able to reproduce the configuration issue:
1. Create two runtime definitions which use different server configurations.
2. Create a server definition using one of the runtime definitions.
3. Copy the server definition (copy/paste in the servers view).
4. Edit the new server definition, changing the runtime associated with the server.
5. Notice the configuration points to the configuration files of the original runtime.
Hope that helps,
Rob
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
Fix For: 3.3.0.M3
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
9:55 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-8355.
--------------------------------
Resolution: Done
This is committed to trunk. Unfortunately it will not fix OLD servers. Only new servers
will benefit from this change.
New servers will have all default (initial) xpaths created with server-relative basedirs,
and, when relevant, will include a ${jboss_config} variable. It will also pass the string
through the Variables plugin for further string replacement.
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
Fix For: 3.3.0.M3
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
10:42 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Len DiMaggio updated JBIDE-8355:
--------------------------------
Affects: [Release Notes]
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/Servers
Affects Versions: 3.2.0.CR1
Reporter: Magnus Mogren
Assignee: Rob Stryker
Fix For: 3.3.0.M3
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
10:44 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Len DiMaggio updated JBIDE-8355:
--------------------------------
Attachment: JBIDE-8355.png
Verified fixed in:
jbosstools-3.3_stable_branch.aggregate-Update-2011-09-07_05-39-13-H18.zip
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/Servers
Affects Versions: 3.2.0.CR1
Reporter: Magnus Mogren
Assignee: Rob Stryker
Fix For: 3.3.0.M3
Attachments: JBIDE-8355.png
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
10:46 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
[
https://issues.jboss.org/browse/JBIDE-8355?page=com.atlassian.jira.plugin...
]
Len DiMaggio closed JBIDE-8355.
-------------------------------
Verified fixed in:
jbosstools-3.3_stable_branch.aggregate-Update-2011-09-07_05-39-13-H18.zip
2 notes for docs:
1) As stated in the JIRA, the solution works for new server definitions
2) If the user has the Runtime Server dialog open when the
conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml file is edited - then the user
must close and re-open the dialog to see the changes.
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/Servers
Affects Versions: 3.2.0.CR1
Reporter: Magnus Mogren
Assignee: Rob Stryker
Fix For: 3.3.0.M3
Attachments: JBIDE-8355.png
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
5135
days inactive
5351
days old
jbosstools-issues@lists.jboss.org
13 comments
5 participants
participants (5)
-
Len DiMaggio (JIRA) -
Magnus Mogren (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Cernich (JIRA)
-
Rob Stryker (JIRA)