> 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.
Sure, but that is why we have a scheduler api essentially. You can already access that
information without needing another table.
> 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!
Amazing eh? :-)
> 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.
Actually, don't use Jyve as an example any more. Jyve was always a quick hack. You
will want
to look at the turbine/examples directory and look at the templating languages in
there such
as Webmacro (my preference) and Freemarker.
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
--
--------------------------------------------------------------
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]
