January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-747) Add configuration type of "normal" or "default" to the gpd action handler configuration dialog

by Sam Healy (JIRA)

Add configuration type of "normal" or "default" to the gpd action handler configuration dialog ---------------------------------------------------------------------------------------------- Key: JBPM-747 URL: http://jira.jboss.com/jira/browse/JBPM-747 Project: JBoss jBPM Issue Type: Feature Request Components: Graphical Process Designer Affects Versions: jBPM 3.1.2 Environment: Win XP Pro, Eclipse 3.1.2 Reporter: Sam Healy Assigned To: Tom Baeyens When configuring action handlers on nodes using the gpd, no option is provided in the configuration window to use a configuration type of "default" or "normal" where a simple instantiation of the action class would suffice. As it is now, the implication is that an action class of this nature cannot be used. -- 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

19 years, 3 months

3
2
0 / 0

[JBoss JIRA] Assigned: (JBAS-2957) Replace HA-JNDI AutoDiscovery with JGroups based implementation

by Jerry Gauthier (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2957?page=all ] Jerry Gauthier reassigned JBAS-2957: ------------------------------------ Assignee: Brian Stansberry (was: Jerry Gauthier) Reassigning to Brian as this issue is current unscheduled > Replace HA-JNDI AutoDiscovery with JGroups based implementation > --------------------------------------------------------------- > > Key: JBAS-2957 > URL: http://jira.jboss.com/jira/browse/JBAS-2957 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Jerry Gauthier > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-5.0.0.CR1 > > > HA-JNDI AutoDiscovery uses its own IP multicasting-based discovery mechanism. This is error-prone code and should be replaced with the well-tested JGroups framework. > See JIRA issue JBCLUSTER-43 for further details. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBCLUSTER-43) Replace HA-JNDI AutoDiscovery with JGroups

by Jerry Gauthier (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-43?page=all ] Jerry Gauthier reassigned JBCLUSTER-43: --------------------------------------- Assignee: Brian Stansberry (was: Jerry Gauthier) Reassigning to Brian as the issue is currently not scheduled. > Replace HA-JNDI AutoDiscovery with JGroups > ------------------------------------------ > > Key: JBCLUSTER-43 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-43 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Brian Stansberry > Priority: Minor > > HA_JNDI AutoDiscovery uses its own IP multicasting-based discovery mechanism. > This is error-prone code and has been the source of many bugs over time. We should replace it with the well-tested JGroups framework, which has a couple of advantages: > - well tested, works > - different discovery mechanisms are available: IP multicast, TCP, GOSSIP etc > - Consolidation of code base -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBRULES-218) Add 'forall' Conditional Element

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-218?page=all ] Edson Tirelli resolved JBRULES-218. ----------------------------------- Fix Version/s: 3.1-m1 (was: 3.1-m2) Resolution: Done And it is finally done! $ svn log -r 8874 -v ------------------------------------------------------------------------ r8874 | tirelli | 2007-01-16 17:15:09 -0300 (Tue, 16 Jan 2007) | 8 lines Changed paths: M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/DRLLexer.java M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/DRLParser.java M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/descr/DescrFactory.java A /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/lang/descr/ForallDescr.java M /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/semantics/java/RuleBuilder.java A /labs/jbossrules/trunk/drools-compiler/src/main/java/org/drools/semantics/java/builder/ForallBuilder.java M /labs/jbossrules/trunk/drools-compiler/src/main/resources/org/drools/lang/DRL.g M /labs/jbossrules/trunk/drools-compiler/src/main/resources/org/drools/semantics/java/javaInvokers.stg M /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/compiler/PackageBuilderTest.java M /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/integrationtests/IntegrationCases.java M /labs/jbossrules/trunk/drools-compiler/src/test/java/org/drools/lang/RuleParserTest.java A /labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/test_DeclarationUsage.drl A /labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/test_Forall.drl A /labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/integrationtests/test_UnbalancedTrees.drl A /labs/jbossrules/trunk/drools-compiler/src/test/resources/org/drools/lang/forall.drl M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/base/DefaultKnowledgeHelper.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/common/AgendaItem.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/common/ScheduledAgendaItem.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/QueryTerminalNode.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/ReteooBuilder.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/RuleTerminalNode.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/builder/BuildUtils.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/builder/ColumnBuilder.java A /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/builder/ForallBuilder.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/builder/ReteooRuleBuilder.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Column.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/ConditionalElement.java A /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Forall.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/LogicTransformer.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Rule.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/RuleConditionElement.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/spi/Activation.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/spi/KnowledgeHelper.java M /labs/jbossrules/trunk/drools-core/src/test/java/org/drools/reteoo/AgendaTest.java M /labs/jbossrules/trunk/drools-core/src/test/java/org/drools/reteoo/LogicalAssertionTest.java M /labs/jbossrules/trunk/drools-core/src/test/java/org/drools/reteoo/QueryTerminalNodeTest.java M /labs/jbossrules/trunk/drools-core/src/test/java/org/drools/reteoo/SchedulerTest.java M /labs/jbossrules/trunk/drools-core/src/test/java/org/drools/rule/LogicTransformerTest.java M /labs/jbossrules/trunk/drools-core/src/test/resources/correct_processTree1.dat M /labs/jbossrules/trunk/drools-core/src/test/resources/correct_transform1.dat JBRULES-218: * forall conditional element added * support to unbalanced logical branches added * test cases added ------------------------------------------------------------------------ > Add 'forall' Conditional Element > -------------------------------- > > Key: JBRULES-218 > URL: http://jira.jboss.com/jira/browse/JBRULES-218 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assigned To: Edson Tirelli > Fix For: 3.1-m1 > > > Add 'forall' Conditional Element -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3995) org.jboss.test.classloader.test.UnifiedLoaderUnitTestCase

