| From | Sent On | Attachments |
|---|---|---|
| Justin Loo | Sep 16, 2004 12:32 am | |
| Quake_Wang | Sep 16, 2004 12:42 am | |
| Hani Suleiman | Sep 16, 2004 6:13 am | |
| Mattias Bogeblad | Sep 16, 2004 8:34 am | |
| Hani Suleiman | Sep 16, 2004 8:51 am | |
| Mattias Bogeblad | Sep 17, 2004 2:31 am | |
| Mattias Bogeblad | Sep 17, 2004 2:52 am | |
| Keshavamurthy Srinivasan | Sep 17, 2004 4:53 am | |
| Hani Suleiman | Sep 17, 2004 5:32 am | |
| Mattias Bogeblad | Oct 27, 2004 1:17 am | |
| Luca Masini | Oct 27, 2004 2:22 am | |
| Mattias Bogeblad | Oct 27, 2004 2:38 am | |
| Luca Masini | Oct 27, 2004 4:09 am | |
| Mattias Bogeblad | Oct 27, 2004 4:26 am | |
| Richard Malaschitz | Oct 27, 2004 7:34 am | |
| Hani Suleiman | Oct 27, 2004 8:43 am | |
| Hani Suleiman | Oct 27, 2004 8:50 am | |
| Luca Masini | Oct 27, 2004 8:53 am | |
| Ming Xue | Oct 27, 2004 10:18 am | |
| xs | Oct 27, 2004 10:25 am | |
| Quake_Wang | Oct 27, 2004 5:42 pm | |
| Luca Masini | Oct 28, 2004 12:32 am | |
| Richard Malaschitz | Oct 28, 2004 12:43 am | |
| Mattias Bogeblad | Oct 28, 2004 12:44 am | |
| Richard Malaschitz | Oct 28, 2004 12:47 am | |
| Quake_Wang | Nov 14, 2004 6:23 pm |
| Subject: | Re: SV: [Opensymphony-workflow] Getting future steps | |
|---|---|---|
| From: | Hani Suleiman (ha...@formicary.net) | |
| Date: | Oct 27, 2004 8:43:12 am | |
| List: | net.java.dev.osworkflow.users | |
Can you actually add a patch for this? It sounds like something useful to have in osworkflow possibly.
On Oct 27, 2004, at 5:38 AM, Mattias Bogeblad wrote:
Hi Luca,
We would be really thankful if you would like to share your code. Can you send it to matt...@sprawlsolutions.se?
Regards Mattias Bogeblad
_______________________________________________________________ Mattias Bogeblad | PH: +46 31 761 09 03 | MOB: +46 702 80 05 05 SPRAWL SOLUTIONS AB Drottningatan 5 403 14 GÖTEBORG
_______________________________________________________________
-----Ursprungligt meddelande----- Från: Luca Masini [mailto:l.ma...@infogroup.it] Skickat: den 27 oktober 2004 11:22 Till: use...@osworkflow.dev.java.net Ämne: Re: [Opensymphony-workflow] Getting future steps
We implemented this in our project, but for now it's not integrated in OSWF. In case we can share with you. Ciao. L.
Mattias Bogeblad wrote:
Hi all,
Is there a way to get a list of future steps in the same way as we can get history steps? We would like to visualize the process for the user. I imagine it may be tricky as a lot of conditions and split/joins can occur.
Regards Mattias Bogeblad
_______________________________________________________________ Mattias Bogeblad | PH: +46 31 761 09 03 | MOB: +46 702 80 05 05 SPRAWL SOLUTIONS AB Drottningatan 5 403 14 GÖTEBORG
_______________________________________________________________
-----Ursprungligt meddelande----- Från: Hani Suleiman [mailto:ha...@formicary.net] Skickat: den 16 september 2004 17:52 Till: use...@osworkflow.dev.java.net Ämne: Re: [Opensymphony-workflow] OSWorkflow without OSUser and
without
DataSource
On Sep 16, 2004, at 11:34 AM, Mattias Bogeblad wrote:
Hi,
I like OSWorkflow. So far I have only run my integration in
MemoryStore
and now I'm switching to JDBC-store. Now my first question:
1. Why cannot JDBCWorkflowStore deal with none-datasources? In my
app
we cannot rely on the appservers setup or anythink like that - we need
to
be very self contained for ease of installation among other things.
I
get by now by writing my own workflowstore.
You can subclass it and override getConnection()
2. When I generate my tables for JDBCWorkflowStore there are some constaints set that demands os_user-table to be involved. Hani - you said OSWorkflow did not require OSUser - how do I get around this?
What
happens if I just remove the constraint? Whats best practice?
Yep, you can just remove them,
---------------------------------------------------------------------
-- ******************************* Ing. Luca Masini Software Engineer
Gruppo Cassa
Infogroup S.p.a. Via delle Panche, 140 50141 Firenze Tel. 055.436.5644 Fax. 055.436.5658 ICQ# 137094359 e-mail l.ma...@infogroup.it *******************************





