Thank you for the detailed reply, Craig. The reason I was hesitating going
whole hog into Shale was I was worried the functionality of Struts that I
have gotten used to may still be in an incumbent stage in Shale. However
since you state that JSF+Shale "has pretty much all the functional
features Struts 1.x" does (and more besides!), I guess this means you are
endorsing Shale's maturity (or features anyway).... Ok, I guess I know
what I will doing this weekend..:)
Thanks again!
Geeta
Craig McClanahan <[EMAIL PROTECTED]>
08/05/2005 02:30 PM
Please respond to
"Struts Users Mailing List" <user@struts.apache.org>
To
Struts Users Mailing List <user@struts.apache.org>
cc
Subject
{Spam?} Re: {Spam?} Re: [OT] What to choose: Struts, JSF, Shale or Spring
On 8/5/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Thank you for your response, Kevin. I was starting to think that too..
>
> However, I went back and listened again to Craig's talk in the
serverside
> Java Symposium (and that was only in March of this year):
> http://www.theserverside.com/symposium/presentations.html
>
> I understood him to say that using the integration library for
Struts+JSF
> apps was definitely a possible option... Tell you the truth, I am quite
> confused now about what we *ought* to do...(:(
>
> Geeta
Sorry for not being able to follow up on this thread.
Having worked with the integration library combining JSF and Struts
1.1, my conclusion is that it should be looked at as a transition
strategy, if you're going to migrate from Struts to JSF and can't
rewrite the entire app all at once -- not as the basis for new
application deveopment. The reasons for this:
* The resulting architecture when you combne them is complex
(front controller for JSF in front of a front controller for Struts)
* Redundancy between the frameworks means you'll spend the
rest of your maintenance time on this app deciding whether to
add a new screen via a Struts action or a JSF backing bean,
whether to use Struts validation or JSF validation, and so on.
I can try to address some of the current issues in the integration
library, but its not the right answer for new app development that
wants to use JSF -- for that, use JSF by itself or JSF+Shale. The
latter combination has pretty much all the functional features Struts
1.x has (including Tiles and Commons Validator) plus a bunch of other
niceties, so you don't need to combine JSF with Struts solely to get
access to existing Struts 1.x functionality.
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
CONFIDENTIALITY NOTICE:This email is intended solely for the person or
entity to which it is addressed and may contain confidential and/or
protected health information. Any duplication, dissemination, action
taken in reliance upon, or other use of this information by persons or
entities other than the intended recipient is prohibited and may violate
applicable laws. If this email has been received in error, please notify
the sender and delete the information from your system. The views
expressed in this email are those of the sender and may not necessarily
represent the views of IntelliCare.
