>From: "Mike Kienenberger" <[EMAIL PROTECTED]> > > Facelets has code to distinguish between JSF 1.1 and JSF 1.2. > > com.sun.facelets.util.FacesAPI. > > https://facelets.dev.java.net/source/browse/facelets/src/java/com/sun/facelets/u > > til/FacesAPI.java >
Ah, looking at the API signatures is a good way to tell the difference between the JSF versions. In addition I need to find the version of myfaces to address the change in the view root between 1.1 and greater. Any ideas? > As Kito mentioned, it also came up at one point that this should be > part of the JSF API. > I agree that should be part of the API. It looks like the 1.2 RI has the beginnings of this, "com.sun.faces.config.JSFVersionTracker". Another thing that really bugs me is that the state marker is not standardized. Good gravy, what's up with that? com.sun.faces.saveStateFieldMaker ~com.sun.faces.saveStateFieldMarker~ <!--@@JSF_FORM_STATE_MARKER@@--> I haven't looked to see what myfaces 1.2 is going to use... I'd also like to see a better strategy for allowing multiple view composition technologies to co-exist. The single suffix is to limiting. It would also be nice if there was a standard API for how JSP tags keep track of their components and parents. With this we might be able to mix types of templates. Use a rich solution for defining the layout but still be able to use jsp fragments. Gary > > > ---------- Forwarded message ---------- > From: Jesse Alexander (KBSA 21) > Date: Oct 28, 2005 9:15 AM > Subject: RE: How to find out which implementation is running > To: MyFaces Discussion , [EMAIL PROTECTED] > > > Well... > > I see two alternatives: > > 1) We add one/two method to javax.faces.application.Application > eg. getImplName() and getSpecVersion() > But that would require a spec change... > > 2) We ask that at startup one of the implementation classes adds > the information as a managedBean or a external-context variable > This could be added also without a spec change, just need to > agree with the RI-people on an identifier to use... > > regards > Alexander > > > -----Original Message----- > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > Sent: Friday, October 28, 2005 4:07 PM > To: MyFaces Discussion > Subject: Re: How to find out which implementation is running > > Good question. > > If you devise something like this, there should also be a way to check > for the spec version of the jsf implementation running. > > regards, > > Martin > > On 10/28/05, Jesse Alexander (KBSA 21) > wrote: > > Hi > > > > When I want to write a component that must run under more than > > JSF-implementation, > > I often should know (runtime not development time) which > implementation > > is running, in > > order to use the correct base-classes. > > > > Has somebody devised a clever method to find out which JSF-runtime is > > active? > > Or should we add something to enable this? > > > > regards > > Alexander > > > On 3/6/07, Gary VanMatre wrote: > > > > I've been trying to determine a better strategy for detecting the supplier > > and > version of the JSF runtime. This has to do with a open JIRA ticket [1]. I > attempted to create a utility class to determine the implementor of the > runtime > and the JSF spec version [2]. This was a real hack but I didn't see a better > way > and I'm still not sure the best way to dynamically extract this version > information. Besides knowing the JSF version (1.1, 1.2), we need the > implementation version (myfaces 1.1, 1.3...). I was thinking about trying to > read the manifest but haven't figured out a good method. This seems like it > should be part of the JSF API? > > > > > > Any ideas? > > > > Gary > > > > > > [1] https://issues.apache.org/struts/browse/SHALE-418 > > [2] > https://svn.apache.org/viewvc/shale/framework/trunk/shale-clay/src/main/java/org > > /apache/shale/clay/utils/JSFRuntimeTracker.java?view=markup
