[jbosside-dev] JIRA starting server with different ports doesnt work

[Rob Stryker]

I'm completley unsure how I should remedy this JIRA issue:
http://jira.jboss.com/jira/browse/JBIDE-405

There are primarily three places ports are stored. The xml files first and
foremost. The XPath editor which can modify the xml files directly. And
finally, the launch configuration arguments.

One implementation of my plugin read strictly from the appropriate xml files
and shoved them into the command line arguments for starting and stopping
the server. But then a user complained that when he modified the command
line args directly, it was still reading from the xml file.

So, it became obvious the xml files should just prime the command args as
starting defaults and after that the user should modify them directly.
However Max is suggesting I add a tab for them. If I add a tab for them,
modifying the fields on the new Ports tab should have what effect exactly?

1) Should modifying a port on such a tab automatically change the command
line arguments for start, stop, and twiddle?
2) Should modifying a port on such a tab change the xml files in the
server's home directory?
3) Should modifying a port in an xml file directly automatically change the
command line arguments?
4) Should modifying a port in an xml file through the xpaths editor in
properties view change the command line arguments?

It seems to me that no matter how I do this, some people are going to be
annoyed, and the easiest answer is to just give the user more control and do
less for them. Maybe I'm just being unambitious. Maybe I'm missing an
obvious answer.

- Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20061113/8d04958e/attachment.html