[jbosstools-issues] [JBoss JIRA] Updated: (JBDS-710) JBoss Server View > XML Config > Ports > choose a file, right-click > Edit File does nothing or opens wrong file
[
https://jira.jboss.org/jira/browse/JBDS-710?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBDS-710:
----------------------------
Attachment: Screenshot-3.png
Screenshot shows the JBoss Server View, with the file I selected to "Edit File"
shown. Also shown is a console w/ vi running, showing the changes to the file (port
number). This was *NOT* opened by JBDS, I had to go find the file by hand.
Aside:
In the background is the server.xml file. Note all the undisplayable double-byte
characters. The OOTB XML editor is choking on the line feed characters (000A in hex:
http://www.motionnet.com/cgi-bin/search.exe?a=showlink&no=65).
Are these files created w/ Windows or Mac line endings? Shouldn't they have
platform-specific line endings, eg., on linux only 000D (13, carriage return) ? Or is the
problem the WTP editor is too dumb to know how to render them?
JBoss Server View > XML Config > Ports > choose a file,
right-click > Edit File does nothing or opens wrong file
-----------------------------------------------------------------------------------------------------------------
Key: JBDS-710
URL: https://jira.jboss.org/jira/browse/JBDS-710
Project: Developer Studio
Issue Type: Bug
Components: servers
Affects Versions: 2.0.0.GA
Reporter: Nick Boldt
Attachments: Screenshot-3.png
First time I tried this, selecting
"JBoss Server View > XML Config > Ports > choose a file, right-click
> Edit File "
did nothing. So, I opened this issue in a browser, and went back to verify... now it
opens a file, but it's the wrong file - or at least not the file referenced in the
view.
File opened is called "server.xml"; file on which I clicked to see the file
was:
~/jbdevstudio/jboss-eap/jboss-as/server/default/conf/jboss-service.xml
This may be working as intended, but it's unclear WHY the view is linked to a file
which isn't the one mentioned. Usability issue at the very least, if not a functional
problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira