[jBPM] - How to fill the value of "outcomes" field in JBPM-console JSON for Personal Task List?
by Thomas Setiabudi
Thomas Setiabudi [https://community.jboss.org/people/thomas.setiabudi] created the discussion
"How to fill the value of "outcomes" field in JBPM-console JSON for Personal Task List?"
To view the discussion, visit: https://community.jboss.org/message/776140#776140
--------------------------------------------------------------
Hi,
In our environment, we use JBPM5.3 as a service via JBPM-Console REST service.
when we call this REST:
/gwt-console-server/rs/tasks/{idRef}
The resulting JSON is something like this:
{
tasks:
[
{
id:6,
processInstanceId:11,
processId:com.sample.evaluation,
name:Performance Evaluation,
assignee:thomas,
isBlocking:true,
isSignalling:false,
outcomes:[],
currentState:ASSIGNED,
participantUsers:[],
participantGroups:[],
url:http://localhost:8080/gwt-console-server/rs/form/task/6/render,
priority:0
},
{
id:7,
processInstanceId:11,
processId:com.sample.evaluation,
name:Performance Evaluation,
assignee:thomas,
isBlocking:true,
isSignalling:false,
outcomes:[],
currentState:ASSIGNED,
participantUsers:[],
participantGroups:[],
url:http://localhost:8080/gwt-console-server/rs/form/task/6/render,
priority:0
}
]
}
The outcomes field is always empty.. "outcomes":[]
is there any way to fill value to this field?
We have a requirement to add a custom field for every human task, and retrieve its value when we open personal task list.
We thought that maybe we can fill in the custom field in the JSON "outcomes" field.
is it possible? Or is there any other way? maybe like create a custom WorkItemHandler that extends the Human Task?
Any help is appreciated.
Regards,
Thomas Setiabudi
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/776140#776140]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[jBPM] - executor-service
by rachi
rachi [https://community.jboss.org/people/rachi] created the discussion
"executor-service"
To view the discussion, visit: https://community.jboss.org/message/816550#816550
--------------------------------------------------------------
I try to execute the attached module, I import the project into eclipse. when I execute the following errors appears :
Starting Executor Service ...
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/G:/maven_repos/org/jboss/weld/se/weld-se/2.0.0.CR2/weld-se-2.0.0.CR2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/G:/maven_repos/org/jboss/weld/servlet/weld-servlet/2.0.0.Beta4/weld-servlet-2.0.0.Beta4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]
[main] INFO org.jboss.weld.Version - WELD-000900 2.0.0 (CR2)
[main] INFO org.jboss.weld.Bootstrap - WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
[main] WARN org.jboss.weld.Bootstrap - Legacy deployment metadata provided by the integrator. Certain functionality will not be available.
mai 07, 2013 4:05:28 PM org.jboss.solder.logging.Logger info
INFO: Solder Config XML provider starting...
mai 07, 2013 4:05:29 PM org.jboss.solder.logging.Logger info
INFO: Loading XmlDocumentProvider: org.jboss.solder.config.xml.bootstrap.ResourceLoaderXmlDocumentProvider
mai 07, 2013 4:05:29 PM org.jboss.solder.logging.Logger info
INFO: Reading XML file: jar:file:/G:/maven_repos/org/jboss/seam/persistence/seam-persistence/3.1.0.Final/seam-persistence-3.1.0.Final.jar!/META-INF/beans.xml
mai 07, 2013 4:05:29 PM org.jboss.solder.logging.Logger info
INFO: Reading XML file: jar:file:/G:/maven_repos/org/jboss/seam/transaction/seam-transaction/3.1.0.Final/seam-transaction-3.1.0.Final.jar!/META-INF/beans.xml
mai 07, 2013 4:05:29 PM org.jboss.solder.logging.Logger info
INFO: Solder 3.2.0.Final (build id: 3.2.0.Final)
[weld-worker-3] INFO org.jboss.weld.ClassLoading - WELD-000119 Not generating any bean definitions from org.jboss.seam.persistence.util.EJBContextUtils because of underlying class loading error: Type javax.ejb.EJBContext not found. If this is unexpected, enable DEBUG logging to see the full error.
[weld-worker-2] INFO org.jboss.weld.ClassLoading - WELD-000119 Not generating any bean definitions from org.jboss.seam.transaction.CMTTransaction because of underlying class loading error: Type javax.ejb.EJBContext not found. If this is unexpected, enable DEBUG logging to see the full error.
[weld-worker-2] INFO org.jboss.weld.ClassLoading - WELD-000119 Not generating any bean definitions from org.jboss.seam.transaction.DefaultSeamTransaction because of underlying class loading error: Type javax.ejb.EJBContext not found. If this is unexpected, enable DEBUG logging to see the full error.
mai 07, 2013 4:05:30 PM org.jboss.solder.logging.Logger info
INFO: Preventing class org.jboss.seam.persistence.hibernate.HibernateManagedSessionExtensionImpl from being installed as bean due to @Veto annotation
mai 07, 2013 4:05:30 PM org.jboss.solder.logging.Logger info
INFO: Preventing class org.jboss.seam.transaction.EntityTransaction from being installed as bean due to @Veto annotation
mai 07, 2013 4:05:30 PM org.jboss.solder.logging.Logger info
INFO: Preventing class org.jboss.seam.persistence.HibernatePersistenceProvider from being installed as bean due to @Veto annotation
mai 07, 2013 4:05:30 PM org.jboss.solder.logging.Logger info
INFO: Preventing class org.jboss.seam.transaction.HibernateTransaction from being installed as bean due to @Veto annotation
mai 07, 2013 4:05:30 PM org.jboss.solder.logging.Logger info
INFO: Preventing class org.jboss.seam.transaction.UTTransaction from being installed as bean due to @Veto annotation
mai 07, 2013 4:05:30 PM org.jboss.solder.logging.Logger info
INFO: Preventing class org.jboss.seam.transaction.SeSynchronizations from being installed as bean due to @Veto annotation
mai 07, 2013 4:05:30 PM org.jboss.solder.logging.Logger info
INFO: Preventing class org.jboss.seam.transaction.NoTransaction from being installed as bean due to @Veto annotation
[weld-worker-1] WARN org.jboss.weld.interceptor.util.InterceptionTypeRegistry - Class 'javax.ejb.PostActivate' not found, interception based on it is not enabled
[weld-worker-1] WARN org.jboss.weld.interceptor.util.InterceptionTypeRegistry - Class 'javax.ejb.PrePassivate' not found, interception based on it is not enabled
mai 07, 2013 4:05:31 PM org.jboss.solder.exception.control.extension.CatchExtension registerHandlerMethod
INFO: Adding handler Qualifiers: [@javax.enterprise.inject.Any()] TraversalMode: BREADTH_FIRST Handles Type: class java.lang.Throwable Precedence: -100 [BackedAnnotatedMethod] public org.jboss.seam.transaction.SimpleTransactionExceptionHandler.markTransactionRollback(@Handles CaughtException<Throwable>) to known handlers
Exception in thread "main" org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
Exception 0 :
org.jboss.weld.exceptions.IllegalStateException: WELD-001332 BeanManager method getBeans() is not available during application initialization
at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerValidated(BeanManagerProxy.java:142)
at org.jboss.weld.bean.builtin.BeanManagerProxy.getBeans(BeanManagerProxy.java:80)
at org.jboss.solder.core.CoreExtension.failIfWeldExtensionsDetected(CoreExtension.java:215)
at org.jboss.solder.core.CoreExtension.afterBeanDiscovery(CoreExtension.java:208)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:274)
at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:261)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:240)
at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:170)
at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:129)
at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:103)
at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:63)
at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:35)
at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:53)
at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:515)
at org.jboss.weld.bootstrap.api.helpers.ForwardingBootstrap.deployBeans(ForwardingBootstrap.java:63)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:137)
at org.jbpm.executor.ExecutorModule.<init>(ExecutorModule.java:31)
at org.jbpm.executor.ExecutorModule.getInstance(ExecutorModule.java:24)
at org.jbpm.executor.ExecutorMain.main(ExecutorMain.java:15)
at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:37)
at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:53)
at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:515)
at org.jboss.weld.bootstrap.api.helpers.ForwardingBootstrap.deployBeans(ForwardingBootstrap.java:63)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:137)
at org.jbpm.executor.ExecutorModule.<init>(ExecutorModule.java:31)
at org.jbpm.executor.ExecutorModule.getInstance(ExecutorModule.java:24)
at org.jbpm.executor.ExecutorMain.main(ExecutorMain.java:15)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/816550#816550]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
[Performance Tuning] - multiple applications in one instance or multiple instances with an application?
by Marco Sarti
Marco Sarti [https://community.jboss.org/people/msarti66] created the discussion
"multiple applications in one instance or multiple instances with an application?"
To view the discussion, visit: https://community.jboss.org/message/816520#816520
--------------------------------------------------------------
Hi,
One of my clients has a cluster of two nodes JBoss 4.3 with about 30 web applications with Apache as front-end/balancer.
Currently he observes several administrative problems: frequent PermGen space errors, applications that disturb each other, and so on, in practice the situation is not exactly under control.
I have observed that:
- Not all applications require balancing, it is useless for almost all
- Some applications are very critical, but the majority are not at all
- Most of the applications use only the engine web, even if the configuration contains all the services
- Many applications consume very few resources, others a lot.
- Both nodes (RedHat linux) are virtual machines in a VMware Infrastructure with 3 virtual cores. The infrastructure is HA, so application ridundancy is not really necessary
What I have to do is plan for rationalization. Starting from the two extremes (all applications in one instance and one instance per application) and considering the hardware as is for now, what logic can be applied to make this infrastructure more rational (and manageable)?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/816520#816520]
Start a new discussion in Performance Tuning at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month