I think that if you're generating the userinterface using JSF, it doesn't really make much sense to transform it later on with Cocoon. In that case I'd stick completely with JSF itself. I could imagine the other use case where you generate JSF templates on the fly using Cocoon.
Kind regards, Robby -----Original Message----- From: Wendy Bossons [mailto:[email protected]] Sent: Thursday, December 17, 2009 3:35 PM To: [email protected] Subject: Re: Use Case for Cocoon with JSF? I take it no one can come up with a use case for Cocoon with JSF. . . so I will consider my rewrite as a new JSF application, without Cocoon. That seems to make the most sense. ..\Wendy Wendy Bossons Web Developer Contact Information: [email protected] 617-253-0770 On Dec 14, 2009, at 11:11 AM, Wendy Bossons wrote: > Hello, > > I am new to Cocoon . . . however, the project on which I'm now > working is Cocoon based and has a significant code base . . . I > would like to create a JSF frontend to this application, have been > given the go ahead to do so. > > As I begin, however, I'm finding only older resources on the web > regarding integrating JSF and Cocoon (circa 2004) . . . and in the > end, these end up back in the Cocoon pipeline as XML/XSL > transformations. So I'm wondering what's the use case for > integrating the two? My initial hope was to simplify the user > interface and to take advantage of the many features of some > extended JSF framework like IceFaces. > > Can someone speak to this idea ... what is the use case(s) for > moving to JSF if it all ends up in an XSL transformation in Cocoon? > Wendy Bossons > Web Developer > > Contact Information: > [email protected] > 617-253-0770 > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
