August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-722) create ws call signalToken(Long id) and signalToken(Long id, String transition)

by Ronald van Kuijk (JIRA)

create ws call signalToken(Long id) and signalToken(Long id, String transition) -------------------------------------------------------------------------------- Key: JBPM-722 URL: http://jira.jboss.com/jira/browse/JBPM-722 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, 6 months

1
2
0 / 0

[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, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-718) Add a webservice frontend to jBPM

by Ronald van Kuijk (JIRA)

Add a webservice frontend to jBPM --------------------------------- Key: JBPM-718 URL: http://jira.jboss.com/jira/browse/JBPM-718 Project: JBoss jBPM Issue Type: Feature Request Environment: n/a Reporter: Ronald van Kuijk Assigned To: Ronald van Kuijk Priority: Minor Fix For: jBPM 3.2 A webservice frontend is an interesting feature. A schema has to be designed, ws toolkit choosen (jbossws 1.0.2GA?) subdir created in the build, ant files etc... etc...etc... Subtasks will be created for this. Anyone to jump in, feel free -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-724) create tests for jbpm WS frontend

by Ronald van Kuijk (JIRA)

create tests for jbpm WS frontend --------------------------------- Key: JBPM-724 URL: http://jira.jboss.com/jira/browse/JBPM-724 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, 6 months

1
3
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, 6 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, 6 months

2
3
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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-405) add support for searching

by Michael Neale (JIRA)

add support for searching ------------------------- Key: JBRULES-405 URL: http://jira.jboss.com/jira/browse/JBRULES-405 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale Priority: Minor Generic search -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-527) JBoss Messaging should support JMSXDeliveryCount

by Joel Lindheimer (JIRA)

JBoss Messaging should support JMSXDeliveryCount ------------------------------------------------- Key: JBMESSAGING-527 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-527 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.0.1.CR4 Environment: All Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov Joel: Here is an excerpt from theserverside which sums up the retry concept within a transaction well: http://www.theserverside.com/tt/articles/content/JMSArchitecture/JMSAppli... For point-to-point messaging, when a transaction reads a message, the message becomes available to the transaction, but does not get physically removed from the destination at that time; instead, the messaging system leaves the message on the destination but does not allow other transactions to see it. When the transaction commits, the message is completely removed from the destination; however, if the transaction rolls back, the message stays on the destination and is now allowed to be read by other transactions. Ovidiu: Right. This is what Messaging does it. Though, to be 100% technically accurate, what it does is actually transacting acknowledgments. The message becomes available to the transaction, and it's the acknowledgment that is sent back to the channel in a transactional context. The acknowledgment is delivered to the channel (and the message removed from the channel) only when transaction commits. This allows for a powerful feature called replay. Replay is the ability to retry the transaction after a rollback. The danger here is you can get caught in an infinite loop trying to replay the transaction. However, JMS systems can make use of the re-delivered count field on the message descriptor. Here, one can determine how many times the message has been re-delivered to a consumer and allow one to stop processing the message. We're actually not supporting JMSXDeliveryCount yet, you're right here. The spec says it's optional. If it's important for you, just log a JIRA feature request, and we'll do it, subject to resource availability :). Joel: Thanks Ovidiu, JMSXDeliveryCount is definitely a very high priority for us. With the rapid growing adoption of MDP use I imagine that I will be something that is also in high demand for the community at large. Furthermore, most JMS vendors support this behavior, so it probably makes sense for JBoss to put it on the roadmap. -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-738) Add format of persistent state transfer to CacheLoader API Javadoc

by Brian Stansberry (JIRA)

Add format of persistent state transfer to CacheLoader API Javadoc ------------------------------------------------------------------ Key: JBCACHE-738 URL: http://jira.jboss.com/jira/browse/JBCACHE-738 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.0.0 Persistent state is a serialized series of NodeData objects. All the standard CacheLoader impls use this format. The requirement to use this format should be added to the CacheLoader API Javadoc to make it part of the official API contract. This will ensure interoperability between cache loaders (e.g state generated by a user's CustomCacheLoader can be stored by JDBCCacheLoader, etc.) -- 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, 6 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 August 2006