Jeff:
As I said as this thread began, I also have internal needs for such
functionality. I'm wondering if it would not make sense to make this a
Turbine module rather than simply a Jetspeed/iCalendar module? Or are your
designs are in effect the same.
My thought was to create a seperate table in which messages and send-times
are stored. I could provide methods for viewing, adding, and deleting items
in the table. In this way, the services would be available to other
applications besides scheduling.
Anyway, I have got the HelloWorld App running. To see how simple things
would be, I also experimented with creating a table in Turbine, then using
the DBConnectionPool to connect and view rows - wow that was simple! Pretty
Cool! I am also going to start looking at the Jyve source code to get an
idea of Turbine's use of the seperate module folders, classes, methods,
etc. (I usually get more from reading sample-code than from narrative). I
also need to read-up on ECS for generating HTML.
I am not familiar with UML diagrams, but could probably figure them out. I
also have some thoughts of my own on how I would structure the objects and
methods; I recognize, however, that you are more familiar with classes
offered by Turbine which may make my task simpler, so I appreciate your
plans.
Steve B.
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "JetSpeed" <[EMAIL PROTECTED]>
Sent: Friday, April 21, 2000 9:59 AM
Subject: Re: Suggestion for eCalendar: Use JAMES to send reminders
>
>
> On Fri, 21 Apr 2000, Steve Belt wrote:
>
> > Jeff:
> >
> > I'll take a stab at the reminder if nobody else is on it. I'm reading
the
> > Turbine documents, and I'll let you know how it goes. I will also
download
> > the latest Jetspeed from CVS so I have the correct lib/Turbine, etc.
> > versions. Once I make HelloWorld work, I'll look at the connection-pool
> > features in Turbine. From there - I hope - it should be simple to
implement.
> >
> > Steve B.
> >
>
> Steve,
>
> Nobody is currently working on that. Now what would be the best way to
> work this... Can you read UML diagrams? If so how about I write up a
> diagram on how these things should be laid out, including inheritance
> structure and methods for each class.
>
> I think this would be best as I have been knee deep in the specification
> for quite a while now. Since time seems to be of major importance for 1.2
> having you create directly from the spec would be duplication of effort.
>
> Fire me off an email when you get the HelloWorld example working, even
> before you get into the persistence mechanisms and pools, etc, and I will
> help you along
>
>
> Thanks in Advance
> Jeff Prickett
> [EMAIL PROTECTED]
>
>
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
