On Thu, 15 Jun 2000, Neeme Praks wrote:
>
> This is a little bit related to the WAP issue brought up and it is also
> related to my real-life needs.
>
>
> PSML could contain information about all the services available on the
> site. All the services are pluggable in the sense, that you can plug out
> all the services from the portal and it would still work (you can log
> on, but there is no content). Also, you can add services later on to the
> portal.
>
I like the idea of this being pluggable. We probably need more discussion
as to how this would look before we cut any code.
It would be very easy with the current state of development to get things
intertwined into a monolithic application where everything depends on
everything else. This, IMHO, is a maintainence nigthmare.
When I started iCalendar development with the eye on a web-based calendar
and then eventually writing valid iCalendar. I tried hard not to tie
myself into Jetspeed internals where it wasnt necessary. It wasnt that
hard as the problem spaces Kevin was dealing with were much different than
those that I had been working on.
Anyway, with the pluggable service, side projects, such as iCalendar and
project can be easily spun off as they grow and mature. As long as
Jetspeed has a hook for the services Jetspeed can still utilize that code.
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]