Simon, >From what I have read from Mathias' emails and from the Facelets site, Facelets allow the use of JSF 1.2 without a JEE 5/JSP 2.1 container. I have verified this by running MyFaces 1.2.3, Trinidad 1.2.9, and Facelets 1.1.14 together from the Oracle JDeveloper 10.1.3.3 IDE which does not have a JEE 5/JSP 2.1 container.
It is not well published that Facelets allows the use of JSF 1.2 without a JSP 2.1 container. However, as I have found, there can be some issues. I was wondering if anyone else found any issues in doing this. I would also be interested in hearing about anyone's experience migrating to JSF 1.2. -Richard On Thu, Sep 4, 2008 at 10:41 AM, Simon Lessard <[EMAIL PROTECTED]> wrote: > Hi Richard, > > You're actually asking two different questions: > 1. How to migrate to Facelets > 2. How to migrate to JSF 1.2 > > For Facelets, you pretty much have it already. > > For JSF 1.2, it's more complicated, first you have to run inside a JEE 5 > container as JSP 2.1 is required. Therefore, simply dropping the MyFaces and > Trinidad 1.2.x jars won't do the trick most of the times. Also, if you have > home made component, it would be very wise to convert their tags to JSP 2.1 > synthax in the TLD (using <deferred-value/>). > > You can the two parts in any order, but I would suggest doing Facelets in > JSF 1.1 environment first. > > > Regards, > > ~ Simon > > > On Thu, Sep 4, 2008 at 1:33 PM, Richard Yee <[EMAIL PROTECTED]> wrote: >> >> All, >> Can any of you share any tips on migrating from Trinidad 1.0.5 and >> MyFaces 1.1.5 to Trinidad 1.2.x, MyFaces 1.2.x, and Facelets? Aside >> from the switch from .jsp to .xhtml files and the facelets >> configuration, are there any code changes that are necessary? I ran >> into a problem with the Trinidad XML Menus and Facelets yesterday >> (Jira issue: TRINIDAD-1215) and want to know if there are any other >> side effects that I might run into. >> >> Thanks, >> >> Richard > >
