I've very much enjoyed Taestry 5.2, because I like the component-level
MVC approach, but it's a bit complex for trivial sites (I still use it
because I'm used to it), but it's really stellar for larger-scale
sites with lots of reusable components, etc. And it's getting faster
and cleaner all the time.
But I come from a WebObjects background, so the tapestry approach
(which was inspired of that ilk) makes sense to me.
Christian
On Jul 15, 2010, at 10:17 AM, Steve wrote:
It seems like this app would be a simple CRUD application, perhaps
later on tie into enterprise services. If I understand the scope
correctly, why not use the web profile on EE6 (glassfish 3). You can
use JPA entities as the model, Session beans to provide REST
endpoints (controller), and HTML with JavaScript (dojo, jquery, etc)
to provide the view. IMHO, this is simpler, easier to maintain
(someone coming behind you will likely know the technologies or can
learn quickly), and sets you up to scale easily. If you stick with
JAX-RI, you'll rarely need to use servlets or even jsp.
Cheers,
Steve
--
You received this message because you are subscribed to the Google
Groups "The Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/javaposse?hl=en
.
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
