[prev in list] [next in list] [prev in thread] [next in thread] 

List:       velocity-user
Subject:    Re: frameworks, tools, and velocity Was: Re: accessing $session when
From:       Anthony Eden <aeden () signaturedomains ! com>
Date:       2004-05-26 13:49:27
Message-ID: 40B4A067.2080800 () signaturedomains ! com
[Download RAW message or body]

What kind of an advocate and project maintainer would I be if I didn't 
mention JPublish? ;-)

JPublish is based on the same design principals as Turbine.  Velocity 
was originally the only template language supported by JPublish, 
although now other template engines such as FreeMarker and WebMacro are 
also supported.  Actions (the logic which provides the glue between your 
view and your business logic) can be written in a variety of scripting 
languages or in Java.  JPublish supports global design templates so that 
designers can work on the site design without interferring with 
programmers or content producers.  Design templates also help reduce the 
amount of work needed to maintain a site design since design elements 
are applied to the site as a whole rather than on each page.

I've used JPublish for projects both large and small and have found that 
it works equally well in either case.  Granted it is not as simple as 
throwing together a small site with PHP, but with the included "starter" 
webapp which you can just expand and modify it is pretty easy to get 
small projects up to speed, and the payoff with the separation of 
concerns is worth it in my opinion.

Anyhow, enough evangelizing.  Give JPublish a try: 
http://www.jpublish.org/ .  It's open source and has a very open license 
(Apache-like).

Sincerely,
Anthony Eden

Nathan Bubna wrote:

>Gonzalo Diethelm said:
>  
>
>...
>  
>
>>* are well integrated with (or depend upon) Velocity
>>    
>>
>
>well, first there is Turbine.  it's *very* well integrated with Velocity, and
>a number of VelocityTools ideas were gleaned from them, though it does not
>itself work with VelocityTools.
>
>then there's Struts w/VelocityStruts.  while the Struts folks have not done
>much themselves to integrate with Velocity, we (VelocityTools) have certainly
>put in the effort to make the two work well together.
>
>there are also several frameworks which seem to have taken steps to integrate
>with Velocity on their own.  these include WebWork and Spring.  i have not
>used WebWork, but i've looked through their code and docs, and it appears
>solid.  my company has recently begun to use Spring with VelocityStruts,
>though i'm not presently working on that project.
>
>the other one i hear good things about is Maverick.  by all accounts it is
>very clean, well-designed framework (though perhaps with less features than
>the rest) that integrates well with pretty much any view layer.  i'm told it
>works great with VelocityTools.
>
>the other major java webapp frameworks i hear about are Tapestry and JSF.
>although JSF--being a spec--could be implemented in Velocity, it has not been,
>and from all i know of Tapestry, i believe that it neither does nor will ever
>have anything to do with Velocity.
>
>  
>
>>Let me rephrase the question under a hypothetical situation: for any of a
>>set of projects that you have to embark on (starting from scratch), please
>>comment on what tools (besides Velocity ;-) you would use. I would be really
>>interested in hearing any opinions for this question; for example:
>>
>>* for a big, enterprise-functionality project: Velocity, foo bar and, of
>>course, baz!
>>    
>>
>
>Turbine, Struts, WebWork, Spring, and Maverick would probably all work for
>these.
>
>  
>
>>* for a small, hobbyist-level project: Velocity, bifur, bofur and, usually,
>>bombur.
>>    
>>
>
>i haven't done this, but i've always figured i'd use VelocityView with
>Velosurf and if i needed a bit more convenience/power/features, then i might
>throw Maverick or parts of Spring into the mix to help out.
>
>  
>
>>* etc.
>>
>>    
>>
>>>actually, i haven't yet had the joy of building any java
>>>webapps small/simple enough to fit this category.
>>>      
>>>
>>And what combinations of tools (in addition to Velocity) have you (and
>>anybody listening) used in real life projects?
>>    
>>
>
>i've used Turbine (with Velocity as view layer), Struts+VelocityStruts, and as
>i said, my coworker has begun working with Spring+Struts+VelocityStruts,
>though i myself have done little work there.
>
>Nathan Bubna
>nathan@esha.com
>
>
>---------------------------------------------------------------------
>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

[prev in list] [next in list] [prev in thread] [next in thread]