March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3115) JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources

by Thomas Kriechbaum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3115?page=com.atlassian.jira.plugin.... ] Thomas Kriechbaum commented on WFLY-3115: ----------------------------------------- I have tested this scenario with wildfly 8.0.1 SNAPSHOT Build #1040 (25.3.2014 - https://ci.jboss.org/hudson/job/WildFly-latest-master/1040/) With this build @Resource(lookup="java:app/url/Configuration") and the following entry in jboss-web.xml resolves an URL defined within standalone.xml <resource-ref> <res-ref-name>java:app/url/Configuration</res-ref-name> <jndi-name>java:jboss/url/Configuration</jndi-name> </resource-ref> see WFLY-2423 that covers the appropriate fix. > JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources > ----------------------------------------------------------------------------------------- > > Key: WFLY-3115 > URL: https://issues.jboss.org/browse/WFLY-3115 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Thomas Kriechbaum > > When using URL-Resources it would be very helpful, if the jboss-specific deployment descriptor (e.g. jboss-web.xml or jboss-app.xml) allows to reference a JNDI-name. At the moment, only valid URLs are supported. > When defining JNDI-names (e.g. java:jboss/url/Configuration) instead of concrete URLs, the EAR must not be adopted for each deployment as the specific URL is part of the server configuration (e.g. standalone.xml). > see proposal by [~sfcoy] at https://community.jboss.org/message/861952#861952 -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3114) @Resource(lookup="java:...") causes an exception for URL resources

by Thomas Kriechbaum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3114?page=com.atlassian.jira.plugin.... ] Thomas Kriechbaum commented on WFLY-3114: ----------------------------------------- I have tested this scenario with wildfly 8.0.1 SNAPSHOT Build #1040 (25.3.2014 - https://ci.jboss.org/hudson/job/WildFly-latest-master/1040/) With this build @Resource(lookup="java:...") does not throw an exception any more! see WFLY-2423 that covers the appropriate fix. > @Resource(lookup="java:...") causes an exception for URL resources > ------------------------------------------------------------------- > > Key: WFLY-3114 > URL: https://issues.jboss.org/browse/WFLY-3114 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Thomas Kriechbaum > > When referencing an URL resource via @Resource the lookup-property only supports a valid URLs (e.g. http://www.jboss.org). A JNDI-Name causes an exception (e.g. java:global/url/Configuration or java:app/url/Configuration) > Issue has been discussed in the user form. > Note: > @Resource(name="java:global/url/Configuration") works. > From my point of view, the javadoc of @Resource is not very easy to understand. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3164) Create customized Audit Logger

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3164?page=com.atlassian.jira.plugin.... ] Kabir Khan commented on WFLY-3164: ---------------------------------- One issue is that we currently only handle two kinds of 'events': -controller audit events -jmx audit events There is talk of supporting more events like authorization done, connection opened etc. so what we come up with needs to be flexible enough to handle those, and possibly more events like that in the future. The concern being if a user implements a custom formatter for 9.0.0, and we add some more events for 9.1.0 their custom formatter should still work although more events were added for 9.1.0. A half-baked idea, take with a pinch of salt, is that perhaps for the custom formatter we could have a reference back to one of the WF provided handler types as a 'fallback' for events not handled by the custom formatter. > Create customized Audit Logger > ------------------------------ > > Key: WFLY-3164 > URL: https://issues.jboss.org/browse/WFLY-3164 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Labels: EAP > Fix For: 9.0.0.CR1 > > > Some users want to have a single line audit log formatter. I think it would be better to have the ability to add your own formatter from a module, something along the lines of: > {code} > <custom-formatter code="org.blah.MyCustomFormatter" module="org.blah/mymodule"> > <property name="layout">...</property> > <property name="propB">...</property> > </custom-formatter> > {code} > We'd need an SPI, and a slight reworking of the audit log internals. In any case doing this will put us in a better position to provide the single line logger if this proposal is not acceptable to our users. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-102) Messages#getBundle() needs to be privileged

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-102?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on JBLOGGING-102: --------------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1080991|https://bugzilla.redhat.com/show_bug.cgi?id=1080991] from NEW to ASSIGNED > 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.1.4.GA, 3.2.0.Beta1 > Reporter: Ivo Studensky > Assignee: James Perkins > Fix For: 3.1.3.GA, 3.2.0.Beta1 > > > 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-102) Messages#getBundle() needs to be privileged

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-102?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on JBLOGGING-102: --------------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1080991|https://bugzilla.redhat.com/show_bug.cgi?id=1080991] from ASSIGNED to NEW > 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.1.4.GA, 3.2.0.Beta1 > Reporter: Ivo Studensky > Assignee: James Perkins > Fix For: 3.1.3.GA, 3.2.0.Beta1 > > > 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-102) Messages#getBundle() needs to be privileged

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-102?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on JBLOGGING-102: --------------------------------------------------- James Perkins <jperkins(a)redhat.com> changed the Status of [bug 1080991|https://bugzilla.redhat.com/show_bug.cgi?id=1080991] from NEW to ASSIGNED > 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.1.4.GA, 3.2.0.Beta1 > Reporter: Ivo Studensky > Assignee: James Perkins > Fix For: 3.1.3.GA, 3.2.0.Beta1 > > > 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-102) Messages#getBundle() needs to be privileged

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-102?page=com.atlassian.jira.plu... ] James Perkins closed JBLOGGING-102. ----------------------------------- Fix Version/s: 3.2.0.Beta1 3.1.3.GA (was: 3.1.5.GA) (was: 3.2.0.Beta2) Resolution: Done Already fixed 3.1.3.GA > 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.1.4.GA, 3.2.0.Beta1 > Reporter: Ivo Studensky > Assignee: James Perkins > Fix For: 3.2.0.Beta1, 3.1.3.GA > > > 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3164) Create customized Audit Logger

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3164?page=com.atlassian.jira.plugin.... ] Kabir Khan reassigned WFLY-3164: -------------------------------- Assignee: Kabir Khan (was: Brian Stansberry) > Create customized Audit Logger > ------------------------------ > > Key: WFLY-3164 > URL: https://issues.jboss.org/browse/WFLY-3164 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Labels: EAP > Fix For: 9.0.0.CR1 > > > Some users want to have a single line audit log formatter. I think it would be better to have the ability to add your own formatter from a module, something along the lines of: > {code} > <custom-formatter code="org.blah.MyCustomFormatter" module="org.blah/mymodule"> > <property name="layout">...</property> > <property name="propB">...</property> > </custom-formatter> > {code} > We'd need an SPI, and a slight reworking of the audit log internals. In any case doing this will put us in a better position to provide the single line logger if this proposal is not acceptable to our users. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3170) system properties are trim()'d and loose whitespace

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/WFLY-3170?page=com.atlassian.jira.plugin.... ] Tom Fonteyne commented on WFLY-3170: ------------------------------------ yup, that's it indeed. I'll get a pull request done for WildFly, but I understand the high risk /postponing for EAP > 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

12 years, 1 month

1
0
0 / 0

[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: ---------------------------------------- Ah, I see. So you a proposing limiting the "no trim" behavior to types that store a string, STRING and the elements in in PROPERTY (perhaps just the value.) I'd be open to trying this in WF 9, but it should not go into EAP 6 until it has been in the wild for a long time. Not in 6.3.x. > 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

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014