January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6316) Update all PrivilegedAction and PrivilegedExceptionAction to be singletons and ensure correct use of Void return type where appropriate.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-6316?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-6316: ---------------------------------- Summary: Update all PrivilegedAction and PrivilegedExceptionAction to be singletons and ensure correct use of Void return type where appropriate. (was: Update all PrivilegedAction amd PrivilegedExceptionAction to be singletons and ensure correct use of Void return type where appropriate.) > Update all PrivilegedAction and PrivilegedExceptionAction to be singletons and ensure correct use of Void return type where appropriate. > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6316 > URL: https://issues.jboss.org/browse/AS7-6316 > Project: Application Server 7 > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 7.2.0.Alpha1 > > -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6316) Update all PrivilegedAction amd PrivilegedExceptionAction to be singletons and ensure correct use of Void return type where appropriate.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-6316: ------------------------------------- Summary: Update all PrivilegedAction amd PrivilegedExceptionAction to be singletons and ensure correct use of Void return type where appropriate. Key: AS7-6316 URL: https://issues.jboss.org/browse/AS7-6316 Project: Application Server 7 Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 7.2.0.Alpha1 -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3714) Add capability to configure date-effective/date-expires for SpreadSheet (XLS/CSV)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3714?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated JBRULES-3714: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=894222 > Add capability to configure date-effective/date-expires for SpreadSheet (XLS/CSV) > --------------------------------------------------------------------------------- > > Key: JBRULES-3714 > URL: https://issues.jboss.org/browse/JBRULES-3714 > Project: JBRULES > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools-decisiontables > Affects Versions: 5.5.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mark Proctor > > Currently users cannot configure date-effective/date-expires for rules when they use SpreadSheet. (It's possible in case of Guided Decision Table Editor) > The request is being able to specify date-effective/date-expires like other attributes ( http://docs.jboss.org/drools/release/5.5.0.Final/drools-expert-docs/html_... "Table 2.2. Rule attribute entries in the Rule Set area" ) -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3714) Add capability to configure date-effective/date-expires for SpreadSheet (XLS/CSV)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3714?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on JBRULES-3714: -------------------------------------------------- Toshiya Kobayashi <tkobayas(a)redhat.com> made a comment on [bug 894222|https://bugzilla.redhat.com/show_bug.cgi?id=894222] Platform BZ for https://issues.jboss.org/browse/JBRULES-3714 Currently users cannot configure date-effective/date-expires for rules when they use SpreadSheet. (It's possible in case of Guided Decision Table Editor) The request is being able to specify date-effective/date-expires like other attributes ( http://docs.jboss.org/drools/release/5.5.0.Final/drools-expert-docs/html_... "Table 2.2. Rule attribute entries in the Rule Set area" ) > Add capability to configure date-effective/date-expires for SpreadSheet (XLS/CSV) > --------------------------------------------------------------------------------- > > Key: JBRULES-3714 > URL: https://issues.jboss.org/browse/JBRULES-3714 > Project: JBRULES > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools-decisiontables > Affects Versions: 5.5.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mark Proctor > > Currently users cannot configure date-effective/date-expires for rules when they use SpreadSheet. (It's possible in case of Guided Decision Table Editor) > The request is being able to specify date-effective/date-expires like other attributes ( http://docs.jboss.org/drools/release/5.5.0.Final/drools-expert-docs/html_... "Table 2.2. Rule attribute entries in the Rule Set area" ) -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3714) Add capability to configure date-effective/date-expires for SpreadSheet (XLS/CSV)

by Toshiya Kobayashi (JIRA)

