There's currently an open issue for this: http://issues.appfuse.org/browse/APF-484
If you'd like to attempt to do it, you could start with AppFuse Light since it's a bit simpler. Or you could use AppFuse, we'd be happy to accept a patch. My original plan was to use the RI since MyFaces didn't have support. As far as which is better, I'm inclined to stick with MyFaces, but I'm fine with using the RI if you get that working. Matt On 5/22/07, Steve Tynor <[EMAIL PROTECTED]> wrote:
I will soon need to integrate my appfuse based JSF project with some classes that were developed for facelets via the JSF 1.2 spec. Appfuse is currently wired to use the myfaces 1.1.5 and these 1.2 classes don't compile due to changes in the API. I seem to have two choices: modify these new classes to work with JSF 1.1 instead of 1.2, or modify the appfuse based code to use 1.2 instead of 1.1. The former doesn't seem like a good long term strategy and anyway I'd prefer to treat them as a library - i.e., all things equal, I'd prefer to change Appfuse to work with 1.2 rather than have to hack this library to work with 1.1. The Myfaces project just announced that they've unofficially passed the 1.2 TCK - so they'll probably be releasing a myfaces 1.2 "real soon now". The Sun reference implementation has been available for about a year. It's not clear to me what other dependencies that Appfuse/JSF uses will need to be adapted and which will "just work" (facelets appears to work with either 1.1 or 1.2, but I'm not sure about the rest): ajax4jsf jsf-facelets el-api el-ri corejsf-validator tomahawk Has anyone else been down this path? Can you advise me on my least painful path? Thanks, Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
