February 2009 - jbpm-dev - Jboss List Archives

[Design of JBoss jBPM] - Re: email templates

by tom.baeyens＠jboss.com

keep me posted on your progress. i'm all ears. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209631#4209631 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209631

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: EJB3 enterprise module?

by alex.guizar＠jboss.com

anonymous wrote : Damn, it seems that linking a Timer to an EJB3 Entity seems not to be possible like in EJB 2.1 (regarding https://jira.jboss.org/jira/browse/JBPM-886 ). In the current implementation the Timer POJO is flushed and loaded as an EJB2 entity bean. It works but looks and feels dirty. If the hack is not easily portable to EJB3 then we should just use two different tables. It does not make sense to sacrifice cleanliness just to save one table. Another thought: the EJB3 stuff should not go into jBPM3, it would mostly bring further maintenance burdens and would certainly not be accepted for inclusion into SOA-P. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209628#4209628 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209628

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: email templates

by kukeltje

ok... bootstrapping works for 80% already... not realy that difficult with the seam mock, a small example from ICEFaces and some things from RichFaces.... Last thing to do seems to be getting the right EL resolvers in place... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209620#4209620 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209620

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: email templates

by kukeltje

I've been looking into what is already in seam. There is a complete mock framework for testing seam including mocking lots of jsf stuff. From what I've seen, this could be leveraged, either by using those classes or by code duplication. So imo it is 100% feasible to have this in place before july 1st. Never the less, some additional bootstrapping from Pete would help. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209535#4209535 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209535

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - first cut of the new history

by tom.baeyens＠jboss.com

HistoryEvents are fired during process execution. We maintain history information on 2 levels: process instance and activity instance. Process instance start and process instance end generate history events are fired directly from within the implementation. ActivityBehaviour implementations are responsible for calling the historyXxx methods that are exposed on the ActivityExecution All the HistoryEvents are delegated to a HistorySession. The default HistorySessionImpl will invoke the process() method on the history events themselves. The HistoryEvents are temporary events. In the process method, they build up the information in the history model. There is a HistoryProcessInstance and there is a whole class hierarchy starting with HistoryActivityInstance. In the HistoryEvent.process methods, the history events create model entities or merge information into the model entities. For instance, a ProcessInstanceStart history event will create a HistoryProcessInstance entity/record. And the ProcessInstanceEnd will set the endTime property in the existing HistoryProcessInstance entity/record. Similar pattern for the activities. But for automatic activities, there is an optimisation so that only 1 event is created and all the information is stored in one single insert (as all this happens inside 1 transaction). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209523#4209523 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209523

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: email templates

by kukeltje

There was an additional reason I asked if you had more info from Pete. The bpm/b2b/... framework I'm developing on top of jBPM uses Facelets/JSF for the webapp, XForms for complex forms (already nicely integrated with seam contexts etc) ebMS for b2b messaging. Besides this, I need to use facelets with jsf for mail templating (customer requirement, does not want to learn new technology). So in my case it is not a big problem since there always is a webapp (even jsf based). But....out of the blue the customer asked me if it would be possible to use this mail templating in a rich client they have. So I have some payed time to look into this if I can get 'booted'. Pete just has to bootstrap me a little. GA is July 1st right? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209480#4209480 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209480

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - in memory hsqldb url

by tom.baeyens＠jboss.com

i've changed the in memory hsqldb url back to jdbc:hsqldb:mem:. that is more convenient when debugging. as org.hsqldb.util.DatabaseManager.main(new String[]{}) uses that url as the default View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209400#4209400 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209400

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: email templates

by tom.baeyens＠jboss.com

finishing the (i.e. Seam mail would boot > JSF itself) might be out of our reach for the GA release. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209369#4209369 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209369

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: email templates

by kukeltje

Yes, I have another option: Develop one completely ourselves... is probably much easier, costs less time, easier to maintain, makes us independent of other frameworks (so e.g. not using velocity either). Best is even to not use EL. Or am I cynical now? Real answer: Depends on what the requirements are..... Velocity would be an option... Since Pete Muir responded that work already started to make the templating (jsf+facelets, not jsp) independent of a webapp, I assume you asked him how much work (and what) still needs to be done for that. Both projects can benefit if this is completed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209305#4209305 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209305

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - ModelAdaptor fix

by tom.baeyens＠jboss.com

heiko, i commented a line in ModelAdaptor to fix a compilation problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209194#4209194 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209194

17 years, 2 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev February 2009