October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-721) create ws call startProcess(String name)

by Ronald van Kuijk (JIRA)

create ws call startProcess(String name) ----------------------------------------- Key: JBPM-721 URL: http://jira.jboss.com/jira/browse/JBPM-721 Project: JBoss jBPM Issue Type: Sub-task Reporter: Ronald van Kuijk Assigned To: Ronald van Kuijk -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-723) Commit ws source into cvs

by Ronald van Kuijk (JIRA)

Commit ws source into cvs ------------------------- Key: JBPM-723 URL: http://jira.jboss.com/jira/browse/JBPM-723 Project: JBoss jBPM Issue Type: Sub-task Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Priority: Minor Fix For: jBPM 3.2 -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-715) Implement runtime automagically generated forms

by Ronald van Kuijk (JIRA)

Implement runtime automagically generated forms ----------------------------------------------- Key: JBPM-715 URL: http://jira.jboss.com/jira/browse/JBPM-715 Project: JBoss jBPM Issue Type: Feature Request Components: Web Interface Environment: n/a Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Priority: Minor Fix For: jBPM 3.2 As long as it is not possible to generate an .xhtml file from the gpd for a task, it should be possible to use a designed process without the need to create custom forms. Initially this would be identical to the 3.1 automagical forms (not taking into account the variable type) but it should some day. Taking the variable type into account would be possible if the variable already exists in the process instances, but if it is initially filled via a type agnostic ui, it will always be string. If it is set via the api, we could take it into account. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3617) 3 failing tests in org.jboss.test.util.test.PropertyEditorsUnitTestCase

by Dimitris Andreadis (JIRA)

3 failing tests in org.jboss.test.util.test.PropertyEditorsUnitTestCase ----------------------------------------------------------------------- Key: JBAS-3617 URL: http://jira.jboss.com/jira/browse/JBAS-3617 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_05 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_05-b05 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-34.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA testEditorSearchPath Failure Found org.jboss.util.propertyeditor in search path junit.framework.AssertionFailedError: Found org.jboss.util.propertyeditor in search path at org.jboss.test.util.test.PropertyEditorsUnitTestCase.testEditorSearchPath(PropertyEditorsUnitTestCase.java:127) testJavaLangEditors Failure Found property editor for: class java.lang.Boolean junit.framework.AssertionFailedError: Found property editor for: class java.lang.Boolean at org.jboss.test.util.test.PropertyEditorsUnitTestCase.doTests(PropertyEditorsUnitTestCase.java:403) at org.jboss.test.util.test.PropertyEditorsUnitTestCase.testJavaLangEditors(PropertyEditorsUnitTestCase.java:188) testJBossEditors Failure Found property editor for: class javax.management.ObjectName junit.framework.AssertionFailedError: Found property editor for: class javax.management.ObjectName at org.jboss.test.util.test.PropertyEditorsUnitTestCase.doTests(PropertyEditorsUnitTestCase.java:403) at org.jboss.test.util.test.PropertyEditorsUnitTestCase.testJBossEditors(PropertyEditorsUnitTestCase.java:306) -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-151) Does the ParamsRepository approach conflict with, or support, the PropertyManager?

by Mark Little (JIRA)

Does the ParamsRepository approach conflict with, or support, the PropertyManager? ---------------------------------------------------------------------------------- Key: JBESB-151 URL: http://jira.jboss.com/jira/browse/JBESB-151 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.1 -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-219) Remove all occurrences of System.exit from code

by Mark Little (JIRA)

Remove all occurrences of System.exit from code ----------------------------------------------- Key: JBESB-219 URL: http://jira.jboss.com/jira/browse/JBESB-219 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.1 The use of System.exit from within product is generally to be avoided. Critical errors that SHOULD result in the VM exiting can be dealt with my throwing errors. If the application wants to catch them and ignore them, then fine. But we should not take that control out of the user's hands. -- 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, 4 months

1
8
0 / 0

[JBoss JIRA] Created: (JBAS-3746) org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase.testValidAttribute failure

by Len DiMaggio (JIRA)

org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase.testValidAttribute failure ----------------------------------------------------------------------------------------- Key: JBAS-3746 URL: http://jira.jboss.com/jira/browse/JBAS-3746 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.5.CR1 Environment: OS/Kernel/Arch = RHEL4/U4 - Linux 2.6.9-42.0.2.ELsmp #1 SMP Thu Aug 17 17:57:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux JVM = R26.4.0-63_CR284516-68626-1.5.0_06-20060926-0859-linux-x86_64 JBossAS = 20091002 Branch_4_0 of JBoss AS, http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_0 Reporter: Len DiMaggio Attachments: TEST-org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase.testValidAttribute.txt This test case: org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase.testValidAttribute fails with JVM = R26.4.0-63_CR284516-68626-1.5.0_06-20060926-0859-linux-x86_64 The failure is seen if the test is run as a one-test or as part of the JBossAS test suite. The error returned is: InfoTortureSUITE attribute: org.jboss.test.jbossmx.compliance.standard.support.Torture: NiceBoolean isIS expected:<true> but was:<false> junit.framework.AssertionFailedError: InfoTortureSUITE attribute: org.jboss.test.jbossmx.compliance.standard.support.Torture: NiceBoolean isIS expected:<true> but was:<false> at org.jboss.test.jbossmx.compliance.standard.AttributeInfoTEST.testValidAttribute(AttributeInfoTEST.java:65) 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, 4 months

2
15
0 / 0

[JBoss JIRA] Created: (JBAS-3614) failing org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase ----------------------------------------------------------------------- Key: JBAS-3614 URL: http://jira.jboss.com/jira/browse/JBAS-3614 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX, Test Suite Environment: Java Version 1.5.0_05 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_05-b05 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-34.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Scott M Stark Fix For: JBossAS-4.0.5.GA testRMMResourceImplementsMBean Failure testRMMResourceImplementsMBean: javax.management.MBeanException: Operation setpojoAttribute not in ModelMBeanInfo junit.framework.AssertionFailedError: testRMMResourceImplementsMBean: javax.management.MBeanException: Operation setpojoAttribute not in ModelMBeanInfo at org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase.testRMMResourceImplementsMBean(ModelMBeanTestCase.java:150) -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-215) Add a connection pool abstraction

by Mark Little (JIRA)

Add a connection pool abstraction --------------------------------- Key: JBESB-215 URL: http://jira.jboss.com/jira/browse/JBESB-215 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Reporter: Mark Little Assigned To: Mohit Keswani Priority: Optional Fix For: 4.1 We should add an abstraction that hides different implementation issues. Mohit says: "Also we can plugin C3P0 pool which hibernate uses. We should develop a base framework which can be configured with any pool, kind of like a factory." -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-403) add support for observation

by Michael Neale (JIRA)

add support for observation --------------------------- Key: JBRULES-403 URL: http://jira.jboss.com/jira/browse/JBRULES-403 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben. This can be done as "hooks" so that on a resource change, an email could be sent to an interested party (perhaps even when the status changes, to allow simple workflow so when a rule is changed, the approver is notified). -- 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, 4 months

1
1
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 October 2006