Re: [TM4J-users] TM4J project web site & XTM (was RE: new member)

[Gerd M. <Ger...@sm...>]

On Wed, 21 Nov 2001 23:25:34 +0100 (MET)
Florian Haas <f.g...@gm...> wrote:

> [Kal]
> > There are lots of options here:
> > 
> > XSLT only - good for static websites. May be restricted in functionality
> > JSP only  -  good for dynamic websites. Full access to API functionality 
> > but requires Java coding skills
> > JSP with XSLT - good for dynamic websites Full access to API. Styling
> > could 
> > be provided through XSLT without requiring Java coding.
> > JSP with Velocity - good for dynamic and static websistes. Potentially
> > full 
> > access to API (may require an interface layer between the Java API and 
> > Velocity - though that should be quite thin). Site developers can work 
> > without needing to know any Java - although some functionality might 
> > require quite a lot of scripting
> > JSP with Velocity and XSLT - Dynamic and static websites. Site developers 
> > don't need to know any Java. Velocity could be used to generate XML which 
> > is styled with XSLT.
> > [...]
> 
> Let me just pitch in one quick thought, as I'm really tired tonight and
> ought to get some sleep: what about Cocoon?

+1 from me. I've already built a simple TopicMap navigation tool
with TM4J on top of Cocoon. But to be honest, I don't know Velocity
very good, so I'm not sure about the pro's and con's. What I don't
like on JSP is the concept of writing Java Code in my HTML site.
Also, does it always need to be HTML when I use JSP ? Or is it also
possible to use XML ? I wouldn't like to be fixed on HTML. The
XML/XSLT approach it much flexible. E.g. we could print all the
stuff to PDF which is no problem with Cocoon.

Best Regards,
Gerd

--
________________________________________________________________
Gerd Mueller                                    ge...@sm...     
SMB GmbH                                  http://www.smb-tec.com