Toshiya Kobayashi created JBRULES-3714: ------------------------------------------ Summary: Add capability to configure date-effective/date-expires for SpreadSheet (XLS/CSV) Key: JBRULES-3714 URL: https://issues.jboss.org/browse/JBRULES-3714 Project: JBRULES Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 5.5.0.Final Reporter: Toshiya Kobayashi Assignee: Mark Proctor Currently users cannot configure date-effective/date-expires for rules when they use SpreadSheet. (It's possible in case of Guided Decision Table Editor) The request is being able to specify date-effective/date-expires like other attributes ( http://docs.jboss.org/drools/release/5.5.0.Final/drools-expert-docs/html_... "Table 2.2. Rule attribute entries in the Rule Set area" ) -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6296) Remove log manager configuration implementations

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/AS7-6296?page=com.atlassian.jira.plugin.s... ] James Perkins commented on AS7-6296: ------------------------------------ Work complete, awaiting PR for AS7-6182 > Remove log manager configuration implementations > ------------------------------------------------ > > Key: AS7-6296 > URL: https://issues.jboss.org/browse/AS7-6296 > Project: Application Server 7 > Issue Type: Task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 7.2.0.Alpha1 > > > After log-manager is updated, remove the logmanager configuration implementations and update the log4j appenders to use the new POJO configuration type. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6307) Ensure loggers get created on the correct LogContext

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/AS7-6307?page=com.atlassian.jira.plugin.s... ] James Perkins commented on AS7-6307: ------------------------------------ Work complete, awaiting PR for AS7-6182 > Ensure loggers get created on the correct LogContext > ---------------------------------------------------- > > Key: AS7-6307 > URL: https://issues.jboss.org/browse/AS7-6307 > Project: Application Server 7 > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 7.2.0.Alpha1 > > > Using the {{ContextClassLoaderLogContextSelector}} causes static loggers loaded from libraries that set the TCCL to a deployments class loader get configured with the incorrect log context. > <dmlloyd> each Class object is examined for its class loader > <dmlloyd> we keep a set of our logging API class loaders > <dmlloyd> we iterate until we find a Class which isn't in one of our known modules > <dmlloyd> then we use that Class's class loader to select the log context -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-5255) Deployed log4j.properties does not affect non log4j logging systems

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/AS7-5255?page=com.atlassian.jira.plugin.s... ] James Perkins commented on AS7-5255: ------------------------------------ Work complete, awaiting PR for AS7-6182. > Deployed log4j.properties does not affect non log4j logging systems > ------------------------------------------------------------------- > > Key: AS7-5255 > URL: https://issues.jboss.org/browse/AS7-5255 > Project: Application Server 7 > Issue Type: Bug > Components: Logging > Affects Versions: 7.1.2.Final (EAP) > Reporter: Patrick Ruckstuhl > Assignee: James Perkins > Priority: Blocker > Fix For: 7.2.0.Alpha1 > > > If I create the file > my.ear/META-INF/log4j.properties > with > log4j.rootLogger=DEBUG, FA > log4j.appender.FA=org.apache.log4j.FileAppender > log4j.appender.FA.File=/tmp/my.log > log4j.appender.FA.layout=org.apache.log4j.PatternLayout > log4j.appender.FA.layout.ConversionPattern= %-4r [%t] %-5p %c %x - %m%n > this results in nothing in the server.log and an empty /tmp/my.log > but if I create a > my.ear/META-INF/logging.properties > this results in everything beeing logged to /tmp/my.log > We're using SLF4J in our application and also using a library that uses COMMONS-LOGGING > I also did a test with doing an additional log statement using the log4j api directly and this one (and only this one) did get logged to /tmp/my.log -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-32) Overriding the deployment name overrides the web-context

by James Perkins (JIRA)

James Perkins created JBASMP-32: ----------------------------------- Summary: Overriding the deployment name overrides the web-context Key: JBASMP-32 URL: https://issues.jboss.org/browse/JBASMP-32 Project: JBoss AS Maven Plugins Issue Type: Bug Reporter: James Perkins Assignee: James Perkins http://stackoverflow.com/questions/14241493/jboss-7-deployment-issues-wit... -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6315) Allow expressions in jaxr subsystem

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6315: ------------------------------------- Summary: Allow expressions in jaxr subsystem Key: AS7-6315 URL: https://issues.jboss.org/browse/AS7-6315 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, JAXR Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 The jndi-name attribute. -- 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

13 years, 6 months

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 January 2013