January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-827) creating timers inside start() creates duplicate timers.

by David Owens (JIRA)

creating timers inside start() creates duplicate timers. -------------------------------------------------------- Key: EJBTHREE-827 URL: http://jira.jboss.com/jira/browse/EJBTHREE-827 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: Windows 2000, JBoss 4.0.5 (jems installer), Java 1.5 Reporter: David Owens Calling ctx.getTimerService().createTimer(...) within the start() method of a managed service bean creates duplicate timers. In other words, I have a bean which is both @Management and @Service which has a method which is @Timeout. In the start method of the bean (when the bean is deployed) I create a new timer. But then the method marked @Timeout is called twice. When I investigate the timers in by calling ctx.getTimerService().getTimers(), I find there are actually 2 timers with different ids, but with the exact same info. I have attached an example. You will see the start() method getting called once when the bean is deployed, but then the timeout method getting called twice. -- 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

18 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-944) Version compabitlity matrix for jboss aop and javassist version in PojoCache

by Ben Wang (JIRA)

Version compabitlity matrix for jboss aop and javassist version in PojoCache ---------------------------------------------------------------------------- Key: JBCACHE-944 URL: http://jira.jboss.com/jira/browse/JBCACHE-944 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0.GA This has come up in different places that jboss aop and javassist versions are not compabitliy between jboss as and jbc release. I have request ed Kabir to make sure it will be in the future. -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4000) <endpoint-interceptors> should come before <activation-config> in standardjboss.xml

by Galder Zamarreno (JIRA)

<endpoint-interceptors> should come before <activation-config> in standardjboss.xml ----------------------------------------------------------------------------------- Key: JBAS-4000 URL: http://jira.jboss.com/jira/browse/JBAS-4000 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno As per jboss_4_0.dtd, standardjboss.xml descriptor should be modified so that tag <endpoint-interceptors> comes before <activation-config>. -- 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

18 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-126) ProxyMapCreator does not handle default annotation values

by Adrian Brock (JIRA)

ProxyMapCreator does not handle default annotation values --------------------------------------------------------- Key: JBMICROCONT-126 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-126 Project: JBoss MicroContainer Issue Type: Task Components: General Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Assigned To: Kabir Khan There is a fixme in ProxyMapCreator that says "//TODO: Need to handle default values for annotations in jdk 1.5" -- 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

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-124) Fixme in test org.jboss.test.classinfo.support.AnnotatedSubClass

by Adrian Brock (JIRA)

Fixme in test org.jboss.test.classinfo.support.AnnotatedSubClass ---------------------------------------------------------------- Key: JBMICROCONT-124 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-124 Project: JBoss MicroContainer Issue Type: Task Components: General Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Assigned To: Kabir Khan Priority: Minor There is a FIXME in the above class. Kabir can you update this task to describe the problem. -- 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

18 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-109) Support direct registration of beans without a StandardMBean wrapper

by Brian Stansberry (JIRA)

Support direct registration of beans without a StandardMBean wrapper -------------------------------------------------------------------- Key: JBMICROCONT-109 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-109 Project: JBoss MicroContainer Issue Type: Sub-task Components: General Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossMC_2_0_0 Beta If a bean is already a valid MBean, it should be possible to directly register it in JMX without wrapping it in a StandardMBean. Otherwise beans that implement things like MBeanRegistration, NotificationBroadcaster, NotificationEmitter will not expose that API to the mbean server. To support this, @JMX will add an attribute: boolean registerDirectly() default false; JMXIntroduction will check the attribute; if true the target bean will be registered directly; otherwise a StandardMBean will be created and registered. -- 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

18 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-379) function with another drools function call won't compile (either with eclipse compiler or janino)

by Thierry R (JIRA)

function with another drools function call won't compile (either with eclipse compiler or janino) ------------------------------------------------------------------------------------------------- Key: JBRULES-379 URL: http://jira.jboss.com/jira/browse/JBRULES-379 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.1 Environment: Debian linux JDK 5 Reporter: Thierry R Assigned To: Mark Proctor function with another drools function call won't compile (either with eclipse compiler or janino) with the error msg : "Function Compilation error " I wrote a DroolsHelper class to work around. -- 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

18 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1091) CMS UI : order : for lists of languages, folders, files names

by Antoine Herzog (JIRA)

