Return-Path: Delivered-To: apmail-struts-user-archive@www.apache.org Received: (qmail 58475 invoked from network); 2 Dec 2004 20:59:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Dec 2004 20:59:57 -0000 Received: (qmail 82039 invoked by uid 500); 2 Dec 2004 20:59:38 -0000 Delivered-To: apmail-struts-user-archive@struts.apache.org Received: (qmail 82019 invoked by uid 500); 2 Dec 2004 20:59:38 -0000 Mailing-List: contact user-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list user@struts.apache.org Received: (qmail 82006 invoked by uid 99); 2 Dec 2004 20:59:38 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of dakota.jack@gmail.com designates 64.233.184.192 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.192) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 02 Dec 2004 12:59:36 -0800 Received: by wproxy.gmail.com with SMTP id 67so328579wri for ; Thu, 02 Dec 2004 12:59:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=SaSaAG1lVBzS2cioA5IQb7/NByymyfh6WrBnaz2XFzac6ACjjrJAX2jBvCh+31k8HTqeiomHOj42xpPcF2WohrmLgJPhxmOCVViLxOw5tWK5WDUMlhTtjttahQcX9WhU7KfUNjQJ+0a5117WdlLtD2Ug3lcJZliM20BF+83mHvY= Received: by 10.54.27.79 with SMTP id a79mr543977wra; Thu, 02 Dec 2004 12:59:32 -0800 (PST) Received: by 10.54.48.20 with HTTP; Thu, 2 Dec 2004 12:59:32 -0800 (PST) Message-ID: Date: Thu, 2 Dec 2004 12:59:32 -0800 From: Dakota Jack Reply-To: Dakota Jack To: Struts Users Mailing List Subject: Re: JSF and non-struts controllerServlets In-Reply-To: <36D954A57C3DE145935A0B4181CDD74802286690@nycmsx01.mhf2.mhf.mhc> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <36D954A57C3DE145935A0B4181CDD74802286690@nycmsx01.mhf2.mhf.mhc> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello, I think that you have to choose between a JSF controller and a controller in the sense you are discussing it. If I am not mistaken, the use of Struts together with JSF, for example, requires that when a request is presented to the web application it choose at the outset between Struts and JSF. As a consequence, if this is right, what you have in mind won't really work. I think that you cannot use the JSF stuff without using the JSF page based controller. (This is not to say that you cannot use traditional model 2 controllers in an environment where JSF is used. This is just to say that you have to choose JSF or model 2 when the request arrives and you cannot go to the model 2 controller then to JSF or vice versa, if I understand.) If that is wrong, someone should correct this misconception. Jack On Thu, 2 Dec 2004 13:46:23 -0500, Seetamraju, Uday wrote: > (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 > > -------------------------------------------------------- > > -- "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@struts.apache.org For additional commands, e-mail: user-help@struts.apache.org