March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBLOGGING-90) Update slf4j-jboss-logging to use slf4j 1.7.2

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-90?page=com.atlassian.jira.plug... ] James Perkins commented on JBLOGGING-90: ---------------------------------------- Pull request sent: https://github.com/jboss-logging/slf4j-jboss-logging/pull/3 > Update slf4j-jboss-logging to use slf4j 1.7.2 > --------------------------------------------- > > Key: JBLOGGING-90 > URL: https://issues.jboss.org/browse/JBLOGGING-90 > Project: JBoss Logging > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > -- 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-6666) Custom log handler properties should support expressions

by Oliver Bock (JIRA)

[ https://issues.jboss.org/browse/AS7-6666?page=com.atlassian.jira.plugin.s... ] Oliver Bock commented on AS7-6666: ---------------------------------- Great! Thanks > Custom log handler properties should support expressions > -------------------------------------------------------- > > Key: AS7-6666 > URL: https://issues.jboss.org/browse/AS7-6666 > Project: Application Server 7 > Issue Type: Enhancement > Components: Logging > Affects Versions: 7.1.1.Final > Reporter: Oliver Bock > Assignee: James Perkins > Priority: Minor > > The configuration of a custom-handler for the logging subsystem in standalone.xml doesn't support expressions in the value attribute of its properties/property elements. Those would be very useful, e.g. for OpenShift. > Example ([...] denote omissions for clarity): > {noformat} > <custom-handler [...]> > [...] > <properties> > <property name="myProp" value="${env.MY_PROP_VALUE}"/> > </properties> > </custom-handler> > {noformat} > TIA -- 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] (JBLOGGING-91) getMessages and getLogger need to be privileged

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-91?page=com.atlassian.jira.plug... ] David Lloyd resolved JBLOGGING-91. ---------------------------------- Fix Version/s: (was: 3.0.2.GA) Resolution: Done > getMessages and getLogger need to be privileged > ----------------------------------------------- > > Key: JBLOGGING-91 > URL: https://issues.jboss.org/browse/JBLOGGING-91 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 3.1.3.GA, 3.2.0.Beta1 > > > They perform actions like getClassLoader() and member access that may require privileges. -- 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] (JBLOGGING-91) getMessages and getLogger need to be privileged

by David Lloyd (JIRA)

David Lloyd created JBLOGGING-91: ------------------------------------ Summary: getMessages and getLogger need to be privileged Key: JBLOGGING-91 URL: https://issues.jboss.org/browse/JBLOGGING-91 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.2.GA, 3.1.3.GA, 3.2.0.Beta1 They perform actions like getClassLoader() and member access that may require privileges. -- 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] (JBEE-129) Common Annotations for the JavaTM Platform 1.2 (JSR-250)

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/JBEE-129?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger resolved JBEE-129. ---------------------------------- Resolution: Done Actually this seems to have been done already at https://github.com/jboss/jboss-annotations-api_spec Sorry! > Common Annotations for the JavaTM Platform 1.2 (JSR-250) > -------------------------------------------------------- > > Key: JBEE-129 > URL: https://issues.jboss.org/browse/JBEE-129 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-javaee-specs > Reporter: Jozef Hartinger > Assignee: Shelly McGowan > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > http://jcp.org/aboutJava/communityprocess/maintenance/jsr250/jsr250change... -- 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] (DROOLS-65) Local Cache is not updated, case client is started before the server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-65?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on DROOLS-65: ----------------------------------------------- Alessandro Lazarotti <alazarot(a)redhat.com> made a comment on [bug 917787|https://bugzilla.redhat.com/show_bug.cgi?id=917787] Pull Request: https://github.com/droolsjbpm/drools/pull/181 > Local Cache is not updated, case client is started before the server > -------------------------------------------------------------------- > > Key: DROOLS-65 > URL: https://issues.jboss.org/browse/DROOLS-65 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: BRMS 5.3.1 > Reporter: Alessandro Lazarotti > Assignee: Mark Proctor > > Local Cache is not updated, case client is started before the server > 1. Start Guvnor > 2. Any regular client application consumes some package with local cache configured (drools.resource.urlcache) > 3. Stop client and server > 4. Restart the client (it will work consuming data from loca cache) > 5. Restart the server and changes a rule from the package used by client application > 6. BUild the package > 7. Local cache still consume the package from the local cache which is never synchronized with the server > It works as expected case only the server is restarted or if server starts before the client. -- 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] (DROOLS-65) Local Cache is not updated, case client is started before the server