CMS UI : order : for lists of languages, folders, files names ------------------------------------------------------------- Key: JBPORTAL-1091 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1091 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Environment: JBoss Portal 2.4, WXP, CMS repository in filesystem, Reporter: Antoine Herzog Assigned To: Roy Russo Priority: Minor In the CMS UI, the ordering of the folders and the files names is "Date of creation". Wish : the ordering by names (more convenient to work). even better : feature to choose the ordering on name, dates, description (second priority). In the list of languages, when you use it with another user language than english, the list is in a very messy order : I guess it is the order of the languages names in english, but showed in the "other language". example : "english" is written "anglais" and can be found after "grec" (greek) and before "esperanto". solution : order the list with the i18n label of each items. even better : propose in top of list the few languages that are supported by the portal. propose a one (or a few) strategie(s) of ordering. -- 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

18 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-549) Better support for linebreaks in LHS

by Dirk Bergstrom (JIRA)

Better support for linebreaks in LHS ------------------------------------ Key: JBRULES-549 URL: http://jira.jboss.com/jira/browse/JBRULES-549 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Dirk Bergstrom Assigned To: Mark Proctor I have some rules with very long LHS expressions. I'd like to split them across multiple lines for readability. However, the parser has limited support for breaks. These work: when ObjectTypeName( p0_exit_epoch > (RUM.now()), p0_exit_epoch > (RUM.daysAgo(7)) ) variable : OtherObjectType($rlis : rlis -> (RUM.countFieldsMatching($rlis, "state", "dev-maybe") > 0)) These don't: variable : OtherObjectType($rlis : rlis -> (RUM.countFieldsMatching($rlis, "state", "dev-maybe") > 0)) variable : OtherObjectType(($rlis : rlis -> (RUM.countFieldsMatching($rlis, "state", "dev-maybe") > 0)) variable : OtherObjectType($rlis : rlis -> (RUM.countFieldsMatching($rlis, "state", "dev-maybe") > 0)) While I'm at it, I'd love to have support for multiline expressions in DSL files, but I can imagine that would be a bit harder... -- 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

18 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-589) WokingMemoryLogger and generics: ClassCastException

by Francesco Dandrea (JIRA)

WokingMemoryLogger and generics: ClassCastException --------------------------------------------------- Key: JBRULES-589 URL: http://jira.jboss.com/jira/browse/JBRULES-589 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.5 Environment: Java 1.5.0_9 Reporter: Francesco Dandrea Assigned To: Mark Proctor Attachments: BacoJBossRules.zip I'm using Jboss Rules 3.0.5 and Java 1.5.0_09. I'm using generics, but I see that I can't have the character < in a Fact in te drl. This is not a problem, I derived my generic class, and the new derived one is not a Generic class... (public class MyClassCiccio extends Ciccio<MyClass>{}) Now, when I execute the application without log it works. But when I instantiate a WorkingMemoryLogger I have a ClassCastException: Exception in thread "main" java.lang.ClassCastException: it.telecomitalia.netbox.MeasureAlarm at org.drools.base.it.telecomitalia.netbox.TfAlarm$getReferencedElement.getValue(Unknown Source) at org.drools.base.ClassFieldExtractor.getValue(Unknown Source) at org.drools.rule.Declaration.getValue(Unknown Source) at org.drools.audit.WorkingMemoryLogger.extractDeclarations(Unknown Source) at org.drools.audit.WorkingMemoryLogger.activationCreated(Unknown Source) at org.drools.event.AgendaEventSupport.fireActivationCreated(Unknown Source) at org.drools.reteoo.TerminalNode.assertTuple(Unknown Source) at org.drools.reteoo.TerminalNode.assertTuple(Unknown Source) at org.drools.reteoo.TupleSource.propagateAssertTuple(Unknown Source) at org.drools.reteoo.NotNode.assertTuple(Unknown Source) at org.drools.reteoo.LeftInputAdapterNode.createAndAssertTuple(Unknown Source) at org.drools.reteoo.LeftInputAdapterNode.assertObject(Unknown Source) at org.drools.reteoo.ObjectSource.propagateAssertObject(Unknown Source) at org.drools.reteoo.ObjectTypeNode.assertObject(Unknown Source) at org.drools.reteoo.Rete.assertObject(Unknown Source) at org.drools.reteoo.ReteooRuleBase.assertObject(Unknown Source) at org.drools.reteoo.ReteooWorkingMemory.doAssertObject(Unknown Source) at org.drools.common.AbstractWorkingMemory.assertObject(Unknown Source) at org.drools.common.AbstractWorkingMemory.assertObject(Unknown Source) at it.telecomitalia.netbox.Main.main(Main.java:34) I have an example (sent to the mailing list) that gives the exception, but -- 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

18 years, 10 months

2
3
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 2007