[JBoss JIRA] Updated: (JBPM-412) have process start accept a map of variables
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-412?page=all ]
Ronald van Kuijk updated JBPM-412:
----------------------------------
Fix Version/s: jBPM 3.3
(was: jBPM 3.2)
Slipping, due to build changes, code changes and the lack of time to keep up. Both should have stabilzed after 3.2 so 3.3 is a more realistic timeline
> have process start accept a map of variables
> --------------------------------------------
>
> Key: JBPM-412
> URL: http://jira.jboss.com/jira/browse/JBPM-412
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Affects Versions: jBPM 3.0.1
> Reporter: Ronald van Kuijk
> Assigned To: Ronald van Kuijk
> Priority: Minor
> Fix For: jBPM 3.3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> The processstart api has no option of accepting variables. This way you cannot use them in the process-start event. This fires when it is started, before you can set any variables. Be passing e.g. a map of variables to the process start this becomes possible.
--
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
[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, 3 months
[JBoss JIRA] Created: (JBREM-667) Worker thread names are confusing
by Ovidiu Feodorov (JIRA)
Worker thread names are confusing
---------------------------------
Key: JBREM-667
URL: http://jira.jboss.com/jira/browse/JBREM-667
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.2.0.Alpha4, 2.2.0.Alpha3 (Bluto)
Reporter: Ovidiu Feodorov
Assigned To: Tom Elrod
Priority: Minor
Fix For: 2.2.0.Alpha5
The worker thread names are confusing.
Example: "SocketServerInvokerThread-10.1.122.40-0", "SocketServerInvokerThread-10.1.122.42-8"
They contain the IP address of the client that originally caused the worker thread to be created, but then the worker threads are recycled via the thread pool, ending in handling invocations from clients created from completely different IP addresses.
I propose calling them "RemotingWorkerThread-<counter>"
--
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