[Design of JBoss jBPM] - Re: how crucial are exception handlers ?
by estaub
I think it's really important to get rigorous about defining transaction behavior. The default transaction scope across nodes needs to be obvious to the process author. Currently, if I'm not mistaken, the transaction scope is controlled mostly by whether activities are synchronous or not, i.e., by whether a transition is taken within the execute() method of an activity, or a transition is taken because of some external event (e.g., a simple timer node). This is a detail of the implementation of the activity that may not be obvious to the process author.
Similarly, the interaction between rollbacks in delegation classes and PVM's process-state persistence needs to be clear.
Since Bonita doesn't even allow transactions to span activities, this probably isn't a concern there - it's mostly an issue for JPDL or anything else that tries to address "microflow" requirements.
-Ed Staub
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134577#4134577
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134577
18 years, 1 month
[Design of JBossXB] - Re: XmlElementWrapper tests
by adrian@jboss.org
The testcase is CollectionWithValues.
(remove the modification then you'll see it fail)
Its not a javabean its a real collection
and it doesn't have "items" it has an add() operation. :-)
| @XmlType()
| @JBossXmlNoElements
| @JBossXmlChildren
| ({
| @JBossXmlChild(name="array", type=AbstractArrayMetaData.class),
| @JBossXmlChild(name="collection", type=AbstractCollectionMetaData.class),
| @JBossXmlChild(name="inject", type=AbstractDependencyValueMetaData.class),
| @JBossXmlChild(name="list", type=AbstractListMetaData.class),
| @JBossXmlChild(name="map", type=AbstractMapMetaData.class),
| @JBossXmlChild(name="null", type=AbstractValueMetaData.class),
| @JBossXmlChild(name="set", type=AbstractSetMetaData.class),
| @JBossXmlChild(name="this", type=ThisValueMetaData.class),
| @JBossXmlChild(name="value", type=StringValueMetaData.class)
| })
| @JBossXmlChildWildcard(wrapper=AbstractValueMetaData.class, property="value")
| public class AbstractCollectionMetaData extends AbstractTypeMetaData
| implements Collection<MetaDataVisitorNode>, Serializable
|
If you think it is confusing then we could condition it on @JBossXMLNoElements
or something that identifies it for this usecase?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134568#4134568
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134568
18 years, 1 month