[
https://issues.jboss.org/browse/WFCORE-3580?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-3580:
------------------------------------------
[~luck3y] I've assigned this to you. I forgot when talking to Alexey about it that
what he had before wouldn't have worked at all with WF 11 / WF Core 3. So as long as
there is no regression versus a .Final release or you don't see something else wrong
this can be rejected.
/host=xxx:add is required now after embedding the host controller
-----------------------------------------------------------------
Key: WFCORE-3580
URL:
https://issues.jboss.org/browse/WFCORE-3580
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 4.0.0.Alpha9
Reporter: Alexey Loubyansky
Assignee: Ken Wills
This is just to report a change in behavior. This is not a critical issue for what I
personally am doing.
The issue is that I used to have a script that would generate a domain.xml configuration
(let's say for the core distribution) that would start like this
{code:java}
embed-host-controller --empty-host-config --remove-existing-host-config
--empty-domain-config --remove-existing-domain-config --host-config=pm-tmp-host.xml
--domain-config=domain.xml
/interface=public:add(inet-address=${jboss.bind.address:127.0.0.1})
/interface=management:add(inet-address=${jboss.bind.address.management:127.0.0.1})
...
{code}
A script like this will fail now because we need to explicitly add a host before
executing any management operation. E.g.
{code:java}
embed-host-controller --empty-host-config --remove-existing-host-config
--empty-domain-config --remove-existing-domain-config --host-config=pm-tmp-host.xml
--domain-config=domain.xml
/host=tmp:add
/interface=public:add(inet-address=${jboss.bind.address:127.0.0.1})
/interface=management:add(inet-address=${jboss.bind.address.management:127.0.0.1})
...
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)