Re: JDBCWorkflowFactory

"Philipp Hug" <[email protected]>
Newsgroups gmane.comp.java.open-symphony.devel
Message-ID <024f01c31ae0$7d7d5c70$340112ac@zeus>
ok, it's in jira and some very basic docs on jira

----- Original Message ----- 
From: "Pat Lightbody" <[email protected]>
To: "Philipp Hug" <[email protected]>;
<[email protected]>
Sent: Wednesday, May 14, 2003 11:11 PM
Subject: Re: [Opensymphony-developers] JDBCWorkflowFactory


> Sure! Can you create a JIRA issue for this and put some docs for it in the
> Wiki?
>
> -Pat
>
> ----- Original Message -----
> From: "Philipp Hug" <[email protected]>
> To: <[email protected]>
> Sent: Tuesday, May 13, 2003 4:43 AM
> Subject: [Opensymphony-developers] JDBCWorkflowFactory
>
>
> > I wrote a little class to store workflow definitions in a jdbc database.
> > The implementation is very simple at the moment: Currently I'm just
> storing
> > the XML file in a blob.
> > This is the HSQLDB "create table" command:
> > CREATE CACHED TABLE OS_WORKFLOWS(WF_DEFINITION BINARY,WF_NAME
VARCHAR(256)
> > NOT NULL PRIMARY KEY)
> >
> > Features planned:
> >  versioning support,
> >  find alternative to storing xml directly
> >  delete function
> >
> > Is anyone interested in having this class in oswf cvs?
> >
> > philipp
> >
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Opensymphony-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-developers
>
>



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.