You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Angeles Sorano <an...@yahoo.com.ar> on 2003/10/01 22:47:56 UTC
Velocitystruts - Urgent -
Please, I want to ask you some questions :
1. what do you think about VelocityStruts? technical
advantages and disadvantages???
2. what do you think about Dolphin 1.2? technical
advantages and disadvantages???
==>>>can they have a comparation?
3. Do you know if StrutsTestCase for JUnit is
compatible with the VelocityStruts's architecture?
or VelocityStruts has a own JUnitTest like
"VelocityStrutsTestCase"? I ask you this because, in
my opinion, the Test is an important part of the
application deploy.
Thank you very much and I am waiting your anwsers very
quickly because this comments will help me at my work.
Angeles Sorano
pd: and sorry for my english, I am practicing....:)))
------------
Internet GRATIS es Yahoo! Conexión
4004-1010 desde Buenos Aires. Usuario: yahoo; contraseña: yahoo
Más ciudades: http://conexion.yahoo.com.ar
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org
Re: Velocitystruts - Urgent -
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Friday, October 3, 2003, at 02:43 PM, Ted Husted wrote:
>>
>
> I find that the Velocity Tools for Struts works as well, or better,
> with Struts than another other presentation technology, bar none.
Really?
> In fact, most of the tools work just as well with any other framework
> you might care to name.
>
> So, the question comes down to whether to Velocity or not to Velocity.
>
> Here's a list of advantages that I've been meaning to post:
>
> Velocity is transparent
>
> To other tools, Velocity markup appears as static text or comments. If
> you have well-formed documents now, you can add Velocity markup and
> have well-formed server pages. Server pages using Velocity can be
> validated by off-the-shelf tools like HTML Tidy and maintained with
> off-the-shelf editors, like FrontPage, Dreamweaver, or whatever else
> you already use.
>
> Velocity is cross-platform
>
> Velocity is available for both Java and .NET. No matter what the
> future holds for your team, your investment in Velocity can be
> preserved.
>
> Velocity is simple
>
> Most developers can review the Velocity documentation and examples in
> the morning and put it to work that very afternoon. It's been
> well-said that Velocity is "an API that fits on the back of a
> matchbook cover".
>
> Velocity is fast
>
> Fast in development, fast in production. Milestone tests show that
> Velocity templates render faster than other alternatives, like Java
> ServerPages.
>
> Velocity is MVC compliant
>
> Most application frameworks now promote the M-V-C design pattern.
> Velocity is designed from the ground-up to provide the View and
> expects that another component to provide the Model. Velocity is
> directly supported by all popular MVC frameworks, including Maverick,
> Struts, and WebWork. If you are using a MVC framework of your own,
> Velocity is sure to integrate easily with your Controller.
>
> Velocity is mature, stable, and actively supported
>
> Velocity 1.0 shipped in 2001 and Velocity 1.4 shipped in 2003. In
> between, the Velocity team has steadily improved the Velocity
> internals without making dramatic changes to the Velocity API. The
> best only gets better.
>
> Velocity is extensible
>
> VelociMacros make it easy for your page developers to create whatever
> custom controls your pages may need. VelocityTools make it easy for
> your code engineers to expose server-side components to your pages.
>
> Velocity is XML ready
>
> Velocity DVSL makes it easy to render XML documents as server pages.
> DVSL looks and feels like XLST, but uses the Velocity syntax.
>
> Glad you asked. :)
Wow. From Ted "JSP" Husted no less!
Seriously - do you mind if we post this on the site?
>
> -Ted.
>
>
>
> --
> Ted Husted,
> Junit in Action - <http://www.manning.com/massol/>,
> Struts in Action - <http://husted.com/struts/book.html>,
> JSP Site Design -
> <http://www.amazon.com/exec/obidos/ISBN=1861005512>.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>
>
--
Geir Magnusson Jr 203-247-1713(m)
geirm@optonline.net
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org
Re: Velocitystruts - Urgent -
Posted by Ted Husted <hu...@apache.org>.
Angeles Sorano wrote:
> 3. Do you know if StrutsTestCase for JUnit is
> compatible with the VelocityStruts's architecture?
> or VelocityStruts has a own JUnitTest like
> "VelocityStrutsTestCase"? I ask you this because, in
> my opinion, the Test is an important part of the
> application deploy.
Yes, StrutsTestCase works the same for Velocity. Though I find Canoo
Webtest to be nearly as helpful, especially if your other layers are
fully tested.
> Please, I want to ask you some questions :
> 1. what do you think about VelocityStruts? technical
> advantages and disadvantages???
I find that the Velocity Tools for Struts works as well, or better, with
Struts than another other presentation technology, bar none. In fact,
most of the tools work just as well with any other framework you might
care to name.
So, the question comes down to whether to Velocity or not to Velocity.
Here's a list of advantages that I've been meaning to post:
Velocity is transparent
To other tools, Velocity markup appears as static text or comments. If
you have well-formed documents now, you can add Velocity markup and have
well-formed server pages. Server pages using Velocity can be validated
by off-the-shelf tools like HTML Tidy and maintained with off-the-shelf
editors, like FrontPage, Dreamweaver, or whatever else you already use.
Velocity is cross-platform
Velocity is available for both Java and .NET. No matter what the future
holds for your team, your investment in Velocity can be preserved.
Velocity is simple
Most developers can review the Velocity documentation and examples in
the morning and put it to work that very afternoon. It's been well-said
that Velocity is "an API that fits on the back of a matchbook cover".
Velocity is fast
Fast in development, fast in production. Milestone tests show that
Velocity templates render faster than other alternatives, like Java
ServerPages.
Velocity is MVC compliant
Most application frameworks now promote the M-V-C design pattern.
Velocity is designed from the ground-up to provide the View and expects
that another component to provide the Model. Velocity is directly
supported by all popular MVC frameworks, including Maverick, Struts, and
WebWork. If you are using a MVC framework of your own, Velocity is sure
to integrate easily with your Controller.
Velocity is mature, stable, and actively supported
Velocity 1.0 shipped in 2001 and Velocity 1.4 shipped in 2003. In
between, the Velocity team has steadily improved the Velocity internals
without making dramatic changes to the Velocity API. The best only gets
better.
Velocity is extensible
VelociMacros make it easy for your page developers to create whatever
custom controls your pages may need. VelocityTools make it easy for your
code engineers to expose server-side components to your pages.
Velocity is XML ready
Velocity DVSL makes it easy to render XML documents as server pages.
DVSL looks and feels like XLST, but uses the Velocity syntax.
Glad you asked. :)
-Ted.
--
Ted Husted,
Junit in Action - <http://www.manning.com/massol/>,
Struts in Action - <http://husted.com/struts/book.html>,
JSP Site Design - <http://www.amazon.com/exec/obidos/ISBN=1861005512>.
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org
Re: Velocitystruts - Urgent -
Posted by Simon Christian <si...@stoutstick.com>.
I can't provide useful answers, but I'm fairly confident that a
comparison between VelocityStruts and Dolphin 1.2 would be a tricky
thing to do, given the latter is a (hugely expensive) chip design
application!!
- s
Angeles Sorano wrote:
> Please, I want to ask you some questions :
> 1. what do you think about VelocityStruts? technical
> advantages and disadvantages???
> 2. what do you think about Dolphin 1.2? technical
> advantages and disadvantages???
> ==>>>can they have a comparation?
> 3. Do you know if StrutsTestCase for JUnit is
> compatible with the VelocityStruts's architecture?
> or VelocityStruts has a own JUnitTest like
> "VelocityStrutsTestCase"? I ask you this because, in
> my opinion, the Test is an important part of the
> application deploy.
>
> Thank you very much and I am waiting your anwsers very
> quickly because this comments will help me at my work.
>
> Angeles Sorano
>
> pd: and sorry for my english, I am practicing....:)))
>
>
>
> ------------
> Internet GRATIS es Yahoo! Conexión
> 4004-1010 desde Buenos Aires. Usuario: yahoo; contraseña: yahoo
> Más ciudades: http://conexion.yahoo.com.ar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org