on 1/27/00 1:35 PM, Dave Cramer <[EMAIL PROTECTED]> wrote:
> Given that I have a marginal (very) understanding of turbine. I am not sure
> I can answer this question. But I will try, and perhaps learn a little about
> turbine.
>
> My understanding of turbine is that it implements a controller/view model.
No, it implements FreeEnergy in Java. But, there is no reason that you have
to go with that method. Turbine is also a collection of useful code that is
free for the using.
> Having briefly looked at it; I think it does alot more. This is the part
> that I am uncomfortable with. My discomfort comes from being forced into a
> specific way of dealing with databases. That being said, I like the idea of
> the controller view model, and would embrace this model.
There is no forcing to deal with databases in a specific way within Turbine.
Turbine comes with a very nice database connection pool, which can also be
wrapped around other pools, but there is nothing within Turbine that forces
you to use that pool.
Please don't make general statements without first discovering the facts. We
give you the source code so that you can do that.
> My view of the solution would then incorporate JSP to display the pages, and
> beans to communicate to the underlying servlet logic.
JSP sucks.
Here are a couple of reasons:
<http://www.servlets.com/soapbox/problems-jsp.html>
In the least, I would suggest methodology to use FreeMarker or Webmacro. We
just added alpha modules for Freemarker support.
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Site: http://www.working-dogs.com/freetrade/
Problems?: [EMAIL PROTECTED]
