[Design of JBoss jBPM] - Re: extending form / task functionality
by tom.baeyens@jboss.com
ok. some very interesting views have passed the stage here.
On the basics, i think we are in agreement. jBPM should be mostly concerned with its core expertise: process executions. All other things should be optional.
Such related things are the identity component, the default UI, task management, process analysis and modelling, ...
Let me try and give this discussion the original (limited) focus: Should we add this one String field to the task that serves as a UI task form identifier. This would be a bit similar as the actorId field.
Pro's: every UI technology (amongst which the default one) will be able to use this field to link the task with the form.
Con's: if not used, will this empty field harm performance ?
I'm not trying to settle the fylosophical debates on how and when the UI has to be separated from the core process. IMO, these are similar discussions as 10 years ago: "how OO classes should be modelled". It is important that there is no hard dependency on any UI technology. And secondly, multiple (not all) UI technologies will be able to make use of it. So i see this as a convenience integration point for UI's. Without the need to get to the bottom of the 'taste'-discussion about what should be where... Let's leave that up to our users.
I don't think we should be disabling features to prevent people from making mistakes. Who would have ever created gunpowder in that kind of reasoning ? We have to explain good practices and tradeoffs in the docs and with sensible defaults. IMO, not by removing optional integration features.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979950#3979950
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979950
19 years, 5 months
[Design of JBoss jBPM] - Re: MessageService and JMS
by mteira
anonymous wrote : command and job are similar. code must be refactored so that the MDB and SLSB work together. the confusion is caused by the fact that the impl of cmdlistener and cmdservice are not yet complete. the first thing we need is a testing set up and completing the impl that is there.
If you can identify here some concrete work that I could do, please make me know.
anonymous wrote : so we don't need other beans. we only need to make sure that Job implements Command or change something else so that it works.
OK. I'll take a look at it.
anonymous wrote : In the next two weeks, i will have some time to help and actually do some work together with you on this. So if you can keep the fight up for a few more days.... help is on its way.
Nice to hear that. Thanks a lot.
--
Manuel.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979949#3979949
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979949
19 years, 5 months
[Design of Kosmos] - Re: SvnMonitoringPortlet
by lamerbot
I tryed latest jar, but exception comes again. I check source and found that simple code :
| try {
| SVNRepository repository = connect("http://anonsvn.labs.jboss.com/labs/jbossrules/trunk");
| System.out.println(repository.getLocation().toString());
| Collection logEntries = repository.log(new String[] {
| ""
| }, null, 0L, repository.getLatestRevision(), true, false);
| }
| catch (Exception ex) {
| ex.printStackTrace();
| }
|
throws that exception
| org.tmatesoft.svn.core.SVNException: svn: REPORT of '/!svn/bc/7012/labs/jbossrules/trunk': 400 Bad Request (http://anonsvn.labs.jboss.com)
| at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:43)
| at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.log(DAVRepository.java:487)
| at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:629)
| at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:919)
| at main.main(main.java:24)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
|
Exception throws
| Collection logEntries = repository.log(new String[] {
| ""
| }, null, 0L, repository.getLatestRevision(), true, false);
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979942#3979942
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979942
19 years, 5 months