Re: Tomahawk + Facelets+ state_saving_method = server navigation problem
ciscolos schrieb: Hi forum , we're using Tomahawk 1.1.7 with Myfaces 1.2.4 and Facelets 1.1.14. After changing the context-param javax.faces.STATE_SAVING_METHOD from client to server. We're not able use command links any more. if we try to perform a view action wich calls a bean we get the following error. We found a lot of stuff about such errors, but unfortunatly nobody wrote any solution. Is there a way to use tomahawk wihle configuring the framwork to server statesaving? thanks a lot for help, cheers ciscolos /pages/start/actuell.jsfThe expected view was not returned for the view identifier: /pages/start/actuell.jsf +- Stack Trace javax.faces.application.ViewExpiredException: /pages/start/actuell.jsfThe expected view was not returned for the view identifier: /pages/start/actuell.jsf at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:88) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:103) It works fine for me. You must be doing something unusual with the request somehow. Do you perhaps have a load-balancing system where requests are redirected to a pool of servers? If so, then when using server-side-state you will of course need to configure http-session clustering. Regards, Simon
Re: Tomahawk + Facelets+ state_saving_method = server navigation problem
Hi Simon thanks for your answer, no we dont use any cluster nether we're using load balancing. So do you have any other idea wich may solve our problem ? cheers ciscolos Simon Kitching wrote: ciscolos schrieb: Hi forum , we're using Tomahawk 1.1.7 with Myfaces 1.2.4 and Facelets 1.1.14. After changing the context-param javax.faces.STATE_SAVING_METHOD from client to server. We're not able use command links any more. if we try to perform a view action wich calls a bean we get the following error. We found a lot of stuff about such errors, but unfortunatly nobody wrote any solution. Is there a way to use tomahawk wihle configuring the framwork to server statesaving? thanks a lot for help, cheers ciscolos /pages/start/actuell.jsfThe expected view was not returned for the view identifier: /pages/start/actuell.jsf +- Stack Trace javax.faces.application.ViewExpiredException: /pages/start/actuell.jsfThe expected view was not returned for the view identifier: /pages/start/actuell.jsf at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:88) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:103) It works fine for me. You must be doing something unusual with the request somehow. Do you perhaps have a load-balancing system where requests are redirected to a pool of servers? If so, then when using server-side-state you will of course need to configure http-session clustering. Regards, Simon -- View this message in context: http://www.nabble.com/Tomahawk-%2B-Facelets%2B-state_saving_method-%3D-server-navigation-problem-tp19692252p19719517.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Tomahawk + Facelets+ state_saving_method = server navigation problem
Are your command links enclosed in a form ? On Mon, Sep 29, 2008 at 12:42 AM, ciscolos [EMAIL PROTECTED] wrote: Hi Simon thanks for your answer, no we dont use any cluster nether we're using load balancing. So do you have any other idea wich may solve our problem ? cheers ciscolos Simon Kitching wrote: ciscolos schrieb: Hi forum , we're using Tomahawk 1.1.7 with Myfaces 1.2.4 and Facelets 1.1.14.After changing the context-param javax.faces.STATE_SAVING_METHOD from client to server. We're not able use command links any more. if we try to perform a view action wich calls a bean we get the following error. We found a lot of stuff about such errors, but unfortunatly nobody wrote any solution. Is there a way to use tomahawk wihle configuring the framwork to server statesaving? thanks a lot for help, cheers ciscolos /pages/start/actuell.jsfThe expected view was not returned for the view identifier: /pages/start/actuell.jsf +- Stack Trace javax.faces.application.ViewExpiredException: /pages/start/actuell.jsfThe expected view was not returned for the view identifier: /pages/start/actuell.jsf at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:88) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:103) It works fine for me. You must be doing something unusual with the request somehow. Do you perhaps have a load-balancing system where requests are redirected to a pool of servers? If so, then when using server-side-state you will of course need to configure http-session clustering. Regards, Simon -- View this message in context: http://www.nabble.com/Tomahawk-%2B-Facelets%2B-state_saving_method-%3D-server-navigation-problem-tp19692252p19719517.html Sent from the MyFaces - Users mailing list archive at Nabble.com. -- Grant Smith
Tomahawk + Facelets+ state_saving_method = server navigation problem
Hi forum , we're using Tomahawk 1.1.7 with Myfaces 1.2.4 and Facelets 1.1.14. After changing the context-param javax.faces.STATE_SAVING_METHOD from client to server. We're not able use command links any more. if we try to perform a view action wich calls a bean we get the following error. We found a lot of stuff about such errors, but unfortunatly nobody wrote any solution. Is there a way to use tomahawk wihle configuring the framwork to server statesaving? thanks a lot for help, cheers ciscolos /pages/start/actuell.jsfThe expected view was not returned for the view identifier: /pages/start/actuell.jsf +- Stack Trace javax.faces.application.ViewExpiredException: /pages/start/actuell.jsfThe expected view was not returned for the view identifier: /pages/start/actuell.jsf at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:88) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:103) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:76) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:148) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:154) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:260) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:366) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:493) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:190) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) -- View this message in context: http://www.nabble.com/Tomahawk-%2B-Facelets%2B-state_saving_method-%3D-server-navigation-problem-tp19692252p19692252.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
navigation not working: tomahawk + facelets
Hi, I'm trying to set up a project using Tomahawk and facelets. Before trying to use facelets, this little login-main page web app was working fine, but I can't get it running when adding facelets. The thing is, it doesn't navigate at all. When I click on a form it reaches the right navigation case, but it shows the message required resource (/mylittleapp/Main.faces) is not available. I think tehre is something missing in my config. Here are the config files: * faces-config.xml ... view-handlercom.sun.facelets.FaceletViewHandler/view-handler ... navigation-rule from-view-id/Login.xhtml/from-view-id navigation-case from-outcomeloginOK/from-outcome to-view-id/Main.xhtml/to-view-id /navigation-case /navigation-rule * web.xml ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; version=2.5 xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd; context-param param-namejavax.faces.CONFIG_FILES/param-name param-value/WEB-INF/faces-navigation-config.xml/param-value /context-param context-param param-namejavax.faces.STATE_SAVING_METHOD/param-name param-valueserver/param-value /context-param context-param param-nameorg.apache.myfaces.DETECT_JAVASCRIPT/param-name param-valuefalse/param-value /context-param context-param param-nameorg.apache.myfaces.PRETTY_HTML/param-name param-valuetrue/param-value /context-param context-param param-nameorg.apache.myfaces.VALIDATE/param-name param-valuetrue/param-value /context-param context-param param-nameorg.apache.myfaces.ADD_RESOURCE_CLASS/param-name param-valueorg.apache.myfaces.renderkit.html.util.DefaultAddResource /param-value /context-param context-param param-nameorg.apache.myfaces.CHECK_EXTENSIONS_FILTER /param-name param-valuetrue/param-value /context-param context-param param-nameorg.apache.myfaces.RESOURCE_VIRTUAL_PATH/param-name param-value/faces/extensionResource/param-value /context-param context-param param-namejavax.faces.PARTIAL_STATE_SAVING_METHOD/param-name param-valuefalse/param-value /context-param context-param param-namejavax.faces.PARTIAL_STATE_SAVING_DISPATCH_EVERY_TIME /param-name param-valuetrue/param-value /context-param context-param param-namecom.sun.faces.validateXml/param-name param-valuetrue/param-value /context-param context-param param-namecom.sun.faces.verifyObjects/param-name param-valuetrue/param-value /context-param context-param param-namejavax.faces.DEFAULT_SUFFIX/param-name param-value.xhtml/param-value /context-param context-param param-namefacelets.DEVELOPMENT/param-name param-valuetrue/param-value /context-param context-param param-namefacelets.LIBRARIES/param-name param-value/WEB-INF/tomahawk.taglib.xml; /WEB-INF/jsf-core.taglib.xml /param-value /context-param filter filter-nameMyFacesExtensionsFilter/filter-name filter-class org.apache.myfaces.webapp.filter.ExtensionsFilter /filter-class init-param param-namemaxFileSize/param-name param-value20m/param-value /init-param /filter filter-mapping filter-nameMyFacesExtensionsFilter/filter-name servlet-nameFaces Servlet/servlet-name /filter-mapping filter-mapping filter-nameMyFacesExtensionsFilter/filter-name url-pattern/faces/myFacesExtensionResource/*/url-pattern /filter-mapping listener listener-class org.apache.myfaces.webapp.StartupServletContextListener /listener-class /listener servlet servlet-namefaces/servlet-name servlet-classjavax.faces.webapp.FacesServlet/servlet-class load-on-startup1/load-on-startup /servlet servlet-mapping servlet-namefaces/servlet-name url-pattern*.faces/url-pattern /servlet-mapping welcome-file-list welcome-fileindex.jsp/welcome-file /welcome-file-list /web-app These are the libraries and their versions: jsf-facelets.jar (1.1.13) my-faces (1.2.2) tomahawk (1.1.6) tomahawk-facelets-taglib.jar (last version) ¿What is worng with the above config?. Thanks __ Enviado desde Correo Yahoo! Disfruta de una bandeja de entrada más inteligente. http://es.docs.yahoo.com/mail/overview/index.html
Tomahawk + facelets id-field in validate message
Hi,
this is my problem:
I have integrated MyFaces Tomahawk 1.6.2 + Facelets 1.1.13
this is my form:
h:form id=userForm
table
tr
td
h:outputText id=label1 value=#{msg.userForm_password}:/
t:inputText id=username
value=#{user.username} required=true size=40/
t:message for=username /
/td
td
h:outputText id=label2 value=#{msg.userForm_password}:/
h:inputSecret id=input1 value=#{user.password} required=true
redisplay=true size=40/
/td
/tr
tr
td colspan=2
h:commandButton id=button1 value=salva action=#{user.save}/
/td
/tr
/table
/h:form
when I sumbit form and validate the form fild, the message appears is :
userForm:username: the value is required
id-form and id-field are concatenated, why?
I want to see only field id.
have you solutions to this problem?
Thanks
RE: [Tomahawk] facelets
I thought: why not putting this file facelets defn file for tomahawk right away in the meta-inf of the Tomahawk jar? Won't harm nobody but will certainly help a lot of people. Although I still subscribe to that idea, he had a point also: MF and facelets are indeed 2 different technologies, better keep the 2 apart. Oh, come on, I've heard lame excuses before but this would seem to take the cake. It's not like facelets support requires additional code/classes/whatever to use tomahawk and facelets, it is merely the extra xml file. Now the end users are forced to try to track down a working file that has a version that works with the version of tomahawk they're using. Give 'em a break and just add the file and be done with it...
Re: [Tomahawk] facelets
Actually, as far as I know, all of the MyFaces committers are +1 for making a tomahawk.taglib.xml file for MyFaces part of the distribution. The problem is that we don't have an automated process in place to keep the file up to date yet. Hence Bruno's comment that we'll address it in Tomahawk for JSF 1.2 since no committer has had the time and energy to tackle it in our current build system. As for what harm, if we put something into the main tomahawk jar file, it becomes exceedingly difficult for end-users to override those definitions. Since there's no process in place to automatically generate the right definitions, there's a lot of room for error here. If we can't keep a community wiki page up to date with the correct definitions, it stands to reason that a committer-only file (committers being only a small subset of the community maintaining the wiki page) is going to be worse, not better, at having the correct entries in the taglib file. I think Bruno's tomahawk-facelets.jar file is probably the best short-term solution until we get the automated build in place. On 8/3/07, Nebinger, David [EMAIL PROTECTED] wrote: I thought: why not putting this file facelets defn file for tomahawk right away in the meta-inf of the Tomahawk jar? Won't harm nobody but will certainly help a lot of people. Although I still subscribe to that idea, he had a point also: MF and facelets are indeed 2 different technologies, better keep the 2 apart. Oh, come on, I've heard lame excuses before but this would seem to take the cake. It's not like facelets support requires additional code/classes/whatever to use tomahawk and facelets, it is merely the extra xml file. Now the end users are forced to try to track down a working file that has a version that works with the version of tomahawk they're using. Give 'em a break and just add the file and be done with it...
Re: [Tomahawk] facelets
It would be nice to have it automated, but really, is it necessary for the short term? The taglib requires hardly any data, so is extremely easy to maintain. To keep the maven site updated already requires modifying its documents, so this is no harder. Sandbox already requires even more work to maintain the TLD files than the work required to support facelets. Voting +1 on adding taglib.xml files to the META-INF directory of tomahawk and sandbox without creating new JAR files. -Andrew On 8/3/07, Mike Kienenberger [EMAIL PROTECTED] wrote: Actually, as far as I know, all of the MyFaces committers are +1 for making a tomahawk.taglib.xml file for MyFaces part of the distribution. The problem is that we don't have an automated process in place to keep the file up to date yet. Hence Bruno's comment that we'll address it in Tomahawk for JSF 1.2 since no committer has had the time and energy to tackle it in our current build system. As for what harm, if we put something into the main tomahawk jar file, it becomes exceedingly difficult for end-users to override those definitions. Since there's no process in place to automatically generate the right definitions, there's a lot of room for error here. If we can't keep a community wiki page up to date with the correct definitions, it stands to reason that a committer-only file (committers being only a small subset of the community maintaining the wiki page) is going to be worse, not better, at having the correct entries in the taglib file. I think Bruno's tomahawk-facelets.jar file is probably the best short-term solution until we get the automated build in place. On 8/3/07, Nebinger, David [EMAIL PROTECTED] wrote: I thought: why not putting this file facelets defn file for tomahawk right away in the meta-inf of the Tomahawk jar? Won't harm nobody but will certainly help a lot of people. Although I still subscribe to that idea, he had a point also: MF and facelets are indeed 2 different technologies, better keep the 2 apart. Oh, come on, I've heard lame excuses before but this would seem to take the cake. It's not like facelets support requires additional code/classes/whatever to use tomahawk and facelets, it is merely the extra xml file. Now the end users are forced to try to track down a working file that has a version that works with the version of tomahawk they're using. Give 'em a break and just add the file and be done with it...
Re: [Tomahawk] facelets
Not sure which method I think is better but I would definitely like there to be a standard, updated way to do this for tomahawk. I vote in that vain if it counts for anything :) Also, won't there be more involved than just the taglib.xml file, such as a Tag Handler to get the tree2 component to work? On 8/3/07, Andrew Robinson [EMAIL PROTECTED] wrote: It would be nice to have it automated, but really, is it necessary for the short term? The taglib requires hardly any data, so is extremely easy to maintain. To keep the maven site updated already requires modifying its documents, so this is no harder. Sandbox already requires even more work to maintain the TLD files than the work required to support facelets. Voting +1 on adding taglib.xml files to the META-INF directory of tomahawk and sandbox without creating new JAR files. -Andrew On 8/3/07, Mike Kienenberger [EMAIL PROTECTED] wrote: Actually, as far as I know, all of the MyFaces committers are +1 for making a tomahawk.taglib.xml file for MyFaces part of the distribution. The problem is that we don't have an automated process in place to keep the file up to date yet. Hence Bruno's comment that we'll address it in Tomahawk for JSF 1.2 since no committer has had the time and energy to tackle it in our current build system. As for what harm, if we put something into the main tomahawk jar file, it becomes exceedingly difficult for end-users to override those definitions. Since there's no process in place to automatically generate the right definitions, there's a lot of room for error here. If we can't keep a community wiki page up to date with the correct definitions, it stands to reason that a committer-only file (committers being only a small subset of the community maintaining the wiki page) is going to be worse, not better, at having the correct entries in the taglib file. I think Bruno's tomahawk-facelets.jar file is probably the best short-term solution until we get the automated build in place. On 8/3/07, Nebinger, David [EMAIL PROTECTED] wrote: I thought: why not putting this file facelets defn file for tomahawk right away in the meta-inf of the Tomahawk jar? Won't harm nobody but will certainly help a lot of people. Although I still subscribe to that idea, he had a point also: MF and facelets are indeed 2 different technologies, better keep the 2 apart. Oh, come on, I've heard lame excuses before but this would seem to take the cake. It's not like facelets support requires additional code/classes/whatever to use tomahawk and facelets, it is merely the extra xml file. Now the end users are forced to try to track down a working file that has a version that works with the version of tomahawk they're using. Give 'em a break and just add the file and be done with it...
[Tomahawk] facelets
does anyone have an updated tomahawk.taglib.xml ? The one at the wiki does not seem updated. Will Myfaces add full facelets support to its custom components? Regards Erlend
Re: [Tomahawk] facelets
I talked about this with Werner Punz...I thought: why not putting this file right away in the meta-inf of the Tomahawk jar? Won't harm nobody but will certainly help a lot of people. Although I still subscribe to that idea, he had a point also: MF and facelets are indeed 2 different technologies, better keep the 2 apart. Yet, it's another thing we can';tr forget to set up and currently the file @MF Wiki is indeed to be stitched together manually with is kinda funny (unprofessional). I think there is room for improvement, either in the form of a facelets-integrated download. (so Toma Sandbox WITH the taglibs in their meta-in dirs) or at least another entry in the download table just for facelets: a link to the jsf-facelts.jar, and 2 links, to the respective taglib files. This, for me, would seem to be its logical place. -Wolf On 7/31/07, Erlend Hamnaberg [EMAIL PROTECTED] wrote: does anyone have an updated tomahawk.taglib.xml ? The one at the wiki does not seem updated. Will Myfaces add full facelets support to its custom components? Regards Erlend
RE: [Tomahawk] facelets
instead of supplying two taglib-files... just create two jar-files with nothing more in it, than the two taglib files... Then the deployment of the two jar-files is enough, whereas the deployment of the two taglib-files requires additional work from the user... regards Alexander From: Wolf Benz [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 31, 2007 11:56 AM To: MyFaces Discussion Subject: Re: [Tomahawk] facelets I talked about this with Werner Punz... I thought: why not putting this file right away in the meta-inf of the Tomahawk jar? Won't harm nobody but will certainly help a lot of people. Although I still subscribe to that idea, he had a point also: MF and facelets are indeed 2 different technologies, better keep the 2 apart. Yet, it's another thing we can';tr forget to set up and currently the file @MF Wiki is indeed to be stitched together manually with is kinda funny (unprofessional). I think there is room for improvement, either in the form of a facelets-integrated download. (so Toma Sandbox WITH the taglibs in their meta-in dirs) or at least another entry in the download table just for facelets: a link to the jsf-facelts.jar, and 2 links, to the respective taglib files. This, for me, would seem to be its logical place. -Wolf On 7/31/07, Erlend Hamnaberg [EMAIL PROTECTED] wrote: does anyone have an updated tomahawk.taglib.xml ? The one at the wiki does not seem updated. Will Myfaces add full facelets support to its custom components? Regards Erlend
Re: [Tomahawk] facelets
It is probably that the next major version of tomahawk (the one explicitly created for jsf 1.2) will integrate the facelets taglib generation in the build process, as it will take advantage of the code generation of the trinidad's maven-faces-plugin. In the meanwhile, I use this library (implemented by myself): http://people.apache.org/~baranda/tomahawk-facelets-1.0.jar Feel free to use it, apache license... Cheers, Bruno On 31/07/07, Jesse Alexander (KSFD 121) [EMAIL PROTECTED] wrote: instead of supplying two taglib-files... just create two jar-files with nothing more in it, than the two taglib files... Then the deployment of the two jar-files is enough, whereas the deployment of the two taglib-files requires additional work from the user... regards Alexander From: Wolf Benz [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 31, 2007 11:56 AM To: MyFaces Discussion Subject: Re: [Tomahawk] facelets I talked about this with Werner Punz... I thought: why not putting this file right away in the meta-inf of the Tomahawk jar? Won't harm nobody but will certainly help a lot of people. Although I still subscribe to that idea, he had a point also: MF and facelets are indeed 2 different technologies, better keep the 2 apart. Yet, it's another thing we can';tr forget to set up and currently the file @MF Wiki is indeed to be stitched together manually with is kinda funny (unprofessional). I think there is room for improvement, either in the form of a facelets-integrated download. (so Toma Sandbox WITH the taglibs in their meta-in dirs) or at least another entry in the download table just for facelets: a link to the jsf-facelts.jar, and 2 links, to the respective taglib files. This, for me, would seem to be its logical place. -Wolf On 7/31/07, Erlend Hamnaberg [EMAIL PROTECTED] wrote: does anyone have an updated tomahawk.taglib.xml ? The one at the wiki does not seem updated. Will Myfaces add full facelets support to its custom components? Regards Erlend
Re: [Tomahawk] facelets
Thx Alexander, For what Tomahawk version is this? (116/117?) -Wolf On 7/31/07, Bruno Aranda [EMAIL PROTECTED] wrote: It is probably that the next major version of tomahawk (the one explicitly created for jsf 1.2) will integrate the facelets taglib generation in the build process, as it will take advantage of the code generation of the trinidad's maven-faces-plugin. In the meanwhile, I use this library (implemented by myself): http://people.apache.org/~baranda/tomahawk-facelets-1.0.jar Feel free to use it, apache license... Cheers, Bruno On 31/07/07, Jesse Alexander (KSFD 121) [EMAIL PROTECTED] wrote: instead of supplying two taglib-files... just create two jar-files with nothing more in it, than the two taglib files... Then the deployment of the two jar-files is enough, whereas the deployment of the two taglib-files requires additional work from the user... regards Alexander From: Wolf Benz [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 31, 2007 11:56 AM To: MyFaces Discussion Subject: Re: [Tomahawk] facelets I talked about this with Werner Punz... I thought: why not putting this file right away in the meta-inf of the Tomahawk jar? Won't harm nobody but will certainly help a lot of people. Although I still subscribe to that idea, he had a point also: MF and facelets are indeed 2 different technologies, better keep the 2 apart. Yet, it's another thing we can';tr forget to set up and currently the file @MF Wiki is indeed to be stitched together manually with is kinda funny (unprofessional). I think there is room for improvement, either in the form of a facelets-integrated download. (so Toma Sandbox WITH the taglibs in their meta-in dirs) or at least another entry in the download table just for facelets: a link to the jsf-facelts.jar, and 2 links, to the respective taglib files. This, for me, would seem to be its logical place. -Wolf On 7/31/07, Erlend Hamnaberg [EMAIL PROTECTED] wrote: does anyone have an updated tomahawk.taglib.xml ? The one at the wiki does not seem updated. Will Myfaces add full facelets support to its custom components? Regards Erlend
Re: [Tomahawk] facelets
Hi, I have uploaded my little project which I created with info from the wiki and other sources here: http://code.google.com/p/tomahawk-facelets It should be supporting tomahawk 1.1.6 and the sandbox. Hope it helps! Bruno On 31/07/07, Wolf Benz [EMAIL PROTECTED] wrote: Thx Alexander, For what Tomahawk version is this? (116/117?) -Wolf On 7/31/07, Bruno Aranda [EMAIL PROTECTED] wrote: It is probably that the next major version of tomahawk (the one explicitly created for jsf 1.2) will integrate the facelets taglib generation in the build process, as it will take advantage of the code generation of the trinidad's maven-faces-plugin. In the meanwhile, I use this library (implemented by myself): http://people.apache.org/~baranda/tomahawk-facelets-1.0.jar Feel free to use it, apache license... Cheers, Bruno On 31/07/07, Jesse Alexander (KSFD 121) [EMAIL PROTECTED] wrote: instead of supplying two taglib-files... just create two jar-files with nothing more in it, than the two taglib files... Then the deployment of the two jar-files is enough, whereas the deployment of the two taglib-files requires additional work from the user... regards Alexander From: Wolf Benz [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 31, 2007 11:56 AM To: MyFaces Discussion Subject: Re: [Tomahawk] facelets I talked about this with Werner Punz... I thought: why not putting this file right away in the meta-inf of the Tomahawk jar? Won't harm nobody but will certainly help a lot of people. Although I still subscribe to that idea, he had a point also: MF and facelets are indeed 2 different technologies, better keep the 2 apart. Yet, it's another thing we can';tr forget to set up and currently the file @MF Wiki is indeed to be stitched together manually with is kinda funny (unprofessional). I think there is room for improvement, either in the form of a facelets-integrated download. (so Toma Sandbox WITH the taglibs in their meta-in dirs) or at least another entry in the download table just for facelets: a link to the jsf-facelts.jar, and 2 links, to the respective taglib files. This, for me, would seem to be its logical place. -Wolf On 7/31/07, Erlend Hamnaberg [EMAIL PROTECTED] wrote: does anyone have an updated tomahawk.taglib.xml ? The one at the wiki does not seem updated. Will Myfaces add full facelets support to its custom components? Regards Erlend
[TOMAHAWK] Facelets support was (RE: [Solved] Unable to display Suggested Items using Sandbox component s:inputAjaxSuggest)
Hi Bansi,
I was having the same problem as you are having now.
In my case it was a configuration problem.
You need to check if your sandbox-taglib.xml contains the following
tag-defintion:
tag
tag-nameinputSuggestAjax/tag-name
component
component-typeorg.apache.myfaces.InputSuggestAjax/component-type
renderer-typeorg.apache.myfaces.InputSuggestAjax/renderer-type
handler-class
facelets.InputSuggestAjaxComponentHandler
/handler-class
/component
/tag
And that your webapp contains the InputSuggestAjaxComponentHandler
class.
Source code for that class can be found at:
http://wiki.java.net/bin/view/Projects/InputSuggestAjaxComponentHandler
I added a small section about using the inputSuggestAjax with facelets
to the wiki.
To all:
It appairs that some additional code is required to use at least one
tomahawk component in combination with facelets. As always there can be
discussion about whom should provide support for this kind of code (the
facelets or tomahawk community)
As being a user I would like to gets such 'integration'-code along with
the component.
On the other hand I would understand if the myfaces-community would not
like to have some code dependand on com.sun.facelets.tag.*-classes in
the tomahawk-project.
How do you feel about a creating seperate project
groupId=org.apache.myfaces.tomahawk and artifactId=tomahawk-facelets,
which has dependancies on org.apache.myfaces.tomahawk:tomahawk and
com.sun.facelets:jsf-facelets and contains the necessary code to get all
the tomahawk components working in a facelets-based application?
That way the user only needs to include 1 dependancy and the codebases
stay clean?
With kind regards,
Marco Beelen
From: Laurentiu Trica [mailto:[EMAIL PROTECTED]
Sent: dinsdag 27 februari 2007 16:00
To: MyFaces Discussion
Subject: Re: [Solved] Unable to display Suggested Items using Sandbox
component s:inputAjaxSuggest
Hi Bansi
I don't know if what i say applies to Sandbox 1.1.3, I am working on
1.1.5.
The public List getSuggestedWords(String keyword) should have 2
parameters:
public List getSuggestedWords(String keyword, Integer maxItems)
and you could specify the max number of items to be displayed from the
component attributes:
s:inputSuggestAjax suggestedItemsMethod=#{test.getSuggestedWords}
value=#{test.currentValue } maxSuggestedItems=10 /
Just try it if you didn't worked it out already.
On 2/26/07, bansi [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Here is some more info on my earlier posting
I figured out from debugging that control doesnt go to
getSuggestedWords()
method as the following line never gets printed in the log
console :
System.out.println(In getSuggestedWords method );
Wondering what could be the reason
Regards
Bansi
bansi wrote:
Hi I am using Facelets 1.1.2 and
tomahawk-sandbox-1.1.3-SNAPSHOT.jar,
tomahawk-1.1.3.jar, MyFaces 1.1.4.
The code works perfectly fine but when i enter values into
textbox it
doesnt show up suggested Items . Then i debugged the
application with
log4j
Here is the jsp page
h:outputText value=Enter your name : /
s:inputSuggestAjax suggestedItemsMethod=#{
test.getSuggestedWords}
value=#{test.currentValue} /
br /
h:commandButton value=Submit/
br /
h:outputText value=Your name is #{ test.currentValue}/
Here is the backing bean
public List getSuggestedWords(String keyword) {
List list = new ArrayList();
list.add(keyword + Ahmed Saleh);
list.add(keyword + Kahki);
list.add(keyword + Kourany);
list.add(keyword + Kiki);
list.add(keyword + Saleh Abouetta);
list.add(keyword + Hashim);
return list;
}
public String getCurrentValue() {
return currentValue;
}
public void setCurrentValue(String currentValue) {
this.currentValue = currentValue;
}
//current selected value
String currentValue;
I have set the Save State to Client in web.xml
Any pointers/suggestions will be highly appreciated
Regards
Bansi
--
View this message in context:
http://www.nabble.com/Unable-to-display-Suggested-Items-using-Sandbox-co
mponent-s%3AinputAjaxSuggest-tf3295288.html#a9168175
Sent from the MyFaces - Users mailing list archive at
Nabble.com.
--
Best regards,
Laurentiu
www.codebeat.ro
--
Notice: This e-mail message, together with any attachments, contains
Re: [TOMAHAWK] Facelets support was (RE: [Solved] Unable to display Suggested Items using Sandbox component s:inputAjaxSuggest)
As always, it's not a matter of do we want it, it's a matter of who's going to do it, and how. For there to be any integrated solution, it has to be a complete solution since it is my understanding that it is not possible to override whatever facelet tags we define. Thus, we probably will need to code-generate the taglib.xml files in order to keep them up-to-date since the person working on a particular component may not realize they need to change the facelets portion of the component taghandler. It would be good if the facelets support were in a separate maven module so that the main Tomahawk code does not depend upon facelets. What you propose sounds great -- when will you provide patches to implement it? :-) On 2/27/07, Beelen, Marco [EMAIL PROTECTED] wrote: It appairs that some additional code is required to use at least one tomahawk component in combination with facelets. As always there can be discussion about whom should provide support for this kind of code (the facelets or tomahawk community) As being a user I would like to gets such 'integration'-code along with the component. On the other hand I would understand if the myfaces-community would not like to have some code dependand on com.sun.facelets.tag.*-classes in the tomahawk-project. How do you feel about a creating seperate project groupId=org.apache.myfaces.tomahawk and artifactId=tomahawk-facelets, which has dependancies on org.apache.myfaces.tomahawk:tomahawk and com.sun.facelets:jsf-facelets and contains the necessary code to get all the tomahawk components working in a facelets-based application? That way the user only needs to include 1 dependancy and the codebases stay clean?
Re: [Solved] [TOMAHAWK] Facelets support was (RE: Unable to display Suggested Items using Sandbox component s:inputAjaxSuggest)
Hi Marco
Thank you for your response. I double checked and found sandbox-taglib.xml
do contain the tag-defintion you mentioned of inputSuggestAjax. Also i
created a facelets subdirectory under src directory to store the java class
InputSuggestAjaxComponentHandler.java
Regards
Bansi
Beelen, Marco wrote:
Hi Bansi,
I was having the same problem as you are having now.
In my case it was a configuration problem.
You need to check if your sandbox-taglib.xml contains the following
tag-defintion:
tag
tag-nameinputSuggestAjax/tag-name
component
component-typeorg.apache.myfaces.InputSuggestAjax/component-type
renderer-typeorg.apache.myfaces.InputSuggestAjax/renderer-type
handler-class
facelets.InputSuggestAjaxComponentHandler
/handler-class
/component
/tag
And that your webapp contains the InputSuggestAjaxComponentHandler
class.
Source code for that class can be found at:
http://wiki.java.net/bin/view/Projects/InputSuggestAjaxComponentHandler
I added a small section about using the inputSuggestAjax with facelets
to the wiki.
To all:
It appairs that some additional code is required to use at least one
tomahawk component in combination with facelets. As always there can be
discussion about whom should provide support for this kind of code (the
facelets or tomahawk community)
As being a user I would like to gets such 'integration'-code along with
the component.
On the other hand I would understand if the myfaces-community would not
like to have some code dependand on com.sun.facelets.tag.*-classes in
the tomahawk-project.
How do you feel about a creating seperate project
groupId=org.apache.myfaces.tomahawk and artifactId=tomahawk-facelets,
which has dependancies on org.apache.myfaces.tomahawk:tomahawk and
com.sun.facelets:jsf-facelets and contains the necessary code to get all
the tomahawk components working in a facelets-based application?
That way the user only needs to include 1 dependancy and the codebases
stay clean?
With kind regards,
Marco Beelen
From: Laurentiu Trica [mailto:[EMAIL PROTECTED]
Sent: dinsdag 27 februari 2007 16:00
To: MyFaces Discussion
Subject: Re: [Solved] Unable to display Suggested Items using Sandbox
component s:inputAjaxSuggest
Hi Bansi
I don't know if what i say applies to Sandbox 1.1.3, I am working on
1.1.5.
The public List getSuggestedWords(String keyword) should have 2
parameters:
public List getSuggestedWords(String keyword, Integer maxItems)
and you could specify the max number of items to be displayed from the
component attributes:
s:inputSuggestAjax suggestedItemsMethod=#{test.getSuggestedWords}
value=#{test.currentValue } maxSuggestedItems=10 /
Just try it if you didn't worked it out already.
On 2/26/07, bansi [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Here is some more info on my earlier posting
I figured out from debugging that control doesnt go to
getSuggestedWords()
method as the following line never gets printed in the log
console :
System.out.println(In getSuggestedWords method );
Wondering what could be the reason
Regards
Bansi
bansi wrote:
Hi I am using Facelets 1.1.2 and
tomahawk-sandbox-1.1.3-SNAPSHOT.jar,
tomahawk-1.1.3.jar, MyFaces 1.1.4.
The code works perfectly fine but when i enter values into
textbox it
doesnt show up suggested Items . Then i debugged the
application with
log4j
Here is the jsp page
h:outputText value=Enter your name : /
s:inputSuggestAjax suggestedItemsMethod=#{
test.getSuggestedWords}
value=#{test.currentValue} /
br /
h:commandButton value=Submit/
br /
h:outputText value=Your name is #{ test.currentValue}/
Here is the backing bean
public List getSuggestedWords(String keyword) {
List list = new ArrayList();
list.add(keyword + Ahmed Saleh);
list.add(keyword + Kahki);
list.add(keyword + Kourany);
list.add(keyword + Kiki);
list.add(keyword + Saleh Abouetta);
list.add(keyword + Hashim);
return list;
}
public String getCurrentValue() {
return currentValue;
}
public void setCurrentValue(String currentValue) {
this.currentValue = currentValue;
}
//current selected value
String currentValue;
I have set the Save State to Client in web.xml
Any pointers/suggestions will be highly appreciated
Regards
Bansi
--
View this message in context:
http://www.nabble.com/Unable-to-display-Suggested-Items-using-Sandbox-co
Tomahawk + Facelets + Shale
I'm having trouble configuring myfaces tomahawk components to work with my Facelets + Shale environment. Is anyone else using this combination successfully? I'm attempting to use the 1.1.5 Snapshot jars for myfaces core and tomahawk. Is anyone here using this combination successfully? Based on instructions at the facelets wiki, this is what I've done so far: I've created a file named tomahawk.taglib.xml under /WEB-INF: ?xml version=1.0? !DOCTYPE facelet-taglib PUBLIC -//Sun Microsystems, Inc.//DTD Facelet Taglib 1.0//EN http://java.sun.com/dtd/facelet-taglib_1_0.dtd; facelet-taglib namespacehttp://myfaces.apache.org/tomahawk/namespace tag tag-namecommandLink/tag-name component component-typeorg.apache.myfaces.component.html.ext.HtmlCommandLink/c omponent-type renderer-typeorg.apache.myfaces.renderkit.html.HtmlLinkRenderer/rende rer-type /component /tag /facelet-taglib I've registered the file in my web.xml: ... context-param param-namefacelets.LIBRARIES/param-name param-value/WEB-INF/tomahawk.taglib.xml/param-value /context-param ... I've referenced the namespace declared in the taglib file in the root html element of my page as such: xmlns:t=http://myfaces.apache.org/tomahawk; Am I missing something? Thanks
RE: Tomahawk + Facelets + Shale
Solved - except I have one more issue. I incorrectly assumed that I had to update the path to the component as it exists in the tomahawk jar. Changing it back to the specifications in the wiki, plus adding the proper renderer-type (that was the missing piece), fixed the problem. Here's how it looks now for the commandLink: tag tag-namecommandLink/tag-name component component-typeorg.apache.myfaces.HtmlCommandLink/component-type renderer-typejavax.faces.Link/renderer-type /component /tag -Original Message- From: Reynolds, James [mailto:[EMAIL PROTECTED] Sent: Friday, January 26, 2007 11:26 AM To: MyFaces Discussion Subject: Tomahawk + Facelets + Shale I'm having trouble configuring myfaces tomahawk components to work with my Facelets + Shale environment. Is anyone else using this combination successfully? I'm attempting to use the 1.1.5 Snapshot jars for myfaces core and tomahawk. Is anyone here using this combination successfully? Based on instructions at the facelets wiki, this is what I've done so far: I've created a file named tomahawk.taglib.xml under /WEB-INF: ?xml version=1.0? !DOCTYPE facelet-taglib PUBLIC -//Sun Microsystems, Inc.//DTD Facelet Taglib 1.0//EN http://java.sun.com/dtd/facelet-taglib_1_0.dtd; facelet-taglib namespacehttp://myfaces.apache.org/tomahawk/namespace tag tag-namecommandLink/tag-name component component-typeorg.apache.myfaces.component.html.ext.HtmlCommandLink/c omponent-type renderer-typeorg.apache.myfaces.renderkit.html.HtmlLinkRenderer/rende rer-type /component /tag /facelet-taglib I've registered the file in my web.xml: ... context-param param-namefacelets.LIBRARIES/param-name param-value/WEB-INF/tomahawk.taglib.xml/param-value /context-param ... I've referenced the namespace declared in the taglib file in the root html element of my page as such: xmlns:t=http://myfaces.apache.org/tomahawk; Am I missing something? Thanks E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized.
RE: Tomahawk + Facelets + Shale
From: Reynolds, James [EMAIL PROTECTED] Solved - except I have one more issue. I incorrectly assumed that I had to update the path to the component as it exists in the tomahawk jar. Changing it back to the specifications in the wiki, plus adding the proper renderer-type (that was the missing piece), fixed the problem. I'm not surprised that facelets needs the rendererType to be specified. Shale Clay has a similar issue with the tomahawk components. Theses guys (components) are pretty relaxed on making sure that the component's getRendererType method is overridden with the correct value. Sometimes they default to the super class. On the flip side, there seems to be a ton of reuse with the runtime. Here's how it looks now for the commandLink: commandLink org.apache.myfaces.HtmlCommandLink javax.faces.Link -Original Message- From: Reynolds, James [mailto:[EMAIL PROTECTED] Sent: Friday, January 26, 2007 11:26 AM To: MyFaces Discussion Subject: Tomahawk + Facelets + Shale I'm having trouble configuring myfaces tomahawk components to work with my Facelets + Shale environment. Is anyone else using this combination successfully? I'm attempting to use the 1.1.5 Snapshot jars for myfaces core and tomahawk. Is anyone here using this combination successfully? Based on instructions at the facelets wiki, this is what I've done so far: I've created a file named tomahawk.taglib.xml under /WEB-INF: -//Sun Microsystems, Inc.//DTD Facelet Taglib 1.0//EN http://java.sun.com/dtd/facelet-taglib_1_0.dtd; http://myfaces.apache.org/tomahawk commandLink org.apache.myfaces.component.html.ext.HtmlCommandLink omponent-type org.apache.myfaces.renderkit.html.HtmlLinkRenderer rer-type I've registered the file in my web.xml: ... facelets.LIBRARIES /WEB-INF/tomahawk.taglib.xml ... I've referenced the namespace declared in the taglib file in the root html element of my page as such: xmlns:t=http://myfaces.apache.org/tomahawk; Am I missing something? Thanks E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized.
Tomahawk / Facelets
Hello All,
I'm trying to use Tomahawk together with Facelets. I've installed the
tomahawk-facelets.jar from Wiki into my WEB-INF/lib directory, and the
simple things work well.
But I've got a problem using Tomahawk components in Facelets components.
I've created a taglib on my own containing the following tag:
tag
tag-namekontoname/tag-name
sourcekontoname.xhtml/source
/tag
and the tag source file
ui:component xmlns:ui=http://java.sun.com/jsf/facelets;
xmlns:h=http://java.sun.com/jsf/html;
xmlns:f=http://java.sun.com/jsf/core;
xmlns:t=http://myfaces.apache.org/tomahawk;
t:columns value=#{liste.angezeigteSpalten} var=spalte
f:facet name=header
Auftragsname
/f:facet
h:outputText value=#{kontoname.wert}/h:outputText
/t:columns
/ui:component
But all the Tomahawk Elements in the file are ignored. The calling file
looks like follows:
t:dataTable var=konto value=
#{leistungsschein.kontozeilen.gefilterteListe}
h:column
f:facet name=header
Datum
/f:facet
h:outputText value=#{leistungsschein.iterDatum} /
/h:column
le:kontoname konto=#{konto} liste=#{leistungsschein.kontozeilen}
/
/t:dataTable
Is it possibly impossible to user le:kontoname as child of t:dataTable?
Or am I doing wrong anything else? Any idea what I can do?
Thank you!
Regards,
Marcus.
_
prosystems IT GmbH
Anwendungsentwicklung
Postfach 31 51
53021 Bonn (Germany)
Tel: 0228 / 3366 - 3329, Fax: 0228 / 3366 - 73329
mailto:[EMAIL PROTECTED] http://www.prosystemsIT.de
Amtsgericht Bonn - HR B 13189
Antwort: Re: Tomahawk / Facelets
Yes ... I did. The Tag worked well when I had it within a h:column tag.
But since the Tag generates a dynamic number of columns (then I used tds
in the tag), I had a tdtd.../tdtd.../td/td in the generated
html. The browser has had no problem, but I didn't like this kind of hack.
So I tried to use t:dataTable with t:columns. If I paste the tag source
into the main file, it works - but it doesn't if I have the t:columns in
the tag.
Mikael
Andersson An: MyFaces Discussion
users@myfaces.apache.org
[EMAIL PROTECTED]Kopie:
.comThema:Re: Tomahawk /
Facelets
19.07.2006 12:46
Bitte antworten
an MyFaces
Discussion
Did you declared the namespace for 'le' in the file using the tag?
You should also declare the namespace to be used in you taglib file, ex:
facelet-taglib
namespacekontoname/namespace
tag
tag-namekontoname/tag-name
sourcekontoname.xhtml/source
/tag
/facelet-taglib
On 19/07/06, Marcus Schmidke [EMAIL PROTECTED] wrote:
Hello All,
I'm trying to use Tomahawk together with Facelets. I've installed the
tomahawk-facelets.jar from Wiki into my WEB-INF/lib directory, and
the
simple things work well.
But I've got a problem using Tomahawk components in Facelets
components.
I've created a taglib on my own containing the following tag:
tag
tag-namekontoname/tag-name
sourcekontoname.xhtml/source
/tag
and the tag source file
ui:component xmlns:ui=http://java.sun.com/jsf/facelets;
xmlns:h=http://java.sun.com/jsf/html
xmlns:f=http://java.sun.com/jsf/core;
xmlns:t=http://myfaces.apache.org/tomahawk;
t:columns value=#{liste.angezeigteSpalten} var=spalte
f:facet name=header
Auftragsname
/f:facet
h:outputText value=#{kontoname.wert}/h:outputText
/t:columns
/ui:component
But all the Tomahawk Elements in the file are ignored. The calling
file
looks like follows:
t:dataTable var=konto value=
#{leistungsschein.kontozeilen.gefilterteListe}
h:column
f:facet name=header
Datum
/f:facet
h:outputText value=#{leistungsschein.iterDatum} /
/h:column
le:kontoname konto=#{konto} liste=#{
leistungsschein.kontozeilen}
/
/t:dataTable
Is it possibly impossible to user le:kontoname as child of
t:dataTable?
Or am I doing wrong anything else? Any idea what I can do?
Thank you!
Regards,
Marcus.
_
prosystems IT GmbH
Anwendungsentwicklung
Postfach 31 51
53021 Bonn (Germany)
Tel: 0228 / 3366 - 3329, Fax: 0228 / 3366 - 73329
mailto:[EMAIL PROTECTED] http://www.prosystemsIT.de
Amtsgericht Bonn - HR B 13189
_
prosystems IT GmbH
Anwendungsentwicklung
Postfach 31 51
53021 Bonn (Germany)
Tel: 0228 / 3366 - 3329, Fax: 0228 / 3366 - 73329
mailto:[EMAIL PROTECTED] http://www.prosystemsIT.de
Amtsgericht Bonn - HR B 13189
