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: Integrating Shale with Facelets
This question really has nothing to do with Shale, you will probably get better responses to these questions on the facelets mailing lists. A couple of things to to check in your web.xml. In your web.xml you should have a context parameter saying what the suffix is for your documents !-- Use Documents Saved as *.xhtml -- context-param param-namejavax.faces.DEFAULT_SUFFIX/param-name param-value.xhtml/param-value /context-param also make sure in your web.xml that your urls are mapped to the facesservlet and that everything goes through the extension filter. !-- extension mapping for adding script/, link/, and other resource tags to JSF-pages -- filter-mapping filter-nameextensionsFilter/filter-name !-- servlet-name must match the name of your javax.faces.webapp.FacesServlet entry -- servlet-nameFacesServlet/servlet-name /filter-mapping !-- extension mapping for serving page-independent resources (javascript, stylesheets, images, etc.) -- filter-mapping filter-nameextensionsFilter/filter-name url-pattern/faces/*/url-pattern /filter-mapping and futher down. servlet servlet-nameFacesServlet/servlet-name servlet-classjavax.faces.webapp.FacesServlet/servlet-class load-on-startup0/load-on-startup /servlet servlet-mapping servlet-nameFacesServlet/servlet-name url-pattern/faces/*/url-pattern /servlet-mapping On 7/21/07, Érico Teixeira [EMAIL PROTECTED] wrote: Hi Lionel I'm sorry the dealy for responding I added el-ri.jar in my dependencies and a it worked But I still can't make my project to work As I said before I'm using a lot of frameworks on it ... My problem now is that the project is not resolving any .jsf redirection I would like to ask to the list about this but it's going to take some time and I'm really getting tired of it because I should already have started the developing fase and I'm still trying to build my project structure ... Anyway I would really appreciated if you have just a little more pacience with me on this project ok ? :) I'm not sure if my deployment descriptor is set correctly becuase there are filters and servlets from MyFaces, Shale and RI declared ... I believe that can be one of the reasons for the problem ... Anyway I would like to thank you for your time and help --- Lionel Port [EMAIL PROTECTED] wrote: Ignore the last two comments. I just noticed my build also has commons-el. The dependencies you have appear to be right. I'm running on weblogic so I can really tell you if its a tomcat issue or not. On 7/20/07, Lionel Port [EMAIL PROTECTED] wrote: I assume you have removed commons-el-1.0 from your pom of course. On 7/20/07, Lionel Port [EMAIL PROTECTED] wrote: did you do a clean before the package. i.e. mvn clean package That will get rid of the dependencies that are already copied to the target directory but not in your pom. On 7/20/07, Érico Teixeira [EMAIL PROTECTED] wrote: I got the EL RI depedencies from the repository and now I'm having this error : java.lang.LinkageError: loader constraints violated when linking javax/el/ExpressionFactory I searched trought the web and got the info that there is a problem using EL RI with Tomcat 6 I'm not sure if my project structure is going to work Can anyone help about this ? I starting to belive that I have to change my project structure At this moment I'm using Shale, MyFaces, Facelets, Spring, Hibernate and Maven When I compile my project with maven through command line I see that in my war file deps I have el-api.jar , el-impl.jar and commons-el-1.0.jar Would that be one of the possible reasons for the problem ? ... - Original Message From: Lionel Port [EMAIL PROTECTED] To: user@shale.apache.org Sent: Tuesday, July 17, 2007 11:12:27 PM Subject: Re: Integrating Shale with Facelets I've an test app working with shale and facelets. I don't think there is anything specific that needs to be done for shale. The dependencies I have are. dependency groupIdcom.sun.facelets/groupId artifactIdjsf-facelets/artifactId version1.1.11/version /dependency dependency groupIdjavax.el/groupId artifactIdel-api/artifactId version1.0/version /dependency dependency groupIdel-impl/groupId artifactIdel-impl/artifactId version1.0/version /dependency On 7/18/07, Érico Teixeira [EMAIL PROTECTED] wrote: Hi I'm trying to create a project using Maven, Shale, Facelets and MyFaces I added the folowing dependency im my POM : dependency
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
