> Serge Huber wrote:
>
> Hi all,
>
> We (my company) are currently evaluating JetSpeed, its weaknesses and
> strengths and I just have a few questions about future directions.
>
> 1) How do you see a more complete integration with the XML.apache.org
> framework?
This was already approved by the PMC. Integration should be happening
over the next 2 weeks. Just need to get the infrastructure setup.
> I remember reading in the todo list that XML integration was pretty
> high
> in the list of priorities and I was wondering what the new ideas on
> this
> are.
They are still there. Jetspeed 2.0 will fully embrace Cocoon 2.0. It
really wasn't possible to do this with the 1.x series. SiteMap and the
new offline infrastructure will really work out well :)
> Is this going to be done via a rewriting of the ECS code into
> using
> XML elements ? Or is it more interesting to do DOM creation directly ?
ECS will still be there. I don't want to remove the capability of ECS
Portlets. That said it will be a minority. XML creation will clearly
be the most popular way to push out content. I really see the Jetspeed
project becoming a way to pull/push XML subscriptions.
> 2) A lot of java web applications interact with EJBs. Are there any
> plans to integrate this into the framework (Turbine) ? Is there a
> possibility to integrate jonAs or another EJB open source container ?
Currently there are no plans. I think EJB is overkill for a lot of web
applications. Now that we have frameworks like Turbine/Castor etc as
alternatives we aren't required to use EJB.
Since a Portlet is just an interface it is possible to use EJBs under
Jetspeed but at this time there are no plans for the Jetspeed Engine to
use EJB.
> 3) In terms of user authentification, what about using something like
> JAAS to allow maximum flexibility of interfacing with login systems ?
> Maybe this could help the wap integration or other future systems
> (such
> as logging in via retinal scans into Jetspeed :))
I have no opinion here. It isn't a requirement for me to have such
massive/crazy authentication requirements. If someone wants to write up
a PROPOSAL I am sure we will all listen.
JAAS is fairly comprehensive. I am not sure if this would go under
Turbine authentication or replace it.
> Anyway, just a few thoughts, and to say that we would of course be
> interested in contributing ideas and code to the project in the next
> few
> weeks.
Sounds like a plan :)
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
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]
