[Design of JBoss jBPM] - Re: Log for task start in jbpm 3.3.1.GA
by osvaldo.pina
I deployed a very simple process with just one task:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="simple">
|
| <start-state name="start">
| <transition to="task-node1"></transition>
| </start-state>
|
| <task-node name="task-node1">
| <task name="task1"></task>
| <transition to="end"></transition>
| </task-node>
|
| <end-state name="end"></end-state>
|
| </process-definition>
|
and then I started an instance of this process and finished it tracing the logs for every action:
logs for action -> Start a new instance:
id_ = 6, class_= I -> ProcessIstanceCreateLog
logs for action -> Signal:
id_ = 7, class_= S -> SignalLog
id_ = 8, class_= T -> TransitionLog
id_ = 9, class_= 1 -> TaskCreateLog
logs for action ->Task start:
nothing was logged!
logs for action ->Task end:
id_ = 10, class_= 3 -> TaskEndLog
id_ = 11, class_= S -> SingalLog
id_ = 12, class_= N -> NodeLog
id_ = 13, class_= T -> TransitionLog
id_ = 14, class_= X -> ProcessInstaceEndLog
So, unless I missed some configuration, task starts are not being logged.
regards,
Osvaldo
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234223#4234223
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234223
15 years, 7 months
[Design of JBossXB] - Re: Marshalling an AbstractKernelDeployment
by flavia.rainone@jboss.com
"Ales" wrote : I think you should use AbstractKernelDeployment10 class.
Unfortunately, I get the same exception with AbstractKernelDeployment10:
Exception in thread "main" org.jboss.xb.binding.JBossXBRuntimeException: Failed to marshal wildcard: neither class mapping was found for class org.jboss.kernel.plugins.deployment.AbstractKernelDeployment10@15594486 (toString: AbstractKernelDeployment10@edf3f6{name=null installed=false beanFactories=[AbstractBeanMetaData@2bc3f5{name=test bean=org.jboss.microcontainer.tools.Test3 properties= constructor=null autowireCandidate=true}]}) nor marshaller for unresolved classes was setup.
| at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalWildcard(MarshallerImpl.java:833)
| at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalWildcardOccurence(MarshallerImpl.java:792)
| at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalParticle(MarshallerImpl.java:745)
| ...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234209#4234209
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234209
15 years, 7 months
[Design of Management Features on JBoss] - Re: How to Expose MBean Invocation Stats into admin-console?
by ips
Andrew,
I notice you are using MCBean:* as the component types for your MOs, e.g.:
(ComponentType{type=MCBean, subtype=*}), compName=jboss.j2ee:service=EJB3,name=UnsecuredStatelessBean-metrics-instance
>From the Jopr/client perspective, we prefer that each type of MO has a unique component type, rather than having to look at the MO's name to figure out exactly what type of MO it is. For example, we'd much prefer something like:
(ComponentType{type=MCBean, subtype=jboss.j2ee:service=EJB3}), compName=UnsecuredStatelessBean-metrics-instance
or even:
(ComponentType{type=EJB3, subtype=StatelessBean}), compName=UnsecuredStatelessBean
I think the latter style is what Scott wants to head twoard in the future (i.e. not exposing via the component type the impl detail that an MCBean or an MBean backs MOs of that type).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234202#4234202
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234202
15 years, 7 months