[JBoss JIRA] (JBLOGGING-102) Messages#getBundle() needs to be privileged
by Ivo Studensky (JIRA)
Ivo Studensky created JBLOGGING-102:
---------------------------------------
Summary: Messages#getBundle() needs to be privileged
Key: JBLOGGING-102
URL: https://issues.jboss.org/browse/JBLOGGING-102
Project: JBoss Logging
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.2.0.Beta1, 3.1.4.GA
Reporter: Ivo Studensky
Assignee: James Perkins
Fix For: 3.1.5.GA, 3.2.0.Beta2
It ({{org.jboss.logging.Messages#getBundle(Class<T> type, Locale locale)}}) calls {{type.getClassLoader()}} which requires privileges when running with Security Manager.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-3170) system properties are trim()'d and loose whitespace
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3170?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-3170:
----------------------------------------
AIUI you are suggesting using different logic for ModelType.PROPERTY?
That won't work; very few attributes are of type PROPERTY. I'm quite sure a system property resource's value attribute is type STRING.
I'm opposed to changing the AttributeDefinition.parse method, at least for EAP 6.3.x. That will effect nearly every attribute in the system and could produce undesired changes in behavior.
> system properties are trim()'d and loose whitespace
> ---------------------------------------------------
>
> Key: WFLY-3170
> URL: https://issues.jboss.org/browse/WFLY-3170
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.1.Final
> Reporter: Tom Fonteyne
> Assignee: Brian Stansberry
>
> When a system property was defined as:
> /system-property=foo:add(value=" spaces ");
> it gets written with the correct spaces around it to the configuration file.
> When the configuration is read the value gets trimmed and the prefix/suffix of spaces is lost.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-2857) command/operation substitution enclosed with `
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-2857?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky resolved WFLY-2857.
-------------------------------------
Resolution: Done
Merged into master.
> command/operation substitution enclosed with `
> ----------------------------------------------
>
> Key: WFLY-2857
> URL: https://issues.jboss.org/browse/WFLY-2857
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: CLI
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
> Fix For: 8.0.1.Final
>
>
> Command/operation substitution (following linux style back quoting an expression) would be a useful feature. Among other things, it would be useful to be able to initialize an environment variable to a result of a command or an operation, e.g.
> set value=`:read-attribute(name=release-version)`
> or
> set value=$(:read-attribute(name=release-version))
> and
> echo $value
> 8.0.0.Final-SNAPSHOT
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-3004) properties are not resolved for arguments of commands handled on the client-side
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-3004?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky resolved WFLY-3004.
-------------------------------------
Resolution: Done
Merged into master.
> properties are not resolved for arguments of commands handled on the client-side
> --------------------------------------------------------------------------------
>
> Key: WFLY-3004
> URL: https://issues.jboss.org/browse/WFLY-3004
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CLI
> Affects Versions: 8.0.0.Final
> Environment: windows 7 and centos 6.4
> Reporter: Gabriele Garuglieri
> Assignee: Alexey Loubyansky
> Fix For: 8.0.1.Final
>
>
> When using cli for batch files using --file and --properties arguments, any property is resolved but for those defined in the connect command line.
> The properties file contains (among the others):
> server.bind.addr = xxxxx
> server.management.port = 9990
> Having:
> connect ${server.bind.addr}
> in the batch file gets
> ERROR [org.jboss.as.cli.CommandContext] Failed to resolve host '${server.bind.addr}': Failed to create URI: Illegal character in authority at index 16: http-remoting://${server.bind.addr}:9990
> Having:
> connect ${server.bind.addr}:${server.management.port}
> gets:
> ERROR [org.jboss.as.cli.CommandContext] The port must be a valid non-negative integer: '${server.bind.addr}:${server.management.
> If i use literal values for the connect command, any other property in the batch is correctly resolved (but that's exactly what i was trying to avoid)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-3004) properties are not resolved for arguments of commands handled on the client-side
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-3004?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky updated WFLY-3004:
------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/6019
> properties are not resolved for arguments of commands handled on the client-side
> --------------------------------------------------------------------------------
>
> Key: WFLY-3004
> URL: https://issues.jboss.org/browse/WFLY-3004
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CLI
> Affects Versions: 8.0.0.Final
> Environment: windows 7 and centos 6.4
> Reporter: Gabriele Garuglieri
> Assignee: Alexey Loubyansky
> Fix For: 8.0.1.Final
>
>
> When using cli for batch files using --file and --properties arguments, any property is resolved but for those defined in the connect command line.
> The properties file contains (among the others):
> server.bind.addr = xxxxx
> server.management.port = 9990
> Having:
> connect ${server.bind.addr}
> in the batch file gets
> ERROR [org.jboss.as.cli.CommandContext] Failed to resolve host '${server.bind.addr}': Failed to create URI: Illegal character in authority at index 16: http-remoting://${server.bind.addr}:9990
> Having:
> connect ${server.bind.addr}:${server.management.port}
> gets:
> ERROR [org.jboss.as.cli.CommandContext] The port must be a valid non-negative integer: '${server.bind.addr}:${server.management.
> If i use literal values for the connect command, any other property in the batch is correctly resolved (but that's exactly what i was trying to avoid)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-3170) system properties are trim()'d and loose whitespace
by Tom Fonteyne (JIRA)
Tom Fonteyne created WFLY-3170:
----------------------------------
Summary: system properties are trim()'d and loose whitespace
Key: WFLY-3170
URL: https://issues.jboss.org/browse/WFLY-3170
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Domain Management
Affects Versions: 8.0.1.Final
Reporter: Tom Fonteyne
Assignee: Brian Stansberry
When a system property was defined as:
/system-property=foo:add(value=" spaces ");
it gets written with the correct spaces around it to the configuration file.
When the configuration is read the value gets trimmed and the prefix/suffix of spaces is lost.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (WFLY-2881) org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-2881?page=com.atlassian.jira.plugin.... ]
Eduardo Martins resolved WFLY-2881.
-----------------------------------
Fix Version/s: 8.0.1.Final
Resolution: Done
> org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout
> --------------------------------------------------------------------------------------
>
> Key: WFLY-2881
> URL: https://issues.jboss.org/browse/WFLY-2881
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB
> Affects Versions: 8.0.0.Final
> Reporter: Frank Langelage
> Assignee: Eduardo Martins
> Fix For: 8.0.1.Final
>
> Attachments: org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.txt, TEST-org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.xml
>
>
> Running build with smoke tests on current github sources I get failure in this test case.
> HOUR_OF_DAY is not 0 as expected but 1.
> I changed the Assert in the test case to print out firstTimeout.toString() instead of only timeZoneDisplayName.
> See attached files for more.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months