Answer:
http://struts.apache.org/faqs/kickstart.html#jsf


> -----Original Message-----
> From: Seetamraju, Uday [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 02, 2004 11:46 AM
> To: Struts Users Mailing List
> Subject: JSF and non-struts controllerServlets
> 
> 
> (If JSF can work with Struts controller, then someone here 
> can give me tips).
> 
> I am asked to upgrade an application that is based on the 
> circa-2001 Model 2 JSP/controllerservlet architecture.
> Given the amount of JSP work, I am strongly proposing (here 
> in my company) to switch to JSF.
> I have a spent only a little time with the "Core JSF" book.
> 
> I didn't find anything that helped me with my most important 
> questions.
> 
> If I used the JSF tags in my JSPs, and included the JSP 
> taglibs and JARs, I strongly feel the JSP will paint well. 
> But when a button is clicked, the above mentioned Model-2 
> based ControllerServlet will pick up the HTTP-PUT/request. 
> From there on, its the old world again, until its time to set 
> the HTTPRequest and HTTPSession for painting the next JSP (I 
> want this to use JSF too).
> 
> (1) In order to use #{bean.property}
> 
> in the JSP, can I have the old word Handler code do as :- ?
> 
> request.setAttribute("bean", beanref);
> 
> (2) Since I won't be able to use the JSF's XML configuration, 
> I would like to confirm that, the application can use its own 
> 'nextpage' framework as is, with JSF-based JSPs.
> 
> 
> Do you know of anything big that I am missing?
> I have ben leaning too far from the current implementation 
> here, without solid foundation/understanding of how JSF can 
> be paired with any controller (I have heard about this many 
> many times now).
> So, hoping someone can point me in the right direction.
> 
> Thanks a million.
>  
>  
>  
> --------------------------------------------------------
> The information contained in this message is intended only 
> for the recipient, and may be a confidential attorney-client 
> communication or may otherwise be privileged and confidential 
> and protected from disclosure. If the reader of this message 
> is not the intended recipient, or an employee or agent 
> responsible for delivering this message to the intended 
> recipient, please be aware that any dissemination or copying 
> of this communication is strictly prohibited. If you have 
> received this communication in error, please immediately 
> notify us by replying to the message and deleting it from 
> your computer.
>  
> Thank you,
>  
> Standard & Poor's
>  
> --------------------------------------------------------
> 
>  
>  
>  
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to