[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
B.J. Reed updated GERONIMODEVTOOLS-176:
---------------------------------------
Attachment: GERONIMODEVTOOLS-176.patch
It looks like the majority of this has been fixed. At least I could double
click the server and bring up the Overview page and I could change the RMI
Naming port to match the server (non 1099). Then I was able to start the
server outside of the GEP and the GEP updated its status properly. I was also
still able to start the server from within GEP.
However, looking at the code a little more closely, I did find one place in
GeronimoServerBehaviourDelegate.java that still had 1099 hard coded. A patch
is included to put the proper value in the map.
> GeronimoServerBehaviourDelegate always uses rmi port 1099
> ---------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-176
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-176
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.1.3
> Reporter: Donald Woods
> Assignee: Tim McConnell
> Fix For: 2.1.3
>
> Attachments: GERONIMODEVTOOLS-176.patch
>
>
> We need to allow the user to reconfigure the RMI port, for the cases where
> they have mapped the server to use something besides the default 1099 port.
> Also, this would allow the plugin to support the new multiple server instance
> feature in the 2.0 server....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
