Serge Huber wrote:
> 
> > > 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.
> 
> > 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 :)
> 
> Ok great. I take it you're also interested about WML possibilities in
> Jetspeed too ?

I am working on this now actually.  It isn't happening easily for one
reason or another.  There are some design issues with Turbine/ECS and
our PSML implementation isn't perfect.  This should be in 1.2b2.

> The biggest problem I see here is that it's not just a matter of changing
> the tag language, but already of reducing the content and offering another
> type of navigation (I have a Motorola WAP phone and almost all the sites
> require far too many steps to get the desired data).

Yes.  I think it will work fine within Jetspeed.  There are some really
amazing things we can do with RSS.  The Controller infrastructure will
allow really easy browsing of WML content.
 
> > 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.
> 
> Well I actually meant just changing the use of ECS to define XML tags. This
> way it's only a conversion of data output rather that a complete rewrite
> (unless this is what is indeed intended).

There are some base ECS elements that don't specify either HTML or XML. 
ClearElement/ElementContainer, etc.  From a minimum standpoint even if
you just want Jetspeed to push XML this can be used.  If you want to use
JSP/Webmacro/PHP, etc, you can still do this with a Portlet.
 
> > 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.
> 
> Ok, I didn't expect that either :) but I was just thinking about the best
> place for EJBs in the Jetspeed/Turbine framework. A lot of projects are
> trying to seperate content from display, and I think some people might be
> interested in interfacing with already existing EJBs to build enterprise
> front-ends.

Kevin

-- 
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]

Reply via email to