November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCOMMON-63) JDK to Log4j/JBoss logging handler

by Galder Zamarreno (JIRA)

JDK to Log4j/JBoss logging handler ---------------------------------- Key: JBCOMMON-63 URL: https://jira.jboss.org/jira/browse/JBCOMMON-63 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common-logging-jdk, common-logging-log4j Reporter: Galder Zamarreno Attachments: logging-jbcommon.zip Certain 3rd party libraries log using JDK logging and customers want to see these applications logging to where JBoss logs. We should provide a JDK logging handler than logs using log4j or JBoss logging API. Please find attached a handler I created to log to log4j. Creating a handler for log4j was easier than creating one for JBoss logging because of the presence of Logger.log(Level, String...) API in log4j. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCOMMON-50) TimedCachePolicy leaks classloader to timer thread

by Brian Stansberry (JIRA)

TimedCachePolicy leaks classloader to timer thread -------------------------------------------------- Key: JBCOMMON-50 URL: http://jira.jboss.com/jira/browse/JBCOMMON-50 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core Affects Versions: 2.2.5.beta1, 2.2.4.GA Reporter: Brian Stansberry TimedCachePolicy has a static reference to a Timer, restartTimer. A timer creates a new thread when it is initialized; the thread inherits its TCCL from the TCCL of the thread that initializes it. Effect is that TCCL leaks to the restartTimer's thread. Not sure the best solution here, since common-core is a general use library. In general I think the right solution is to set the TCCL to a "safe" classloader before creating the Timer, and restore the TCCL afterwards. But what is a "safe" classloader? If you use TimedCachePolicy.class.getClassLoader(), then that classloader is leaked. That's fine in JBoss AS, but may be bad in other use cases. Perhaps null or system classloader is the right choice; I don't know enough about how this class is used to have a good idea if the TimerTasks being used (seems to only be RestartTimer) need to load classes. -- 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

15 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JASSIST-62) make $type available in insertBefore

by Yanic Inghelbrecht (JIRA)

make $type available in insertBefore ------------------------------------ Key: JASSIST-62 URL: http://jira.jboss.com/jira/browse/JASSIST-62 Project: Javassist Issue Type: Feature Request Environment: javassist 3.7.1 (latest from cvs HEAD) Reporter: Yanic Inghelbrecht Assigned To: Shigeru Chiba The tutorial explicitly mentions that $type is not available in CtMethod#insertBefore, which is why I did not file this as a bug. The problem is that it is impossible to determine the return type without support from javassist, since there can be multiple methods in the same class with the same name and parameter types but different return types (because of bridge methods to support covariant return types). The return type is to distinguish between the bridge methods and the originals. Again, this is for a tool that performs run-time analysis of execution events, so it is important it can accurately distinguish between method(calls). Currently the tool lumps together the originals and bridges for lack of information, which is incorrect. So for me this is a high priority bug / rfe. A quick response as to whether or not this request is deemed feasible would be appreciated - even if the implementation will take a while. Thanks in advance. Best regards, Yanic -- 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

15 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1632) DSL expander can't add a field constraint to a fact when a previous field constraint has parentheses

by Pierre De Swert (JIRA)

DSL expander can't add a field constraint to a fact when a previous field constraint has parentheses ---------------------------------------------------------------------------------------------------- Key: JBRULES-1632 URL: http://jira.jboss.com/jira/browse/JBRULES-1632 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.7 Reporter: Pierre De Swert Assigned To: Mark Proctor I have made a little example to reproduce the problem. Let us assume we have a very simple Wine class... public class Wine { private int age; private String type; private String country; private String vineyard; .... I define the following in my DSL: [condition][]Il existe un vin "{i}"={i} : Wine() [condition][]- plus vieux que "{y}"=age > {y} [condition][]- du crû "{c}"=vineyard == "{c}" In the following rule, I can't add the last field constraint when the age of the prvious one is "($y + 10)" rule "Very Old Wine" when #conditions # there is a wine 10 years older than a person > Person($y : age) Il existe un vin "$v" - plus vieux que "($y + 10)" # - plus vieux que "$y" - du crû "Nuits-Saint-Georges" then #actions End -- 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

