Hi, When testing Apache MyFaces 2 with PrimeFaces2, I've realized that Facelets method rule api is implementation specific, so with mojarra it is com.sun.faces.facelets.tag.MethodRule and with myfaces it is org.apache.myfaces.facelets.tag.MethodRule Is there any specific reason why it hasn't been moved to standard API eg javax.faces.facelets.tag.MethodRule? -- Cagatay Civici JSF EG | PrimeFaces Lead | Apache MyFaces PMC http://www.primefaces.org

Hi, When testing Apache MyFaces 2 with PrimeFaces2, I've realized that Facelets method rule api is implementation specific, so with mojarra it is com.sun.faces.facelets.tag.MethodRule and with myfaces it is org.apache.myfaces.facelets.tag.MethodRule Is there any specific reason why it hasn't been moved to standard API eg javax.faces.facelets.tag.MethodRule? -- Cagatay Civici JSF EG | PrimeFaces Lead | Apache MyFaces PMC http://www.primefaces.org

On Fri, Jan 29, 2010 at 7:50 PM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: > This class is one of the prime candidates supporting the request to > reevaluate the decision as to which Facelets APIs would be made public. This > particular class has it's own spec issue, which at the moment is > unscheduled. > > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=595 > > Since this is a very commonly needed class, I recommend that it is promoted > as part of the 2.0 rev a release. I totally agree! > > -Dan > > On Fri, Jan 29, 2010 at 5:38 AM, Cagatay Civici <cagatay.civici(a)gmail.com&gt; > wrote: >> >> Hi, >> >> When testing Apache MyFaces 2 with PrimeFaces2, I've realized that >> Facelets method rule api is implementation specific, >> >> so with mojarra it is com.sun.faces.facelets.tag.MethodRule >> and with myfaces it is org.apache.myfaces.facelets.tag.MethodRule >> >> Is there any specific reason why it hasn't been moved to standard API eg >> javax.faces.facelets.tag.MethodRule? >> >> -- >> Cagatay Civici >> JSF EG | PrimeFaces Lead | Apache MyFaces PMC >> http://www.primefaces.org > > > > -- > Dan Allen > Senior Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://mojavelinux.com > http://mojavelinux.com/seaminaction > http://www.google.com/profiles/dan.j.allen > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf

On Fri, Jan 29, 2010 at 2:42 PM, Cagatay Civici <cagatay.civici(a)gmail.com&gt;wrote: > Agreed as well, otherwise every library(Trinidad, PrimeFaces ...) needs to > come up with it's own implementation which is the quick dirty workaround at > the moment. > If there are other APIs like MethodRule which are absolutely critical (meaning they are going to get duplicated right off the bat), please name them now or hold your peace until after rev a. We are looking for the absolutely critical here, because the goal is not to add a new features to JSF 2.0 but to fix what should be considered oversights.