by Alessandro Lazarotti (JIRA)

[ https://issues.jboss.org/browse/DROOLS-65?page=com.atlassian.jira.plugin.... ] Alessandro Lazarotti updated DROOLS-65: --------------------------------------- Git Pull Request: https://github.com/droolsjbpm/drools/pull/181 > Local Cache is not updated, case client is started before the server > -------------------------------------------------------------------- > > Key: DROOLS-65 > URL: https://issues.jboss.org/browse/DROOLS-65 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: BRMS 5.3.1 > Reporter: Alessandro Lazarotti > Assignee: Mark Proctor > > Local Cache is not updated, case client is started before the server > 1. Start Guvnor > 2. Any regular client application consumes some package with local cache configured (drools.resource.urlcache) > 3. Stop client and server > 4. Restart the client (it will work consuming data from loca cache) > 5. Restart the server and changes a rule from the package used by client application > 6. BUild the package > 7. Local cache still consume the package from the local cache which is never synchronized with the server > It works as expected case only the server is restarted or if server starts before the client. -- 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] (JBEE-129) Common Annotations for the JavaTM Platform 1.2 (JSR-250)

by Jozef Hartinger (JIRA)

Jozef Hartinger created JBEE-129: ------------------------------------ Summary: Common Annotations for the JavaTM Platform 1.2 (JSR-250) Key: JBEE-129 URL: https://issues.jboss.org/browse/JBEE-129 Project: JBoss JavaEE Spec APIs Issue Type: Sub-task Reporter: Jozef Hartinger Assignee: Shelly McGowan Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 http://jcp.org/aboutJava/communityprocess/maintenance/jsr250/jsr250change... -- 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] (DROOLS-65) Local Cache is not updated, case client is started before the server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-65?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated DROOLS-65: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=917787 > Local Cache is not updated, case client is started before the server > -------------------------------------------------------------------- > > Key: DROOLS-65 > URL: https://issues.jboss.org/browse/DROOLS-65 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: BRMS 5.3.1 > Reporter: Alessandro Lazarotti > Assignee: Mark Proctor > > Local Cache is not updated, case client is started before the server > 1. Start Guvnor > 2. Any regular client application consumes some package with local cache configured (drools.resource.urlcache) > 3. Stop client and server > 4. Restart the client (it will work consuming data from loca cache) > 5. Restart the server and changes a rule from the package used by client application > 6. BUild the package > 7. Local cache still consume the package from the local cache which is never synchronized with the server > It works as expected case only the server is restarted or if server starts before the client. -- 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] (DROOLS-65) Local Cache is not updated, case client is started before the server

by Alessandro Lazarotti (JIRA)

Alessandro Lazarotti created DROOLS-65: ------------------------------------------ Summary: Local Cache is not updated, case client is started before the server Key: DROOLS-65 URL: https://issues.jboss.org/browse/DROOLS-65 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Environment: BRMS 5.3.1 Reporter: Alessandro Lazarotti Assignee: Mark Proctor Local Cache is not updated, case client is started before the server 1. Start Guvnor 2. Any regular client application consumes some package with local cache configured (drools.resource.urlcache) 3. Stop client and server 4. Restart the client (it will work consuming data from loca cache) 5. Restart the server and changes a rule from the package used by client application 6. BUild the package 7. Local cache still consume the package from the local cache which is never synchronized with the server It works as expected case only the server is restarted or if server starts before the client. -- 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 March 2013