[JBoss JIRA] (AS7-4265) cli command to add/remove AS modules
by David Jensen (JIRA)
[ https://issues.jboss.org/browse/AS7-4265?page=com.atlassian.jira.plugin.s... ]
David Jensen commented on AS7-4265:
-----------------------------------
This works well for me, however, there's one thing which I had to manually change before it would work:
I have a properties file which needs to be outside the WAR file, but yet accessible by the WAR file. I read the instructions on how to do this using the "modules" approach (https://developer.jboss.org/wiki/HowToPutAnExternalFileInTheClasspath), and so using the CLI module "add" command would be perfect.
This is what I did:
module add --name=com.mycompany.myproject.configuration --resources=myproperties.properties (where the myproperties.properties file is in the same folder where I issue this command)
Everything worked well, except that the module.xml file created looked like this:
<?xml version="1.0" ?>
<module xmlns="urn:jboss:module:1.1" name="com.mycompany.myproject.configuration">
<resources>
<resource-root path="myproperties.properties"/> <!-- THIS IS THE LINE WHICH I NEED CHANGED. -->
</resources>
</module>
But what I need is:
<?xml version="1.0" ?>
<module xmlns="urn:jboss:module:1.1" name="com.mycompany.myproject.configuration">
<resources>
<resource-root path="."/> <!-- THIS IS WHAT I NEED. -->
</resources>
</module>
Otherwise the WAR file can't find the properties file.
How do I do this?
Thanks,
> cli command to add/remove AS modules
> ------------------------------------
>
> Key: AS7-4265
> URL: https://issues.jboss.org/browse/AS7-4265
> Project: Application Server 7
> Issue Type: Task
> Components: CLI
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
> Fix For: 7.1.2.Final (EAP)
>
>
> I think it'd be useful to have a command to add modules to the AS which given the jars, dependencies, etc would generate the structure in the modules dir, copy the jars and generate the xml.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ]
ofbiz brazil updated WFLY-3791:
-------------------------------
Description:
Hello,
When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
Java Code:
--------------
final ModelNode request = new ModelNode();
request.get(ClientConstants.OP).set("read-resource");
request.get("recursive").set(true);
request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
final ModelNode response = client.execute(new OperationBuilder(request).build());
final String section = response.get(ClientConstants.RESULT).get("security-domain")
.get("pw_MSSQL_CAS_DS")
Result:
---------
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
"rolled-back" => true
}
Cheers,
was:
Hello,
When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
Java Code:
--------------
final ModelNode request = new ModelNode();
request.get(ClientConstants.OP).set("read-resource");
request.get("recursive").set(true);
request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
final ModelNode response = client.execute(new OperationBuilder(request).build());
Result:
---------
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
"rolled-back" => true
}
Cheers,
> Error on ModelControllerClient to list sections
> -----------------------------------------------
>
> Key: WFLY-3791
> URL: https://issues.jboss.org/browse/WFLY-3791
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Client, CLI, ConfigAdmin, Web Console
> Affects Versions: 8.1.0.Final
> Environment: Java 7
> Reporter: ofbiz brazil
> Assignee: Stuart Douglas
> Priority: Critical
>
> Hello,
> When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
> Java Code:
> --------------
> final ModelNode request = new ModelNode();
> request.get(ClientConstants.OP).set("read-resource");
> request.get("recursive").set(true);
> request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
> final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
> final ModelNode response = client.execute(new OperationBuilder(request).build());
> final String section = response.get(ClientConstants.RESULT).get("security-domain")
> .get("pw_MSSQL_CAS_DS")
> Result:
> ---------
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
> "rolled-back" => true
> }
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ]
ofbiz brazil updated WFLY-3791:
-------------------------------
Component/s: ConfigAdmin
Web Console
> Error on ModelControllerClient to list sections
> -----------------------------------------------
>
> Key: WFLY-3791
> URL: https://issues.jboss.org/browse/WFLY-3791
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Client, CLI, ConfigAdmin, Web Console
> Affects Versions: 8.1.0.Final
> Environment: Java 7
> Reporter: ofbiz brazil
> Assignee: Stuart Douglas
> Priority: Critical
>
> Hello,
> When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
> Java Code:
> --------------
> final ModelNode request = new ModelNode();
> request.get(ClientConstants.OP).set("read-resource");
> request.get("recursive").set(true);
> request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
> final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
> final ModelNode response = client.execute(new OperationBuilder(request).build());
> Result:
> ---------
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
> "rolled-back" => true
> }
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ]
ofbiz brazil updated WFLY-3791:
-------------------------------
Priority: Critical (was: Major)
> Error on ModelControllerClient to list sections
> -----------------------------------------------
>
> Key: WFLY-3791
> URL: https://issues.jboss.org/browse/WFLY-3791
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Client, CLI
> Affects Versions: 8.1.0.Final
> Environment: Java 7
> Reporter: ofbiz brazil
> Assignee: Stuart Douglas
> Priority: Critical
>
> Hello,
> When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
> Java Code:
> --------------
> final ModelNode request = new ModelNode();
> request.get(ClientConstants.OP).set("read-resource");
> request.get("recursive").set(true);
> request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
> final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
> final ModelNode response = client.execute(new OperationBuilder(request).build());
> Result:
> ---------
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
> "rolled-back" => true
> }
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFCORE-74) Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-74?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFCORE-74:
-----------------------------------
Description:
Attribute/parameter descriptions allow "arbitrary descriptors".[1]
Perhaps we could add something like this to that list:
filesystem-path -- boolean -- indicates the attribute value represents a filesystem
path. The absence of this item implies false.
The CLI could then check for that and help the user with escaping if true. Currently CLI users need to escape '\' in low-level operation values, but they don't in commands. It's not necessary in commands because the CLI statically knows what the command is about; with a low level operation it can only do things based on the metadata provided by the server.
We can't guarantee that every 'path' attribute would have that set
properly though. So it's not a guarantee.
This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
Also, consider other similar cases -- 'url' as a possible example.
[1] https://docs.jboss.org/author/display/WFLY9/Admin+Guide#AdminGuide-Arbitr...
was:
Attribute/parameter descriptions allow "arbitrary descriptors".[1]
Perhaps we could add something like this to that list:
path -- boolean -- indicates the attribute value represents a filesystem
path. The absence of this item implies false.
The CLI could then check for that and help the user with escaping if true. Currently CLI users need to escape '\' in low-level operation values, but they don't in commands. It's not necessary in commands because the CLI statically knows what the command is about; with a low level operation it can only do things based on the metadata provided by the server.
We can't guarantee that every 'path' attribute would have that set
properly though. So it's not a guarantee.
This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
Also, consider other similar cases -- 'url' as a possible example.
[1] https://docs.jboss.org/author/display/WFLY9/Admin+Guide#AdminGuide-Arbitr...
> Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-74
> URL: https://issues.jboss.org/browse/WFCORE-74
> Project: WildFly Core
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
>
> Attribute/parameter descriptions allow "arbitrary descriptors".[1]
> Perhaps we could add something like this to that list:
> filesystem-path -- boolean -- indicates the attribute value represents a filesystem
> path. The absence of this item implies false.
> The CLI could then check for that and help the user with escaping if true. Currently CLI users need to escape '\' in low-level operation values, but they don't in commands. It's not necessary in commands because the CLI statically knows what the command is about; with a low level operation it can only do things based on the metadata provided by the server.
> We can't guarantee that every 'path' attribute would have that set
> properly though. So it's not a guarantee.
> This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
> Also, consider other similar cases -- 'url' as a possible example.
> [1] https://docs.jboss.org/author/display/WFLY9/Admin+Guide#AdminGuide-Arbitr...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
ofbiz brazil created WFLY-3791:
----------------------------------
Summary: Error on ModelControllerClient to list sections
Key: WFLY-3791
URL: https://issues.jboss.org/browse/WFLY-3791
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Application Client, CLI
Affects Versions: 8.1.0.Final
Environment: Java 7
Reporter: ofbiz brazil
Assignee: Stuart Douglas
Hello,
When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
Java Code:
--------------
final ModelNode request = new ModelNode();
request.get(ClientConstants.OP).set("read-resource");
request.get("recursive").set(true);
request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
final ModelNode response = client.execute(new OperationBuilder(request).build());
Result:
---------
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
"rolled-back" => true
}
Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFCORE-74) Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-74?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFCORE-74:
-----------------------------------
Description:
Attribute/parameter descriptions allow "arbitrary descriptors".[1]
Perhaps we could add something like this to that list:
path -- boolean -- indicates the attribute value represents a filesystem
path. The absence of this item implies false.
The CLI could then check for that and help the user with escaping if true. Currently CLI users need to escape '\' in low-level operation values, but they don't in commands. It's not necessary in commands because the CLI statically knows what the command is about; with a low level operation it can only do things based on the metadata provided by the server.
We can't guarantee that every 'path' attribute would have that set
properly though. So it's not a guarantee.
This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
Also, consider other similar cases -- 'url' as a possible example.
[1] https://docs.jboss.org/author/display/WFLY9/Admin+Guide#AdminGuide-Arbitr...
was:
Attribute/parameter descriptions allow "arbitrary descriptors".[1]
Perhaps we could add something like this to that list:
path -- boolean -- indicates the attribute value represents a filesystem
path. The absence of this item implies false.
The CLI could then check for that and help the user with escaping if true. Currently CLI users need to escape '\' in low-level operation values, but they don't in commands. It's not necessary in commands because the CLI statically knows what the command is about; with a low level operation it can only do things based on the metadata provided by the server.
We can't guarantee that every 'path' attribute would have that set
properly though. So it's not a guarantee.
This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
Also, consider other similar cases -- 'url' as a possible example.
> Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-74
> URL: https://issues.jboss.org/browse/WFCORE-74
> Project: WildFly Core
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
>
> Attribute/parameter descriptions allow "arbitrary descriptors".[1]
> Perhaps we could add something like this to that list:
> path -- boolean -- indicates the attribute value represents a filesystem
> path. The absence of this item implies false.
> The CLI could then check for that and help the user with escaping if true. Currently CLI users need to escape '\' in low-level operation values, but they don't in commands. It's not necessary in commands because the CLI statically knows what the command is about; with a low level operation it can only do things based on the metadata provided by the server.
> We can't guarantee that every 'path' attribute would have that set
> properly though. So it's not a guarantee.
> This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
> Also, consider other similar cases -- 'url' as a possible example.
> [1] https://docs.jboss.org/author/display/WFLY9/Admin+Guide#AdminGuide-Arbitr...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFCORE-74) Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-74?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFCORE-74:
-----------------------------------
Issue Type: Enhancement (was: Feature Request)
> Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-74
> URL: https://issues.jboss.org/browse/WFCORE-74
> Project: WildFly Core
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
>
> Attribute/parameter descriptions allow "arbitrary descriptors".[1]
> Perhaps we could add something like this to that list:
> path -- boolean -- indicates the attribute value represents a filesystem
> path. The absence of this item implies false.
> The CLI could then check for that and help the user with escaping if true. Currently CLI users need to escape '\' in low-level operation values, but they don't in commands. It's not necessary in commands because the CLI statically knows what the command is about; with a low level operation it can only do things based on the metadata provided by the server.
> We can't guarantee that every 'path' attribute would have that set
> properly though. So it's not a guarantee.
> This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
> Also, consider other similar cases -- 'url' as a possible example.
> [1] https://docs.jboss.org/author/display/WFLY9/Admin+Guide#AdminGuide-Arbitr...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFCORE-74) Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-74?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFCORE-74:
-----------------------------------
Description:
Attribute/parameter descriptions allow "arbitrary descriptors".[1]
Perhaps we could add something like this to that list:
path -- boolean -- indicates the attribute value represents a filesystem
path. The absence of this item implies false.
The CLI could then check for that and help the user with escaping if true. Currently CLI users need to escape '\' in low-level operation values, but they don't in commands. It's not necessary in commands because the CLI statically knows what the command is about; with a low level operation it can only do things based on the metadata provided by the server.
We can't guarantee that every 'path' attribute would have that set
properly though. So it's not a guarantee.
This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
Also, consider other similar cases -- 'url' as a possible example.
was:
Attribute/parameter descriptions allow "arbitrary descriptors".[1]
Perhaps we could add something like this to that list:
path -- boolean -- indicates the attribute value represents a filesystem
path. The absence of this item implies false.
The CLI could then check for that and help the user with escaping if true.
We can't guarantee that every 'path' attribute would have that set
properly though. So it's not a guarantee.
This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
Also, consider other similar cases -- 'url' as a possible example.
> Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-74
> URL: https://issues.jboss.org/browse/WFCORE-74
> Project: WildFly Core
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
>
> Attribute/parameter descriptions allow "arbitrary descriptors".[1]
> Perhaps we could add something like this to that list:
> path -- boolean -- indicates the attribute value represents a filesystem
> path. The absence of this item implies false.
> The CLI could then check for that and help the user with escaping if true. Currently CLI users need to escape '\' in low-level operation values, but they don't in commands. It's not necessary in commands because the CLI statically knows what the command is about; with a low level operation it can only do things based on the metadata provided by the server.
> We can't guarantee that every 'path' attribute would have that set
> properly though. So it's not a guarantee.
> This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
> Also, consider other similar cases -- 'url' as a possible example.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFCORE-74) Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-74:
--------------------------------------
Summary: Use 'filesystem-path' arbitrary descriptor for attributes/params that represent a path
Key: WFCORE-74
URL: https://issues.jboss.org/browse/WFCORE-74
Project: WildFly Core
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Attribute/parameter descriptions allow "arbitrary descriptors".[1]
Perhaps we could add something like this to that list:
path -- boolean -- indicates the attribute value represents a filesystem
path. The absence of this item implies false.
The CLI could then check for that and help the user with escaping if true.
We can't guarantee that every 'path' attribute would have that set
properly though. So it's not a guarantee.
This is really a cross-request between WFCORE and WFLY; WFCORE with the needed base support and then configuring any relevant params/attributes in both code bases.
Also, consider other similar cases -- 'url' as a possible example.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months