Moving from Struts to JSF is moving to a "more defined" framework? That is pretty difficult to grasp. Could you explain?
On 9/6/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On 9/6/05, Walton, Kaleb (ISS Southfield) <[EMAIL PROTECTED]> wrote: > > > > Hey all, > > > > As I had mentioned in a previous post, our team is looking to move > > towards a more well defined web framework. From my limited experience > > using Shale (ran the shale-use-cases) I'm not feeling very confident > > that we could use it *right away*. > > > > I wanted to ask for opinions on what would be a gradual step for us to > > take towards the Shale framework (once it's stable enough to use in a > > production environment). For example, would JSF + Spring be a good combo > > that would make for an easy transition to Shale? Struts + WebFlow + > > Spring? Etc.. > > > > Do the aforementioned framework combinations even matter? Will Shale > > just add another layer on top or glue together with what we would have > > already developed? Although I've been reading up on Shale quite a bit, > > my understanding is still limited so please excuse me if these questions > > are easily found through already documented sources. If they are, please > > share where they can be found :) > > > > The key to choosing a transition approach is what you want to use for the > "front controller" part of your architecture durng the interim. If you're > starting from Struts, a straightforward path would be to use the integration > library to start switching your pages to using JSF components instead of > Struts HTML tags (without having to modify your actions), followed by a > migration of the back-end logic to using JSF's front controller and request > processing lifecycle. > > If, on the other hand, you decide to commit to JSF's controller early rather > than late, you might as well just use Shale along with it from the > beginning. Unlike the way that other frameworks deal with JSF, Shale > *assumes* you will be using the JSF controller architecture, and it just > adds ease of use around problems you'll face anyway. It doesn't try to treat > JSF as purely a component architecture. > > Craig McClanahan > > Regards, > > Kaleb > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
