April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBPM-454) conditional transitions

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-454?page=comments#action_12359653 ] Koen Aers commented on JBPM-454: -------------------------------- Yes, it is already supported in HEAD and in the last alpha release out there. Stay tuned for a stable release. > conditional transitions > ----------------------- > > Key: JBPM-454 > URL: http://jira.jboss.com/jira/browse/JBPM-454 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2 beta 1 > > > add a mechanism to calculate the available transitions at runtime for 1) a token in a node 2) a task instance in a node -- 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] Reopened: (JBPM-619) outofmemory during ant test suite run

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-619?page=all ] Tom Baeyens reopened JBPM-619: ------------------------------ still not resolved on my machine. after running the tests, the test.report target shows the problem. probably because i have cut out the report generation that the test build script works for you. i'll keep investigating how we can resolve this. ideas and hints are appreciated. > outofmemory during ant test suite run > ------------------------------------- > > Key: JBPM-619 > URL: http://jira.jboss.com/jira/browse/JBPM-619 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2 > Reporter: Jim Rigsbee > Assigned To: David Lloyd > Fix For: jBPM jPDL 3.2 > > > MailTests will fail if your local workstation is not setup correctly. These tests are failing in the cruise control build 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-877) jta configuration for process deployment in enterprise environment

by Tom Baeyens (JIRA)

jta configuration for process deployment in enterprise environment ------------------------------------------------------------------ Key: JBPM-877 URL: http://jira.jboss.com/jira/browse/JBPM-877 Project: JBoss jBPM Issue Type: Task Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2 another bug report from Jeff: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019684#4019684 " I have reported this before: 21:11:35,953 ERROR [[ProcessUploadServlet]] Servlet.service() for servlet Proces sUploadServlet threw exception org.hibernate.HibernateException: Unable to locate current JTA transaction at org.hibernate.context.JTASessionContext.currentSession(JTASessionCont it requires changes to jbpm.cfg.xml to set to false and CMTTransactionFactory to JTATransactionFactory org.hibernate.transaction.JTATransactionFactory " -- 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
8
0 / 0

[JBoss JIRA] Created: (JBPM-889) fgdfgdfgfdg

by naeem ahmad (JIRA)

fgdfgdfgfdg ----------- Key: JBPM-889 URL: http://jira.jboss.com/jira/browse/JBPM-889 Project: JBoss jBPM Issue Type: Task Reporter: naeem ahmad Assigned To: Tom Baeyens -- 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] Created: (JBPM-734) org.jbpm.util.XmlException: couldn't parse xml

by Ivan Garcia (JIRA)

org.jbpm.util.XmlException: couldn't parse xml ---------------------------------------------- Key: JBPM-734 URL: http://jira.jboss.com/jira/browse/JBPM-734 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Reporter: Ivan Garcia Assigned To: Tom Baeyens This code try{ String cfg = "<jbpm-configuration>"; cfg += "</jbpm-configuration>"; jbpmConfiguration = JbpmConfiguration.parseXmlString(cfg); }catch(Exception e){ e.printStackTrace(); } launch this exception, org.jbpm.util.XmlException: couldn't parse xml at org.jbpm.util.XmlUtil.parseXmlInputSource(XmlUtil.java:78) at org.jbpm.util.XmlUtil.parseXmlResource(XmlUtil.java:60) at org.jbpm.configuration.ObjectFactoryParser.parseElementsFromResource(ObjectFactoryParser.java:104) at org.jbpm.JbpmConfiguration.parseObjectFactory(JbpmConfiguration.java:299) at org.jbpm.JbpmConfiguration.parseXmlString(JbpmConfiguration.java:318) Caused by: java.net.MalformedURLException at java.net.URL.<init>(URL.java:601) at java.net.URL.<init>(URL.java:464) at java.net.URL.<init>(URL.java:413) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.jbpm.util.XmlUtil.parseXmlInputSource(XmlUtil.java:76) ... 6 more and i dont know why :-( Thanks -- 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

4
7
0 / 0

[JBoss JIRA] Commented: (JBPM-578) remove JbpmSession and JbpmSessionFactory

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-578?page=comments#action_12359651 ] Tom Baeyens commented on JBPM-578: ---------------------------------- i'm thinking that leaving them in is the best approach. and leave them deprecated, of course. suppose that someone still uses them somewhere. we break his/her stuff. on top of that, it takes work to get them out. and they are nowhere documented. so nobody should get it in their head to start using it out of the blue. > remove JbpmSession and JbpmSessionFactory > ----------------------------------------- > > Key: JBPM-578 > URL: http://jira.jboss.com/jira/browse/JBPM-578 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > those are deprecated in jbpm 3.1 and will be removed in 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-885) The Comment class taskes server time i.e. time on server machine at that time, buit few system may require feature to supply date and time while creating comment on a task node.

by Ashish Kumar Singh (JIRA)

The Comment class taskes server time i.e. time on server machine at that time, buit few system may require feature to supply date and time while creating comment on a task node. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBPM-885 URL: http://jira.jboss.com/jira/browse/JBPM-885 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1 Reporter: Ashish Kumar Singh Assigned To: Tom Baeyens Priority: Minor The Comment class taskes server time i.e. time on server machine at that time, buit few system may require feature to supply date and time while creating comment on a task node. To achieve this functionality we will need to extend Comment class. This will be great if we can include this functionality in Comment class itself by giving a seter method for Coment class. -- 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
3
0 / 0

[JBoss JIRA] Created: (JGRP-468) SFC does not control unicast messages

by Brian Stansberry (JIRA)

SFC does not control unicast messages ------------------------------------- Key: JGRP-468 URL: http://jira.jboss.com/jira/browse/JGRP-468 Project: JGroups Issue Type: Task Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.4.1 SP2 SFC does not control unicast messages. This makes it unsuitable for UDP-based channels that will handle a lot of unicast, e.g. a channel used by a buddy replication-enabled JBoss Cache. Also makes it unsuitable for use as a shared multiplexed channel when one of the services might use a lot of unicast. Proposed solution is to refactor the core locking and credit accounting behavior of SFC into an inner class. SFC would then maintain an instance of that inner class to track credits for group (i.e. multipoint) messages. A separate instance of the inner class would be maintained to track unicast traffic to each peer. So, in a 4 node cluster, SFC would maintain 5 instances of the inner class. (Maintaining an instance for unicast messages to oneself is probably unnecessary, but its a lightweight object and not maintaining it would add complexity.) Will add a "control_unicast" config flag with default value of true. Allows simple disabling of unicast flow control in TCP-based configurations. -- 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: (JGRP-463) Port SFC to Branch_2_4

by Brian Stansberry (JIRA)

Port SFC to Branch_2_4 ---------------------- Key: JGRP-463 URL: http://jira.jboss.com/jira/browse/JGRP-463 Project: JGroups Issue Type: Feature Request Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.4.1 SP2 Port the new Simple Flow Control protocol to Branch_2_4. Allows more stable memory management, which is needed in JBoss AS 4.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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-467) SFC needs JGRP-292 fix

by Brian Stansberry (JIRA)

SFC needs JGRP-292 fix ---------------------- Key: JGRP-467 URL: http://jira.jboss.com/jira/browse/JGRP-467 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Reporter: Brian Stansberry Assigned To: Bela Ban If a sender thread blocks and times out, in SFC the thread will send a credit request while holding the lock. This is the same issue FC had in JGRP-292. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2007