Why not convert all methods that can take Options to varargs?
cache.get(Fqn f, Object key, Option... o);
You can then call it with or without option, i.e.:
And also like this:
Option myOption = ...
| cache.get("a/b/c", "k", myOption);
Even better now, you can define individual Option as subsclasses/implementations of Option allowing each to carry extra parameters if needed.
For example: Let's imagine that for https://jira.jboss.org/jira/browse/JBCACHE-1470 we would like to add the cache listener class to the supress event notification. You could do something like this:
SupressEvenNotificationOption seno = ....; // SupressEvenNotificationOption implements Option
| cache.put("a/b/c", "k", "v", seno);
This looks much cleaner to me and you avoid multiple method definitions in Cache API.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205679#4205679
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205679
anonymous wrote : * if no proper match exist, we'll clearly indicate that this construct is not BPMN and that it is jPDL specific
i've been searching a bit into the most recent version of the spec and i can't find a real extension solution in the spect to do that.
i can only find how to add custom properties to bpmn elements. but not how we could indicate that we're overriding the default bpmn behaviour.
we're looking for extensibility on the graphical notation level. and it seems that that is exactly what is been blocked in the spec.
for example, the wait state that bernd mentioned. does anyone have an idea how we can model the jpdl state behaviour correctly in bpmn ?
or do you know of sections in the spec that would allow us to indicate that we're overriding the default AND-split for the outgoing transitions ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205664#4205664
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205664
So commit r5759 adds the structure for the outbound part of the RA.
The work is based on Adrian's work and include some of the settings to setup the connection to JBM 2.0.
Important places to look currently:
Missing parts - to be completed:
* SerialVersionUIDs once all classes are complete
* Ability to specify all options for JBossConnectionFactory
* Verification of transaction / XA
* General testing (integration of JBM 2.0 + RA into AS)
* TCK testing
But look it over and send me your feedback.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205639#4205639
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205639