by Dimitris Andreadis (JIRA)

org.jboss.test.classloader.test.UnifiedLoaderUnitTestCase --------------------------------------------------------- Key: JBAS-3995 URL: http://jira.jboss.com/jira/browse/JBAS-3995 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_06 Java Vendor BEA Systems, Inc. Java VM Name BEA JRockit(R) Java VM Version R26.4.0-63-63688-1.5.0_06-20060626-2259-linux-ia32 Java VM Info OS Name Linux OS Version 2.6.9-42.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 testUnpackedResources Failure state.intValue() == ServiceMBean.STARTED junit.framework.AssertionFailedError: state.intValue() == ServiceMBean.STARTED at org.jboss.test.classloader.test.UnifiedLoaderUnitTestCase.testUnpackedResources(UnifiedLoaderUnitTestCase.java:113) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) 0.124 testResource Failure state.intValue() == ServiceMBean.STARTED junit.framework.AssertionFailedError: state.intValue() == ServiceMBean.STARTED at org.jboss.test.classloader.test.UnifiedLoaderUnitTestCase.testResource(UnifiedLoaderUnitTestCase.java:93) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3473) Fix DistributedStateImpl.nodeRemove

by Brian Stansberry (JIRA)

Fix DistributedStateImpl.nodeRemove ----------------------------------- Key: JBAS-3473 URL: http://jira.jboss.com/jira/browse/JBAS-3473 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta AFAICT, this is not correct. Key/value pairs are stored in the category node's data map; nodeRemoved treats things as if each key is its own node. Actually, I think the node per key approach is correct, until TreeCacheListener can provide info on what data was changed. Also, remove() itself notifies listeners of a removal, and then the listener does as well. Needs to be one or the other; probably nodeRemoved() as that gets called for both local and remote removes. -- 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

19 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-698) gpd is not working with latest version of commons-fileupload jar.

by Olivier Debels (JIRA)

gpd is not working with latest version of commons-fileupload jar. ----------------------------------------------------------------- Key: JBPM-698 URL: http://jira.jboss.com/jira/browse/JBPM-698 Project: JBoss jBPM Issue Type: Bug Components: Graphical Process Designer Reporter: Olivier Debels Assigned To: Tom Baeyens When trying to used the graphical process designer with the latest version of commons-upload (version 1.1.1) it is not longer possible to deploy process definitions. You get the exception 'The process definition was rejected because no multiplart boundary was found'. The reason is that the gpd is using a ',' to separate its content type (in the url used to trigger the upload servlet) where it must be a ';' according to RFC1341. So instead of 'multipart/form-data,boundary=AaB03x' it must be 'multipart/form-data;boundary=AaB03x'. The webapp must work with the latest version of commons-fileupload. -- 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

19 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAOP-332) Surpress transformation errors is ignored

by Kabir Khan (JIRA)

Surpress transformation errors is ignored ----------------------------------------- Key: JBAOP-332 URL: http://jira.jboss.com/jira/browse/JBAOP-332 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.5.2.GA Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 1.5.3.GA, 2.0.0.alpha3 See if this is the case for 2.0.0.alpha2 as well -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAOP-342) JavassistMethodHashing.getMethodMap() for an interface extending another interface is empty

by Kabir Khan (JIRA)

JavassistMethodHashing.getMethodMap() for an interface extending another interface is empty ------------------------------------------------------------------------------------------- Key: JBAOP-342 URL: http://jira.jboss.com/jira/browse/JBAOP-342 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha2, 1.5.2.GA Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 1.5.3.GA, 2.0.0.alpha3 interface Super{ -- 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-382) TLS: check whether interruption policies are implemented correctly

by Bela Ban (JIRA)

TLS: check whether interruption policies are implemented correctly ------------------------------------------------------------------ Key: JGRP-382 URL: http://jira.jboss.com/jira/browse/JGRP-382 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 - Look at thread interruption policies. Are we handling these correctly ? - There are some exceptions due to uncaught interrupt exceptions - PooledExecutor.shutdownNow() interrupts all threads, therefore they need to handle interruptions correctly Suggested reading: Java Concurrency in Practice (Goetz) chapter 7 -- 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

19 years, 3 months

1
2
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