Because it's from Sun/JSR process. That doesn't make it the best, but since we are building java apps, then anything implementing a JSR is the standard...
Frank Russo Senior Developer FX Alliance, LLC > -----Original Message----- > From: Cosmin Bucur [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 08, 2005 12:39 PM > To: Tapestry users > Subject: Re: tapestry to JSF conversion > > > What makes JSF the standard ? 2 - 3 extra books published ? > > On 12/8/05, Leonardo Quijano Vincenzi > <[EMAIL PROTECTED]> wrote: > > Konstantin Ignatyev wrote: > > > Tapestry can be used to create portlets, and JSF > > > supports them too. > > > I think this kind of integration is enough. > > > I think that an attempt to mix T and JSF components on > > > the page does not worth the efforts. > > > > > The problem would be for people migrating from one framework to the > > other. I think the main point of concern would be JSF beans > - Tapestry > > pages integration ? That'd allow people to share variables > and stuff. > > > > Anyway, if someone bites *that* bullet it'd be nice. But as > Jesse say, > > just don't hope any committer have the time to check that now. > > > > -- > > Ing. Leonardo Quijano Vincenzi > > DTQ Software > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
