[Design of JBoss Portal] - Portlet runtime meta data extension
by julien＠jboss.com
I would like to avoid to have to extend the Container*Info classes for its usage in 2.7, for several reasons:
1/ minimize the coupling (would not survive refactors)
2/ would require to introduce factories (so the builder creates the proper implementation subclass)
It will be more appropriate to use an extension mechanism based on composition by adding on CorePortletInfo a notion of attachment/payload, basically an hashmap using generics to more convenience.
| public interface PortletInfo
| {
| /**
| * Returns a generic attachment on the portlet info.
| *
| * @param type the parameter type
| * @return the attachment or null
| * @throws IllegalArgumentException if the parameter type is null
| */
| <T> T getAttachment(Class<T> type) throws IllegalArgumentException;
|
| ...
|
| }
|
There is a setAttachment on the ContainerPortletInfo implementation that allows to attach payload during the phase where the deployer builds the runtime meta data from the descriptor meta data.
The deployer extension will be able to add payload for the core info extensions.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135880#4135880
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135880
18 years
[Design of JBoss jBPM] - Re: iCalendar wrapper
by kukeltje
@Adrian,
jBPM does not (imo) avoid assignment states at least not at the technical level. The technical level being jbpm, the businesslevel the processdefinition.
Some explanation: You can see if a task is assigned to a person or a group. You can see if it is started, suspended, resumed and ended. Declining a task can be seen as reassigning it back to the pool (if there is one). Declining something at the businesslevel would mean taking a certain transition. Something that is logged as well.
@Tom:
I agree, not to many nodes, functionality where it belongs and making things pluggable (a real good idenity module being (imo) the most important one). Mail could be extended as well to support mime (so html messages can be send), but I'm not even sure jBPM should do all this. Why not leave some functionality up to other SOA parts. ESB conatains mail sender as well. Why not put services in there? But that is another discussion
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135806#4135806
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135806
18 years