Steps to reproduce:
1) Create an as71 server
2) expand the server in servers view
3) expand the XML Configuration, then expand PORTS
4) right-click on ports, select "new xpath"
5) Fill with details as follows
a) name: blahblah (whatever)
b) root dir: (blank)
c) file pattern: standalone/configuration/${jboss_config_file}
d) xpath pattern: //*[local-name()="socket-binding-group"]
e) xpath attribute: port-offset
6) save xpath
7) look in view, ensure new xpath appearsr
8) look NEXT to new xpath (decorator, grey text), make sure value reads ${jboss.socket.binding.port-offset:0} [FAIL] (?!)
9) right-click new query, click 'edit xpath'
10) Ensure name, root dir, file pattern, xpath pattern, xpath attribute, are as expected [FAIL](?!)
- relates to
-
JBIDE-2050 Add support for ServiceBindingManager for port discovery. (Was AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.)
- Closed
-
JBIDE-9720 Issues when starting and stopping an EAP or SOA-P server using -Djboss.service.binding.set=ports-03 in JBDS
- Closed