Re: shale-tiger and jsf 1.2
I'd be grateful if someone could explain what is the proccess of shale-tiger starting up and reading the annotated beans. I mean I don't see any faces-config.xml in its jar. What class is supposed to try to start the process of scanning annotated classes? Is it somewhere in shale-core? Thanks Gregg Leichtman pisze: There appear to be some problems with MyFaces 1.2.0 or Tomcat 6.0.13 and JSF tags. For example see: http://article.gmane.org/gmane.comp.jakarta.myfaces.user/38651 This does not address your specific problem, but I ran into the above referenced problem immediately. Notice that the problem was reported yesterday. -= Gregg =- Tomasz Pasierb wrote: Hi, shale-tiger doesn't seem to work with myfaces 1.2 which has recenlty been released. I have a bean annotated with @Bean and it doesn't seem to be picked up. The bean doesn't exists when I try to get/set some properties on it using EL. Everything is fine with the bean when it's declared in faces-config.xml. Additionally no messages are logged by tiger even on debug level apart from the one that states that 'original variableResolver was wrapped...' Does shale-tiger work with jsf 1.2? (I've quickly skimmed through the sources and it seems that only DTDs for jsf 1_0 and 1_1 are allowed (FacesConfigParser#REGISTRATIONS) if that's what it's used for. I've configured my webapp according to the jee5 tutorial where they use schema for 1.2. May this be the reason why shale-tiger doesn't register the annotated beans?) Regards, Tom Pasierb
Re: shale-tiger and jsf 1.2
From: Tomasz Pasierb [EMAIL PROTECTED] I'd be grateful if someone could explain what is the proccess of shale-tiger starting up and reading the annotated beans. I mean I don't see any faces-config.xml in its jar. What class is supposed to try to start the process of scanning annotated classes? Is it somewhere in shale-core? Not shale-core but shale-view. The view library has a context listener registered in the META-INF/taglib.tld [1]. The listener tries [2] to load a complementing listener [3] in the tiger library. The context listener scans the classes for shale annotations. Later a variable resolver [4] in the tiger library uses the annotations to deliver managed beans. I think there has been some issues in the past with tiger and JSF 1.2 [5]. You might try explicitly declaring the packages to scan. I had a problem using OC4J in embedded mode. The web classpath /WEB-INF/classes was not avaiable when the context listeners loaded. context-param param-nameorg.apache.shale.tiger.SCAN_PACKAGES/param-name param-valueorg/acme/view/beans/param-value /context-param [1] http://svn.apache.org/viewvc/shale/framework/trunk/shale-view/src/main/resources/META-INF/taglib.tld?view=markup [2] http://svn.apache.org/viewvc/shale/framework/trunk/shale-view/src/main/java/org/apache/shale/view/faces/LifecycleListener.java?view=markup [3] http://svn.apache.org/viewvc/shale/framework/trunk/shale-tiger/src/main/java/org/apache/shale/tiger/view/faces/LifecycleListener2.java?view=markup [4] http://svn.apache.org/viewvc/shale/framework/trunk/shale-tiger/src/main/java/org/apache/shale/tiger/faces/VariableResolverImpl.java?view=markup [5] https://issues.apache.org/struts/browse/SHALE-345 Gary Thanks Gregg Leichtman pisze: There appear to be some problems with MyFaces 1.2.0 or Tomcat 6.0.13 and JSF tags. For example see: http://article.gmane.org/gmane.comp.jakarta.myfaces.user/38651 This does not address your specific problem, but I ran into the above referenced problem immediately. Notice that the problem was reported yesterday. -= Gregg =- Tomasz Pasierb wrote: Hi, shale-tiger doesn't seem to work with myfaces 1.2 which has recenlty been released. I have a bean annotated with @Bean and it doesn't seem to be picked up. The bean doesn't exists when I try to get/set some properties on it using EL. Everything is fine with the bean when it's declared in faces-config.xml. Additionally no messages are logged by tiger even on debug level apart from the one that states that 'original variableResolver was wrapped...' Does shale-tiger work with jsf 1.2? (I've quickly skimmed through the sources and it seems that only DTDs for jsf 1_0 and 1_1 are allowed (FacesConfigParser#REGISTRATIONS) if that's what it's used for. I've configured my webapp according to the jee5 tutorial where they use schema for 1.2. May this be the reason why shale-tiger doesn't register the annotated beans?) Regards, Tom Pasierb
Re: shale-tiger and jsf 1.2
There appear to be some problems with MyFaces 1.2.0 or Tomcat 6.0.13 and JSF tags. For example see: http://article.gmane.org/gmane.comp.jakarta.myfaces.user/38651 This does not address your specific problem, but I ran into the above referenced problem immediately. Notice that the problem was reported yesterday. -= Gregg =- Tomasz Pasierb wrote: Hi, shale-tiger doesn't seem to work with myfaces 1.2 which has recenlty been released. I have a bean annotated with @Bean and it doesn't seem to be picked up. The bean doesn't exists when I try to get/set some properties on it using EL. Everything is fine with the bean when it's declared in faces-config.xml. Additionally no messages are logged by tiger even on debug level apart from the one that states that 'original variableResolver was wrapped...' Does shale-tiger work with jsf 1.2? (I've quickly skimmed through the sources and it seems that only DTDs for jsf 1_0 and 1_1 are allowed (FacesConfigParser#REGISTRATIONS) if that's what it's used for. I've configured my webapp according to the jee5 tutorial where they use schema for 1.2. May this be the reason why shale-tiger doesn't register the annotated beans?) Regards, Tom Pasierb signature.asc Description: OpenPGP digital signature
