July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-1313) RepositorySelector should be integrated into JBoss Server

by Amit Bhayani (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1313?page=comments#action_12420034 ] Amit Bhayani commented on JBAS-1313: ------------------------------------ Attached log4j-rs-withTimerTask.zip is a modified version of Log4jRepositorySelector where the deployed log4j.xml/log4j.properties files are continuously monitored for any modification and if modifications are found the log file is re created with new configuration. > RepositorySelector should be integrated into JBoss Server > --------------------------------------------------------- > > Key: JBAS-1313 > URL: http://jira.jboss.com/jira/browse/JBAS-1313 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Stan Silvert > Assigned To: Stan Silvert > Priority: Minor > Fix For: JBossAS-5.0.1.CR1 > > Attachments: log4-rs.zip, log4j-rs-withTimerTask.zip, log4j-test.sar, TestingLog4j.zip > > > Often, an application will want to have its own log4j configuration and have all log messages generated go to an application-specific log file. Solutions to this problem are documented on this wiki page: http://www.jboss.org/wiki/Wiki.jsp?page=Logging > The log4j RepositorySelector provides a clean solution to this problem without any special classloader settings. However, at the present time, a developer must create his own version of a RepositorySelector and make sure his application initializes it properly. > This can be difficult to accomplish because the RepositorySelector feature is not well known and takes time to understand. It can also be difficult to make sure that the RepositorySelector is initialized before the application makes ANY call to Logger.getLogger(). > We can instead, provide a RepositorySelector implementation as part of the JBoss Application server. If a deployer finds a log4j.xml file in the /META-INF direcotry (or /WEB-INF for WARs) it would add an entry into the RepositorySelector for that application. Then, logging from that application would use the custom log4j configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1668) Smooks Data Loader

by Mark Proctor (JIRA)

Smooks Data Loader ------------------ Key: JBRULES-1668 URL: http://jira.jboss.com/jira/browse/JBRULES-1668 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 5.0.0.M2 Create a project to allow smooks to insert filtered data into the session, making sure smooks is aware of internal drools models. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1667) Internal Models are not being resolved from the RuleBase CompositeClassLoader

by Mark Proctor (JIRA)

Internal Models are not being resolved from the RuleBase CompositeClassLoader ----------------------------------------------------------------------------- Key: JBRULES-1667 URL: http://jira.jboss.com/jira/browse/JBRULES-1667 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 5.0.0.M2 The classloader on the rulebase is not able to resolve internal models. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-720) Clips Parser

by Mark Proctor (JIRA)

Clips Parser ------------ Key: JBRULES-720 URL: http://jira.jboss.com/jira/browse/JBRULES-720 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m2 Clips Parser -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
4
0 / 0

[JBoss JIRA] Updated: (JBAS-1832) Improving JBoss WebConsole's snapshots

by gunter zeilinger (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1832?page=all ] gunter zeilinger updated JBAS-1832: ----------------------------------- Attachment: jboss-4.2.2.GA-bin-patch.zip jboss-4.2.2.GA-src-patch.zip jboss-4.2.2.GA-src-patch.diff Attached patch for JBossAS-4.2.2.GA additionally add support to JBoss Web Console to persist created snapshots. To apply on binary JBossAS-4.2.2.GA distribution > unzip jboss-4.2.2.GA-bin-patch.zip in your server configuration directory (e.g: jboss-4.2.2.GA/server/default ). jboss-4.2.2.GA-src-patch.zip contains the modified and added sources, jboss-4.2.2.GA-src-patch.diff the diff against http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_2_2_GA. > Improving JBoss WebConsole's snapshots > -------------------------------------- > > Key: JBAS-1832 > URL: http://jira.jboss.com/jira/browse/JBAS-1832 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX/Web Console > Affects Versions: JBossAS-4.0.0 Final > Environment: Not relevant > Reporter: Mathieu Bourrier > Assigned To: Jon Prindiville > Priority: Minor > Attachments: jboss-4.2.2.GA-bin-patch.zip, jboss-4.2.2.GA-src-patch.diff, jboss-4.2.2.GA-src-patch.zip > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The snapshots in the Webconsole cannot be started automatically on startup, as the Recording field isn't an attribute. > 2 classes need to be modified, and the changes are quite small. > Given topic describes changes to be made in order to manage it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCOMMON-59) Add Atomic property editors

by Ales Justin (JIRA)

Add Atomic property editors --------------------------- Key: JBCOMMON-59 URL: http://jira.jboss.com/jira/browse/JBCOMMON-59 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.7.GA Reporter: Ales Justin Assigned To: Ales Justin Priority: Minor Fix For: 2.2.8.GA Add property editor for Atomic(Integer|Long|Boolean). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1957) Upgrade jBPM to the latest version of the 3.2.x branch

by Martin Putz (JIRA)

Upgrade jBPM to the latest version of the 3.2.x branch ------------------------------------------------------ Key: JBPORTAL-1957 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1957 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Workflow Reporter: Martin Putz Requests have come in to upgrade jBPM from the currently used 3.1.4 version to the latest version of the 3.2 branch. Main reasons: - advanced feature set - ability to deploy the jbpm-console of the 3.2 branch along with JBoss Portal in order to inspect the running processes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBREFLECT-28) Add synchronzation code to NumberInfo

by Ales Justin (JIRA)

Add synchronzation code to NumberInfo ------------------------------------- Key: JBREFLECT-28 URL: http://jira.jboss.com/jira/browse/JBREFLECT-28 Project: JBoss Reflection Issue Type: Task Components: ClassInfo Affects Versions: JBossReflection.2.0.0.Beta12 Reporter: Ales Justin Assigned To: Ales Justin Priority: Minor Fix For: JBossReflection.2.0.0.CR1 Synchronize on delegate write/read in NumberInfo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5719) Deployment ordering of WAR and -ds.xml not working in JBoss-5.0 CR1

by jaikiran pai (JIRA)

Deployment ordering of WAR and -ds.xml not working in JBoss-5.0 CR1 ------------------------------------------------------------------- Key: JBAS-5719 URL: http://jira.jboss.com/jira/browse/JBAS-5719 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Environment: JBoss-5.0 CR1 Windows 2003 Server Sun Java 1.5 Reporter: jaikiran pai Assigned To: Ales Justin If the server is started with a WAR and a -ds.xml file in the deploy folder, then WAR is deployed first instead of the -ds.xml. This results in the WAR deployment failing, if the WAR is dependent on the datasource to be available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-794) FD_SOCK: un-suspected members are not added back to pingable_mbrs

by Bela Ban (JIRA)

FD_SOCK: un-suspected members are not added back to pingable_mbrs ----------------------------------------------------------------- Key: JGRP-794 URL: http://jira.jboss.com/jira/browse/JGRP-794 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.4, 2.7 [Bruce Schuchardt] I had a test run where a member was suspected by FD_SOCK, but replied to an ARE_YOU_DEAD message. The process was then immediately killed by the test but was never suspected again. FD_SOCK.run() removes suspected members from pingable_mbrs so they won't be ping targets. When a member is unsuspected, it needs to be put back in pingable_mbrs in the correct place and the pinger thread needs to be started or interrupted. Otherwise no-one will be watching the unsuspected member until the next view change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

2
5
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 July 2008