[JBoss JIRA] Updated: (JBPM-1039) OutOfMemoryError While using multi h:selectOneRaido in dataform with multy columns
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-1039?page=all ]
Thomas Diesler updated JBPM-1039:
---------------------------------
Assignee: (was: Tom Baeyens)
> OutOfMemoryError While using multi h:selectOneRaido in dataform with multy columns
> ----------------------------------------------------------------------------------
>
> Key: JBPM-1039
> URL: http://jira.jboss.com/jira/browse/JBPM-1039
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Web Interface
> Affects Versions: jBPM jPDL 3.2.1
> Environment: jBPM 3.2.1 Tomcat 6.0.14
> Reporter: zhou guangzhao
> Priority: Minor
>
> The following taskform code works in JBPM3.2.GA.
> But when running in JBPM 3.2.1, it causes OutOfMemoryError. By testing, I found that if I change <jbpm:dataform columns="2"> to <jbpm:dataform>, it will work well in both JBPM3.2.GA and JBPM3.2.1.
> Sometimes it maybe works in JBPM3.2.1. But while adding more h:selectOneRadio, I get the error.
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" >
> <!-- the DOCTYPE means we are required to use html for a root element -->
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:c="http://java.sun.com/jstl/core"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:tf="http://jbpm.org/jsf/tf"
> xmlns:jbpm="http://jbpm.org/jsf">
> <ui:component>
> <jbpm:dataform columns="2">
>
> <f:facet name="header">
> <h:outputText value="#{taskName}"/>
> </f:facet>
>
> <!-- TASKFORM ROWS -->
> <jbpm:datacell>
> <f:facet name="header">
> <h:outputText value="Sex"/>
> </f:facet>
> <h:selectOneRadio id="StudentSex" value="#{var['StudentSex']}">
> <f:selectItem itemLabel="Male" itemValue="Male"/>
> <f:selectItem itemLabel="Female" itemValue="Female"/>
> </h:selectOneRadio>
> </jbpm:datacell>
> <jbpm:datacell>
> <f:facet name="header">
> <h:outputText value="HasAS"/>
> </f:facet>
> <h:selectOneRadio id="HasAS" value="#{var['HasAS']}" >
> <f:selectItem itemLabel="Yes" itemValue="Yes"/>
> <f:selectItem itemLabel="No" itemValue="No"/>
> </h:selectOneRadio>
> </jbpm:datacell>
>
> <jbpm:datacell>
> <f:facet name="header">
> <h:outputText value="Actions"/>
> </f:facet>
> <!-- TASKFORM BUTTONS -->
> <tf:saveButton value="Save"/>
> <tf:cancelButton value="Cancel"/>
> <tf:transitionButton value="Save and Close"/>
> </jbpm:datacell>
>
> </jbpm:dataform>
>
> </ui:component>
> </html>
>
--
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
17 years, 10 months
[JBoss JIRA] Updated: (JBPM-1070) The jBPM test configuration has problem with database setup
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-1070?page=all ]
Thomas Diesler updated JBPM-1070:
---------------------------------
Assignee: (was: Tom Baeyens)
> The jBPM test configuration has problem with database setup
> -----------------------------------------------------------
>
> Key: JBPM-1070
> URL: http://jira.jboss.com/jira/browse/JBPM-1070
> Project: JBoss jBPM
> Issue Type: Bug
> Affects Versions: jBPM jPDL 3.2.2
> Reporter: Jiri Pechanec
>
> The jBPM test process expects hiberante.properties file to be placed in defined configuration directory. jBPM config file JBPM.3/jpdl/jar/src/test/config/jbpm.cfg.xml orders to use hibernate.properties file (<string name="resource.hibernate.properties" value="hibernate.properties" />).
> But the JBPM.3/jpdl/jar/src/test/java/org/jbpm/db/AbstractDbTestCase.java uses config file less JBPM.3/jpdl/jar/src/test/java/org/jbpm/jbpm.test.cfg.xml and the line mentioned above is missing. Thus the configuration is read from standard hibernate.cfg.xml.
> Solution
> Either add the missing line to jbpm.test.cfg.xml or change AbstractDbTestCase.java to use central config file in config directory. The second one is preferred.
--
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
17 years, 10 months
[JBoss JIRA] Updated: (JBPM-996) Add ESB Service Node to jpdl and jpdl-designer
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-996?page=all ]
Thomas Diesler updated JBPM-996:
--------------------------------
Assignee: (was: Tom Baeyens)
> Add ESB Service Node to jpdl and jpdl-designer
> ----------------------------------------------
>
> Key: JBPM-996
> URL: http://jira.jboss.com/jira/browse/JBPM-996
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Environment: The ESB has an ESBActionHandler that can be manually configured at each node representing an ESB service in a jPDL processdefinition. A new node type of service-node, that is supported through the jpdl designer, would make it easier for the user to add these sevices, as the designer would know what properties are required for the user to provide.
> A nice thing about the ESB from a jBPM perspective (and an ESB Service Node) is that it gives jBPM access to practically any type of service through the same node-type, e.g., web services, rule services, jms queues, file transfer services, etc. So if jBPM has a service node, it eliminates the need to create lots of other specialized node types in jBPM, and less of a need for customers to create custom action handlers.
> Reporter: Jeff DeLong
>
--
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
17 years, 10 months
[JBoss JIRA] Updated: (JBPM-1016) ProcessState 'leave' method always returns default transition
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-1016?page=all ]
Thomas Diesler updated JBPM-1016:
---------------------------------
Assignee: (was: Tom Baeyens)
> ProcessState 'leave' method always returns default transition
> --------------------------------------------------------------
>
> Key: JBPM-1016
> URL: http://jira.jboss.com/jira/browse/JBPM-1016
> Project: JBoss jBPM
> Issue Type: Patch
> Components: Core Engine
> Affects Versions: jBPM jPDL 3.2
> Reporter: Randy Gullett
>
> The leave method for ProcessStates currently automatically takes the default transition despite taking a transition as a parameter. Can it be modified so that it leaves by the transition passed in (if it isn't null) like you'd expect it to? I want to be able to short-circuit my subprocesses in certain scenarios. See the method as it's currently coded below.
> public void leave(ExecutionContext executionContext, Transition transition) {
> ProcessInstance subProcessInstance = executionContext.getSubProcessInstance();
> Token superProcessToken = subProcessInstance.getSuperProcessToken();
> // feed the readable variableInstances
> if ((variableAccesses != null) && (!variableAccesses.isEmpty())) {
> ContextInstance superContextInstance = executionContext.getContextInstance();
> ContextInstance subContextInstance = subProcessInstance.getContextInstance();
> // loop over all the variable accesses
> Iterator iter = variableAccesses.iterator();
> while (iter.hasNext()) {
> VariableAccess variableAccess = (VariableAccess) iter.next();
> // if this variable access is writable
> if (variableAccess.isWritable()) {
> // the variable is copied from the sub process mapped name
> // to the super process variable name
> String mappedName = variableAccess.getMappedName();
> Object value = subContextInstance.getVariable(mappedName);
> String variableName = variableAccess.getVariableName();
> log.debug("copying sub process var '"+mappedName+"' to super process var '"+variableName+"': "+value);
> if (value!=null) {
> superContextInstance.setVariable(variableName, value, superProcessToken);
> }
> }
> }
> }
> // fire the subprocess ended event
> fireEvent(Event.EVENTTYPE_SUBPROCESS_END, executionContext);
> // remove the subprocess reference
> superProcessToken.setSubProcessInstance(null);
>
> // We replaced the normal log generation of super.leave() by creating the log here
> // and overriding the addNodeLog method with an empty version
> superProcessToken.addLog(new ProcessStateLog(this, superProcessToken.getNodeEnter(), new Date(), subProcessInstance));
> // call the subProcessEndAction
> [b]super.leave(executionContext, getDefaultLeavingTransition());[/b] }
> The bold line could be replaced by something like:
> if(transition != null) {
> super.leave(executionContext, transition);
> } else {
> super.leave(executionContext, getDefaultLeavingTransition());
--
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
17 years, 10 months