[jBPM Development] - Re: jBPM4 History/Log implementation.
by rams.rapo
Hi,
I noticed that whenever fields like duedate on a task are changed, the dbversion column gets incremented. However there's no entry in history detail table to see old and new values.
Also in history task impl class we may be losing reference to detail before persisting it.
|
| public void updated(TaskImpl task) {
| if ( (assignee==null && task.getAssignee()!=null)
| || (assignee!=null) && (!assignee.equals(task.getAssignee()))
| ) {
| addDetail(new HistoryTaskAssignmentImpl(assignee, task.getAssignee()));
| this.assignee = task.getAssignee();
| }
| if (priority!=task.getPriority()) {
| addDetail(new HistoryPriorityUpdateImpl(priority, task.getPriority()));
| this.priority = task.getPriority();
| }
| if ( (duedate==null && task.getDuedate()!=null)
| || (duedate!=null) && (!duedate.equals(task.getDuedate()))
| ) {
| addDetail(new HistoryTaskDuedateUpdateImpl(duedate, task.getDuedate()));
| this.duedate = task.getDuedate();
| }
| }
|
| // details //////////////////////////////////////////////////////////////////
|
|
| public void addDetail(HistoryDetailImpl detail) {
| detail.setHistoryTask(this, nextDetailIndex);
| nextDetailIndex++;
| }
|
|
Env:
| jbpm 4.0
| jboss 5.1.0
| Oracle 10g
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266210#4266210
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266210
16 years, 4 months
[JBoss OSGi Development] - Re: Service integration with MC
by alesj
"alesj" wrote :
| But what to do with stop, destroy and uninstalls?
|
| | try {
| | uninstallMethod.invoke(target, VMD::get)
| | } finally {
| | VDM::unget
| | }
| |
| whereas service could still hold onto the ref - which might be an issue if that ref is ServiceFactory,
| as ServiceFactory::unget could modify the actual created service.
|
Another problem/ugliness that I see is the usage of "external" service to do proper parameter type matching at uninstall.
e.g. bean + parameters at uninstalls, bean + parameters in value-factory, ...
This can be "properly" dealt with double call to ungetTarget.
| if (unget)
| {
| try
| {
| Object target = context.getTarget();
| // do parameter type matching
| ...
| }
| finally
| {
| context.ungetTarget();
| }
| context.ungetTarget();
| }
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266147#4266147
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266147
16 years, 4 months
[JBoss Microcontainer Development] - Re: Supporting qualifiers in MC
by alesj
"kabir.khan(a)jboss.com" wrote :
| And there is a bean in the controller of type Something, but it does not supply @Test? I think coarse-grained needs to work slightly differently from fine-grained. Fine-grained needs a bean with all the qualifiers specified at the injection point. Coarse-grained needs a bean with as many as possible of the qualifiers specified at bean level.
|
We just need to make sure we have exact rules, whatever those might be.
The stuff we discussed could be categorized as pseudo. :-)
I guess the real examples and commons sense will flush those rules out.
"kabir.khan(a)jboss.com" wrote :
| When looking into this, I noticed that AbstractInjectionValueMetaData takes the LookupStrategy into account when searching for the context, while the SearchClassContextDependencyItem does not appear to do so.
|
Could be an oversight.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266141#4266141
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266141
16 years, 4 months