[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, 2 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, 2 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, 2 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, 2 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, 2 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, 2 months
[JBoss JIRA] (WFLY-3774) CDI bean with StereoType is not injectable in implicit bean archive
by Jozef Hartinger (JIRA)
[ https://issues.jboss.org/browse/WFLY-3774?page=com.atlassian.jira.plugin.... ]
Jozef Hartinger resolved WFLY-3774.
-----------------------------------
Resolution: Cannot Reproduce Bug
WildFly 8.1.0.Final only supports CDI 1.1. For CDI 1.2 support you'll have to build either the master or 8.x branch. I tried your reproducer on both and got a clean test run. Feel free to reopen if you are still able to reproduce the problem on master or 8.x
> CDI bean with StereoType is not injectable in implicit bean archive
> -------------------------------------------------------------------
>
> Key: WFLY-3774
> URL: https://issues.jboss.org/browse/WFLY-3774
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CDI / Weld
> Affects Versions: 8.1.0.Final
> Reporter: Takayoshi Kimura
> Assignee: Jozef Hartinger
> Attachments: stereotype.zip
>
>
> CDI 1.2 defines bean defining annotations and with beans with these annotations should be injectable. However a bean with StereoType, one of bean defining annotations, is not injectable within implicit bean archive on WildFly.
> Attached a simple war project to reproduce this problem. This works on GlassFish 4 but doesn't work on WildFly 8.1.0 nor WildFly 9 master at this time. Making this an explicit bean archive by adding empty beans.xml (or set bean-discovery-mode=all) fixes the problem, the container recognizes the CDI bean correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (LOGTOOL-85) Suppress all warnings in generated sources
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/LOGTOOL-85?page=com.atlassian.jira.plugin... ]
David Lloyd commented on LOGTOOL-85:
------------------------------------
I'd rather not do this. The warnings may indicate real bugs. The processor should be cloning generic types, avoiding this type of warnings at least.
> Suppress all warnings in generated sources
> ------------------------------------------
>
> Key: LOGTOOL-85
> URL: https://issues.jboss.org/browse/LOGTOOL-85
> Project: Log Tool
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 1.2.0.Final
> Reporter: Vlad Arkhipov
> Assignee: James Perkins
>
> Generated logger/messages implementaions may cause the compiler to emit warnings (for example, if your interface method has generic parameters). It will be a problem if you compile with -Xlint:all -Werror flags.
> I suppose there is no real reason to make the processor honour generics, and these warnings can be safely ignored?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (WFLY-3774) CDI bean with StereoType is not injectable in implicit bean archive
by Jozef Hartinger (JIRA)
[ https://issues.jboss.org/browse/WFLY-3774?page=com.atlassian.jira.plugin.... ]
Jozef Hartinger reassigned WFLY-3774:
-------------------------------------
Assignee: Jozef Hartinger (was: Stuart Douglas)
> CDI bean with StereoType is not injectable in implicit bean archive
> -------------------------------------------------------------------
>
> Key: WFLY-3774
> URL: https://issues.jboss.org/browse/WFLY-3774
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CDI / Weld
> Affects Versions: 8.1.0.Final
> Reporter: Takayoshi Kimura
> Assignee: Jozef Hartinger
> Attachments: stereotype.zip
>
>
> CDI 1.2 defines bean defining annotations and with beans with these annotations should be injectable. However a bean with StereoType, one of bean defining annotations, is not injectable within implicit bean archive on WildFly.
> Attached a simple war project to reproduce this problem. This works on GlassFish 4 but doesn't work on WildFly 8.1.0 nor WildFly 9 master at this time. Making this an explicit bean archive by adding empty beans.xml (or set bean-discovery-mode=all) fixes the problem, the container recognizes the CDI bean correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months