[Design of JBoss jBPM] - Re: blobs, clobs, text and bytes
by tom.baeyens＠jboss.com
on 2) : as long as we can postpone db specific handling, that will make development much easier and our progress much faster. db-specific things means that we would need a set of mappings for each db. that means that we would have to maintain and synchronize between all those copies.
so i'ld like to keep the same mappings for all the dbs. and if we need to apply a small modification for one particular db, it should be possible to apply this change automatically from the single original source mapping files.
on 3): cause that results in incorrect behaviour in a cluster. 2nd level cache of hibernate is only used for process definition caching as that can be assumed to be static information that (after deployment) will not change.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209830#4209830
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209830
17 years, 1 month
[Design of JBoss jBPM] - console roles
by tom.baeyens＠jboss.com
yesterday during the meeting with the sa's one of the interesting feedbacks was : we have JON for operators (or linux propellorheads as burr called them :-) and we have our own GWT console that is targetted as different roles.
in the past it has been difficult to isolate those roles in the web application. as typically powerusers want to navigate from any place to any place. so it becomes difficult to offer e.g. only the task mgmt part to a task-clerk. or to embed the operator part of our console (looking and retrying failed jobs, number of optimistic locking exceptions) in JON.
our formost interest is to ship a project to the community that can get us adoption. so it definitely requires a console to be included that can show off the jbpm capabilities.
features like task lists, process monitoring, analythics and operational functions are targetted at different audiences. but how can we structure our own console towards these different roles without crippling the powerusers that want to do it all and navigate conveniently.
so how can we make parts of this web app exposed to a single target role ? and how can we leverage these components in let's say JON/JOPR and maybe Guvnor.
thoughts ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209829#4209829
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209829
17 years, 1 month
[Design of JBoss jBPM] - Re: email templates
by jbarrez
I agree with Heiko here. Working around JSF to generate an email ... it just feels wrong.
It's not because the Seam guys are doing it, that jBPM must follow. Seam works in webapp-only environment. It makes (a bit) sense there. But what if one wants to use emailing in a Swing-jBPM app? Then they have to set up a seperate app server for the email-generating webapp? This just will not happen IRL.
I also think that using Velocity would be better. Velocity is nothing more than a fast engine that fills up a template with what is provided as input. It might be not as 'fancy' as JSF, but it gets the job done in a very simple and understandable way.Users can provide their own velocity templates that can easily plugged in a jbpm process definition. Heck, you can even create a custom JPDL node for this.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209794#4209794
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209794
17 years, 1 month