Community
Participate
Working Groups
I created an IBM WebSphere 6 Server mapping, but specified the cell name incorrectly. I opened the editor on the configuration and clicked "Open Launch Configuration". In the "Properties for IBM WebSphere 6" dialog, I switch to the "Arguments" page and changed the incorrectly-specified cell name to the correct value. I click "Apply", then "Okay" (effect is the same when I don't click "Apply" first). I close the window and reopen (by clicking "Open Launch Configuration"). The original text remains (i.e. my changes are gone). If I add to the end of the Program arguments, the change does remain. Any changes I attempt to make anywhere in the existing value are discarded (at least every combination that I've tried). I also tried this by going through the Run Configuration dialog ("Run > Run..."). Same effect. I can provide screen shots if you think this would be valuable. For kicks, I created a Tomcat server and tried messing around with it to see if it has similar problems. The value for Tomcat is simply "start". If I add text to the end, it retains the changes. If I change the word "start", it appends the word "start" after my changes the next time I open the window. I can show this if you'd like, but the changes I'm making don't really make any sense, so I don't know how valuable screen shots will be.
For the generic servers, including websphere adapter this is the expected behavior(although not the right one). The problem is initially the arguments were treated by the generic server framework as a long string so detecting the changes in the middle required very ugly methods. After the 0.7 release I have added the possibility to add the arguments seperately(some work left for 1.5 as well) into framework but for backward compatability reasons the long string option is still supported. Most of the server adapters(if not all) use the old way which result in the behavior you have described.
*** Bug 157645 has been marked as a duplicate of this bug. ***
*** Bug 162811 has been marked as a duplicate of this bug. ***
Any plan to solve this problem? We are already to 1.5.1 and the server support is still not usable. We need to use a jboss configuration with non standard ports and we need to pass some properties at startup, but launch config and server definition are always reset to default each time we start the server or open launch configuration. Pls could you raise the severity/priority of this bug? Thanks, Gabriele
Fixed on the HEAD and will release for the 2.0 stream. With this fix VM and program arguments are never recreated
resolving
*** Bug 169936 has been marked as a duplicate of this bug. ***
Closing as fixed since M1.
New Gerrit change created: https://git.eclipse.org/r/108078
