Hello Kevin,
Committed the ICalendarErrorResources file that has that missing value.
Sorry for the bad builds. Cant seem to get ant working consistently hence
I am building most stuff by hand. Somewhere ant is having some problems in
my dev environment.
Seems to me we are at a decision bar with this iCalendar implementation.
On the one hand Exolab promises an iCalendar implementation in their
Intalio product. This is great because exoffice already has proven it
writes open source code with projects like castor. If they say it is going
to happen it probably will.
On the other hand, I cant run/debug/test that implementation because I
cant find the code. The machine shuffle.exolab.org just gives me a
forbidden prompt when I try to load a url there.
My proposal for the iCalendar implementation we currently have is this:
Finish everything but parsing and writing iCalendar streams ie build the
objects and tie them in with Castor for database persistence and stop
there. Wait for exolab if we need to write or read iCalendar streams.
My personal need is just for a web based calendar. I started implementing
parsing because it was helping me understand the bigger picture.
Plan Step by Step
1. Implement iCalendar properties
2. Implement the actual iCalendar objects
3. Tie the iCalendar objects, properties, and parameters to Castor and
Turbine users.
4. Write a web based calendar for jetspeed
Secondly, I would like to say here that when exoffice releases its
iCalendar implementation. I would work on step 4 again to tie it into
their particular object implementation.
Again, Sorry for the bad builds
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]
