re: Case Study: XMLC vs. Velocity

It funny to find out that other developers have the same acceptance
problems
with XMLC. The company I worked for started our project about four years
ago. It was the first web-project and there for we have the free choice
of the technologie. We start with Servlet/JSP but I switched to XMLC in
early 2001. Meanwhile a bunch of other web-related project starts and
guess what - not one of them uses (or reuses) our existing, well tested
XMLC framework. They prefer JSP/Taglib or XSLT because of the complexity
of DOM navigation and all the arguments you figure out... 
...and run into a lot of problems. As we compare the stability and the
performance of the different web-apps/web-app-technologies we figure
out, that the XMLC way seams to be harder for the developers (in the
beginning), but the result is a high performance and really stable
web-app.
Meanwhile our project becomes a "development platform standard" and new
projects has to follow the XMLC way :)

Stefan Flick <stefan@xxxxxxxxx>
> -----Ursprüngliche Nachricht-----
> Von: xmlc-admin@xxxxxxxxxxx [mailto:xmlc-admin@xxxxxxxxxxx] Im Auftrag
von
> David Corbin
> Gesendet: Montag, 15. September 2003 23:45
> An: xmlc@xxxxxxxxxxx; David H. Young
> Cc: Matthew Hixson
> Betreff: Re: Xmlc: Case Study: XMLC vs. Velocity
> 
> On Monday 15 September 2003 10:38, David H. Young wrote:
> Well, in our shop, the designer happens to be a programmer too.  In
that
> sense, we're not taking full advantage of XMLC :)
> 
> One developer that griped (he's not on this project anymore) is an
XPath,
> but
> not XSLT guy (some of the time).  He just thinks it's too disconnected
> when
> compared to JSP.  All the other developers, as far as I know are not
> XSLT/XPath people.
> 
> But, I agree with you that xslt is hard to wrangle with.
> 
> > I've heard similar stories.  xmlc requires a lot of internal
evangelism
> > since there's little supporting material.  A big part of it, I'm
> > convinced, is appreciating the needs of a non-programmer designer as
> > being just as important as the developer who implements the page.
That
> > was what it was designed for.  My wife would call it a "control
issue."
> :}
> >
> > I'm curious if your colleagues also do xslt/xpath development and
> > somehow they "get that?"  I find it much more mysterious than
xmlc...
> > and yet it seems to be no problem for folks to make the leap between
jsp
> > and xslt.