RE: DVSL

[Ron Wheeler <rw...@artifact-software.com>]

Thanks.

The lack of choices has never been the problem in the Jakarta area:-)
I am pretty sure that there is an evolution of the architectural thinking
and that new projects have come into existance to improve productivity and
encapsulate the underlying technologies into easier-to-use, high level
functions.

DVSL looks pretty attractive in theory and looks like a better way to
process XML in the Jetspeed enviroonment. Is it?
I would like to have the opinion of the experienced Jakarta insiders about
how this technology should be used and whether it is the "preferred" way to
handle XML. Is it a strategic part of Jakarta with the same standing as
XALAN in terms of functional extensions and bug  fixes?

A really nice document for the site would be a marketing brochure on the
Jakarta "product line" to help managers understand the choices available and
help outsiders make the best use of the technology. I have found it somewhat
difficult to understand how all the parts interrelate and to extract out an
architecture that is productive, consisting of components that will continue
to be enhanced and supported.

I hope that the use of the word marketing does not get me banned from the
site. I do appreciate that the key people who would have to write this are
also the guys who are taking the time to help me and others while actually
making all the wonderful tools for us.

Ron


-----Original Message-----
From: Weaver, Scott [mailto:Sweaver@rippe.com]
Sent: Thursday, August 07, 2003 11:07 AM
To: 'Jetspeed Users List'
Subject: RE: Velocity vs JSP


> How many people are shifting from XSLT to DVSL?
> I am just getting reasonably comfortable with XSLT (have done a couple of
> multi-document navigations) but if DVSL/Velocity/Jetspeed is a good

As of Jetspeed 2, there is no marriage to any specific technology or
framework in project.  You are free to choose the technology that suits you
best like Struts with JSTL or VelociTags,  Turbine with Velocity or JSP or
maybe even Tapestry which is devoid of a templating language entirely!  The
ideals behind Jetspeed is to make it, combined with the Pluto container, THE
defacto open source portal, JSR-168 or otherwise.  We are adhering very
closely to as many J2EE technologies including JMX for management and
possibly JAAS for security.

> We will try to share our "Jetspeed for
> Dummies" documentation once we get a bit further on and get it into a
> format
> that we could have used when we started.

Any contributions of documentation or otherwise are always welcome.



*===================================*
* Scott T Weaver                    *
* Jakarta Jetspeed Portal Project   *
* weaver@apache.org                 *
*===================================*
 


> -----Original Message-----
> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> Sent: Thursday, August 07, 2003 10:49 AM
> To: Jetspeed Users List
> Subject: RE: Velocity vs JSP
>
> Nick Bauman seemed pretty convinced from the case study.
>
> I will continue to focus on Velocity. It does seem easier to understand
> and
> I think that I can build frameworks that my staff (not all  programmers
> but
> very smart) can modify with great predictabilty of outcome.
>
> How many people are shifting from XSLT to DVSL?
> I am just getting reasonably comfortable with XSLT (have done a couple of
> multi-document navigations) but if DVSL/Velocity/Jetspeed is a good
> reliable
> architecture, I would just as soon invest the time and effort there.
> The biggest problem is the documentation. It assumes too much of an
> understanding of the history and underpinnings of Jetspeed. Just sorting
> out
> the roadmap for the configuration files and determining how all the xreg
> vm
> pmsl files related was a pain. We will try to share our "Jetspeed for
> Dummies" documentation once we get a bit further on and get it into a
> format
> that we could have used when we started.
>
> Ron
>
>
>
>
> -----Original Message-----
> From: Weaver, Scott [mailto:Sweaver@rippe.com]
> Sent: Thursday, August 07, 2003 10:08 AM
> To: 'Jetspeed Users List'
> Subject: RE: Velocity vs JSP
>
>
> > If I have to prioritize my education (which -for better or worse -
> drives
> > the corporate strategy), should I focus on learning Velocity or learn
> how
> > to
> > use JSP?
>
> I use both JSP and Velocity but I am quite particular to Velocity.  The
> nice
> thing about Velocity is you don't need to "focus" on learning it.  It has
> a
> learning curve of about 2 to 3 hours and is so elegant and simple it's
> almost scary.
>
>
> > I reference to a white paper would be the best answer to this question.
>
> The Velocity site is the best the place to start, here is link to
> comparison
> of Velocity vs. JSP.
>
> http://jakarta.apache.org/velocity/casestudy1.html
>
> *===================================*
> * Scott T Weaver                    *
> * Jakarta Jetspeed Portal Project   *
> * weaver@apache.org                 *
> *===================================*
>
>
>
> > -----Original Message-----
> > From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
> > Sent: Thursday, August 07, 2003 9:44 AM
> > To: Jetspeed Users List
> > Subject: RE: Velocity vs JSP
> >
> > Thanks for the strategy and the code fragment.
> >
> > Without getting into theology, what is the current thinking about JSP
> > versus
> > Velocity?
> > As a latecomer to the server side development wars, we have done one
> > fairly
> > large and complex application in JSP and XML.
> > The Jetspeed framework looks like it might be easier and more productive
> > than continuing to develop our own portal architecture.
> > I was not the coder on the JSP/XML portal but I am getting more
> > technically
> > involved in the investigation of Jetspeed and Velocity.
> >
> > Bottom Line question
> >
> > If I have to prioritize my education (which -for better or worse -
> drives
> > the corporate strategy), should I focus on learning Velocity or learn
> how
> > to
> > use JSP?
> > I do not care about "working on my resumé" since I am way too old to
> make
> > a
> > living as a programmer. I am only trying to try to keep the company at
> the
> > most productive point of the technology spectrum.
> >
> > I reference to a white paper would be the best anwer to this question.
> >
> > Ron
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org