Hey Shawn, do you mean that you have been able to use JSF tags in the decorador page? I would like to know all the steps needed to do it. Because this is a topic of interest to the SiteMesh community. A question, why use JSF instead JSP for the decorator pages. Besides, I put all my decorator pages inside /WEB-INF/jsp/common/sm path, this way I protect this pages.
________________________________ De: Bobby Rosenberger [mailto:[EMAIL PROTECTED] Enviado el: Wednesday, December 19, 2007 12:31 PM Para: MyFaces Discussion Asunto: Re: Has anybody integrated Sitemesh+JSF/Tomahawk? Hey Shawn, It's working! That last round was my error - I neglected to include an f:view in my decorator. Thanks for your assistance and timely responses Shawn. Your help encouraged me to continue trying to get this working when I would have otherwise given-up and not used jsf tags in my site-mesh decorators. Which would have greatly reduced its benefits. To All: The directions found at http://jira.opensymphony.com/browse/SIM-201 for using the JSF View Handler for SiteMesh are unclear or out-of-date... not sure who might be able to update those, but it seems like it would be a worthwhile effort. Being able to use sitemesh along with JSF tags is a powerful combo. Thanks again Shawn. Bobby On 12/18/07, Bobby Rosenberger <[EMAIL PROTECTED] > wrote: Hey Shawn, ok, I've followed your method of dropping the climbingrose stuff into my projects source and gotten it to compile... and made the appropriate changes in the web.xml and faces config. I also added a simple <h:outputText value="HELLO!!"/> to my main decorator.jsp... as far as I can tell, it is just being ignored. Any thoughts? On 12/14/07, Garner, Shawn <[EMAIL PROTECTED] > wrote: I don't think I ran any ant files. I just unzipped the source into my project source directory probably, unzipped the view handler into my source, resolved any compilation errors by adding sitemesh dependency jars, then you have to rengister the viewhandler in your faces config. I don't have the project in front of me right now. I'll look at the project tonight. Shawn ________________________________ From: Bobby Rosenberger [mailto: [EMAIL PROTECTED] Sent: Friday, December 14, 2007 2:05 PM To: MyFaces Discussion Subject: Re: Has anybody integrated Sitemesh+JSF/Tomahawk? Hey Shawn, I tried, unsuccessfully, to get his working. I'm certain I'm missing something simple, because I see where you posted saying you got it working using the same version numbers of everything that I use. The part of the directions that seems to have more steps than indicated was: "+ You can drop the unzipped folder in sitemesh source folder and do a rebuild." I downloaded the source code for sitemesh, and dropped the climbingrose stuff in the sitemesh/src directory and ran the sitemesh ant build script... the climbingrose stuff was not included. I assume some changes have to be made to the build.xml? Or have I gone down the wrong path altogether? If I move the climbingrose stuff into the sitemesh/src/java directory I get compile errors... Any words of wisdom for me? Thanks, Bobby De: Garner, Shawn [mailto: [EMAIL PROTECTED] Enviado el: Wednesday, December 12, 2007 9:15 AM Para: MyFaces Discussion; MyFaces Development Asunto: RE: Has anybody integrated Sitemesh+JSF/Tomahawk? Check this out if you want to use sitemesh: http://jira.opensymphony.com/browse/SIM-201 -----Message Disclaimer----- This e-mail message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply email to [EMAIL PROTECTED] and delete or destroy all copies of the original message and attachments thereto. Email sent to or from the Principal Financial Group or any of its member companies may be retained as required by law or regulation. Nothing in this message is intended to constitute an Electronic signature for purposes of the Uniform Electronic Transactions Act (UETA) or the Electronic Signatures in Global and National Commerce Act ("E-Sign") unless a specific statement to the contrary is included in this message. While this communication may be used to promote or market a transaction or an idea that is discussed in the publication, it is intended to provide general information about the subject matter covered and is provided with the understanding that The Principal is not rendering legal, accounting, or tax advice. It is not a marketed opinion and may not be used to avoid penalties under the Internal Revenue Code. You should consult with appropriate counsel or other advisors on all matters pertaining to legal, tax, or accounting obligations and requirements. La informacin de este mensaje y sus anexos son propiedad exclusiva de Axede S.A. Es nicamente para el uso del destinatario intencional y pueden contener informacin de carcter privado o confidencial. Le informamos que cualquier revisin, retransmisin, divulgacin, copia o uso indebido del mismo est estrictamente prohibida y ser sancionada legalmente. Information contained in this message and every attachment is property of Axede S.A. Only the destiny user is able to make use of the data here contained, which is private and/or confidential. Any revision, broadcasting, spreading, copy or illegal use of this information is strictly prohibited and will be sanctioned by legal means.
