Well, you could use reflection if from the tomahawk you check the version of JSF being used. But we are talking here about the opposite, in order to restore the view correctly the JSF implementation needs to know the version used by the artifact to know which behaviour to follow... tomahawk is based on 1.1, for instance and myfaces 1.2 needs to be aware of that...
Cheers, Bruno On 28/05/07, Martin Marinschek <[EMAIL PROTECTED]> wrote:
Reflection? Checking for method-names? regards, Martin On 5/28/07, Bruno Aranda <[EMAIL PROTECTED]> wrote: > Hi, > > For backwards compatibility, when restoring the view we need to know > if older (<1.2) ViewHandler and StateManager are used in order to fall > into 1.1 behaviour if they are older. The RI checks the faces-config > file of the artifact [1], inferring the version from the XML grammar > (name of the DTD or schema). If it is not the 1.2 schema, the > behaviour is the 1.1 one. Do you have a better idea on how to check > the version used in the implementation of an artifact (e.g. tomahawk)? > > The resulting error of not tracking the version can be observed when > running the sandbox with myfaces 1.2, in the convertNumber example. > > cd tomahawk/sandbox/examples > mvn -PjettyConfig clean jetty:run -Djsf=12 > > With the RI (-Djsf=ri12) this does not happen. > > Cheers, > > Bruno > > [1] https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=149 > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