15 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1222) Problem with DSL and espace caracters "\"

by Delbart Vincent (JIRA)

Problem with DSL and espace caracters "\" ----------------------------------------- Key: JBRULES-1222 URL: http://jira.jboss.com/jira/browse/JBRULES-1222 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.1 Reporter: Delbart Vincent Assigned To: Mark Proctor Priority: Minor Hi, In the DSL writting it's possible to use : "+", "." ... caracters with escape caracters "\" But in the completion list of the rules editor and in the DSLMapping class the "\" stay : http://www.nabble.com/file/p12874031/escapeCaracters.jpg thks, V. -- 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

15 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1192) a typo in a dslr file does not always show up an error marker

by Michael Neale (JIRA)

a typo in a dslr file does not always show up an error marker ------------------------------------------------------------- Key: JBRULES-1192 URL: http://jira.jboss.com/jira/browse/JBRULES-1192 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.1 Reporter: Michael Neale Assigned To: Kris Verlaenen Open the examples, go to TroubleTicketWithDSL.dslr then make some type of the RHS of the rule. the file will get marked as having an error, but not the rule which caused 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

15 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1186) Adding 'OR' constraints to fact's properties in DSL

by Andy Mei (JIRA)

Adding 'OR' constraints to fact's properties in DSL --------------------------------------------------- Key: JBRULES-1186 URL: http://jira.jboss.com/jira/browse/JBRULES-1186 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.1 Environment: All OS platform Reporter: Andy Mei Assigned To: Mark Proctor Priority: Critical I would like to write something like this : There is a Cheese with ( - age is less than 42 or - age is more than 60 ) - type is 'stilton' Unfortunately, It's the drools parser which manage "-" char. Also this previous synthax don't work in the LHS. Anyone could help me to do an equivalent condition in my DSL ? If possible with "-" sugar char. -- 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

15 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-6013) Support createDestination in jboss/message-driven

by Adrian Brock (JIRA)

Support createDestination in jboss/message-driven ------------------------------------------------- Key: JBAS-6013 URL: https://jira.jboss.org/jira/browse/JBAS-6013 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB2, EJB3 Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-5.0.0.GA In the old JMSContainerInvoker there was a flag called "createJBossMQDestination" which allowed the MDB to automatically create the JMS destination. This has is no longer supported with the reworking of the metadata and changes to the MDB container. To re-introduce this behaviour and resolve some of the issues we had with this feature (which lead to it being disabled by default), the behaviour should be made pluggable via a deployer instead. Issues this will resolve over the previous implementation: 1) The Destination will be removed at undeployment 2) The Destination construction method can be replaced by switiching the deployer, e.g. for different backend jms servers including understanding rar specific activation config properties 3) The behaviour is not necessarily JMS specific, e.g. other inbound adapters could create their own destinations The legacy "createJBossMQDestination" will still be checked when it exists. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBCOMMON-37) Add jboss-common 1.2.1.GA to the JBoss maven repository

by Anders Hammar (JIRA)

Add jboss-common 1.2.1.GA to the JBoss maven repository ------------------------------------------------------- Key: JBCOMMON-37 URL: http://jira.jboss.com/jira/browse/JBCOMMON-37 Project: JBoss Common Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.2.1.GA Environment: n/a Reporter: Anders Hammar Assigned To: Dimitris Andreadis I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. I'm For the transitive dependency to work, the jboss-common artifact is needed. Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing. -- 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

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-383) Complete Retro Mavenization

by Paul Gier (JIRA)

Complete Retro Mavenization --------------------------- Key: JBBUILD-383 URL: http://jira.jboss.com/jira/browse/JBBUILD-383 Project: JBoss Build System Issue Type: Feature Request Components: JBossRetro Reporter: Paul Gier Fix For: JBossRetro-1.1.1.GA The mavenization can be completed when the next surefire plugin is released. Also there needs to be a way to configure the manifest file for the runtime jar. Look into breaking retro into three modules: weaver, retro-runtime, and maven-plugin. -- 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

15 years, 9 months

1
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008