[ANNOUNCE] Apache Tobago 5.3.0 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 5.3.0. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main features Tobago 5.3.0 * Sheet: Multi-Column * Sheet: Column-Hearder Toolbar * Date: before and after facets * Markup: responsive UI (e.g. hide in case of small displays) * Bugfixes Changes --- Please check the release notes for each version at these URLs for a full list of the changes: Tobago 5.3.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=12350747 For more information about Apache Tobago, please visit https://myfaces.apache.org/#/tobago Have fun, -The MyFaces team
[ANNOUNCE] Apache Tobago 2.5.0, 4.5.5 and 5.1.0 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.5.0, 4.5.5 and 5.1.0. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main features Tobago 5.1.0 * Drag and Drop File Upload * Restore scroll position of containers after server request * Default position of label should be configurable * SegmentLayout: Extra extra large * Bugfixes Tobago 4.5.5 * Update JS libraries * Bugfixes Tobago 2.5.0 * Select2 feature * Maintenance Changes --- Please check the release notes for each version at these URLs for a full list of the changes: Tobago 5.1.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344152=12310273 Tobago 4.5.5 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350236=12310273 Tobago 2.5.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345962=12310273 For more information about Apache Tobago, please visit https://myfaces.apache.org/#/tobago Have fun, -The MyFaces team
[ANNOUNCE] Apache Tobago 2.4.5 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.4.5. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main new features - * Bugfixes Changes --- Please check the release notes at https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349661=12310273 for a full list of the changes in this version. For more information about Apache Tobago, please visit https://myfaces.apache.org/#/tobago/. Have fun, -The MyFaces team
Quarkus with MyFaces 2.3-next: Jandex problem
Hi, I've tried to get the Tobago 5 demo running with Quarkus. It seems to work but NOT with the build artifacts from the Maven Repos. The error message is the same for M6 and SNAPSHOT (I assume the myfaces-api is the problem, because it contains the META-INF/jandex.idx file). Repo artifacts: https://repository.apache.org/snapshots/org/apache/myfaces/core/myfaces-api/2.3-next-SNAPSHOT/myfaces-api-2.3-next-20211021.081500-689.jar or https://repo.maven.apache.org/maven2/org/apache/myfaces/core/myfaces-api/2.3-next-M6/myfaces-api-2.3-next-M6.jar Error message: [ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:1.13.7.Final:build (default) on project tobago-example-demo: Failed to build quarkus application: io.quarkus.builder.BuildException: Build failure: Build failed due to errors [ERROR] [error]: Build step io.quarkus.arc.deployment.ArcProcessor#generateResources threw an exception: java.lang.IllegalStateException: Value is not set for javax.faces.convert.FacesConverter.value(). Most probably an older version of Jandex was used to index an application dependency. Make sure that Jandex 2.1+ is used. [ERROR] at io.quarkus.arc.processor.AnnotationLiteralProcessor.process(AnnotationLiteralProcessor.java:77) [ERROR] at io.quarkus.arc.processor.BeanGenerator.initConstructor(BeanGenerator.java:697) When I build the SNAPSHOT of myfaces-api on my machine, no problem occurs. Both jandex.idx file (SNAPSHOT of Repo and SNAPSHOT of my machine) has same size, but different content. My Setup is: * Maven 3.8.3 * AdoptOpenJDK 1.8.0_292 or Temurin 1.8.0_302 or 11.0.12 or Oracle 1.8.0_162 * OS: MacOS 10.15.7 (x86_64) My demo is the Tobago 5.x and is available here: https://github.com/apache/myfaces-tobago Use branch "tobago-5.x" The MyFaces next Version can be changed in the ROOT/pom.xml: Tag 2.3-next-M6 Initial build with "mvn clean install" cd to tobago-example/tobago-example-demo Try to build with mvn clean install -Pquarkus (will probably fail, if myfaces is from the Repo) If it not fails start with java -jar target/quarkus-app/quarkus-run.jar Browse: http://localhost:8080/content/010-input/40-date/Date.xhtml There are still some problems with Quarkus and the Demo, but this can be fixed later. Does anyone have an idea what the Jantex problem is? Regards, Udo
[ANNOUNCE] Apache Tobago 4.5.0 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 4.5.0. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main new features - * Sheet: Lasy loading by scroll * Several minor improvements * Update jQuery and Bootstrap * Bugfixes Changes --- Please check the release notes at http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=12345562 for a full list of the changes in this version. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
[ANNOUNCE] Apache Tobago 4.4.1 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 4.4.1. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main features Tobago 4.4.1 * Bugfixes Please check the release notes for each version at these URLs for a full list of the changes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=12345061 For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
Re: Browser-Support for Tobago 5
Hi Marko, thanks for your suggestion. Actually we use Babel for Tobago (current master development), but for me Babeldoes not keep what it promises. There are some language features in TypeScript/ES6 than can't be translated to ES5. So, we have to decide to program in a "modern and clean" way, or doing workarounds all the day... Regards, Udo Am 09.04.19 um 17:15 schrieb Voß, Marko: > Hello, > > you could make use of NPM and Babel (https://babeljs.io) or the like to > transform your JS to the supported version. So the written JS and the > resulting JS do not need to be the same. > > Greetings, > Marko > > -----Ursprüngliche Nachricht- > Von: Udo Schnurpfeil > Gesendet: Dienstag, 9. April 2019 14:36 > An: MyFaces Development ; MyFaces Discussion > > Betreff: Browser-Support for Tobago 5 > > Hi folks, > > Tobago 5 is now under development and the plan is to refactor all the > JavaScript code to TypeScript. With this, we want to clean up code and throw > old workarounds away. > > The basic idea is to write TypeScript and generate a compatible JavaScript > for all supported browsers. But it turns out, that it's a bit easier to > implement and much easier to make "clean" code and project setup, when we > require ECMAScript6. ES6 is widely supported by all current browsers, but not > by the Internet Explorer 11 (is still supported by Microsoft and used in some > enterprise environment). > > The release date of Tobago 5 seems to be later this year. > > As a solution, I would prefer to remove IE11 support for Tobago 5 and support > Tobago 4 a longer time (with bugfixes and backports). > > Any suggestions? > > Regards, > > Udo > > > -- Dipl.-Math. Udo Schnurpfeil - Managing Director IRIAN Deutschland GmbH - Koppelstr. 4a - 26135 Oldenburg - Germany mobile +49 174 9784746 - fax +49 441 99922161 mailto:udo.schnurpf...@irian.eu - http://www.irian.eu/
Browser-Support for Tobago 5
Hi folks, Tobago 5 is now under development and the plan is to refactor all the JavaScript code to TypeScript. With this, we want to clean up code and throw old workarounds away. The basic idea is to write TypeScript and generate a compatible JavaScript for all supported browsers. But it turns out, that it's a bit easier to implement and much easier to make "clean" code and project setup, when we require ECMAScript6. ES6 is widely supported by all current browsers, but not by the Internet Explorer 11 (is still supported by Microsoft and used in some enterprise environment). The release date of Tobago 5 seems to be later this year. As a solution, I would prefer to remove IE11 support for Tobago 5 and support Tobago 4 a longer time (with bugfixes and backports). Any suggestions? Regards, Udo
Re: [Tobago] tobago-vm.apache.org/
Hi, I've startet the system. My uptime-checker didn't called me... Thanks for the info. Regards, Udo Am 26.03.19 um 19:16 schrieb jfrm.mau...@gmail.com: > > Hi, > > I cannot reach: http://tobago-vm.apache.org/ > > Is the site in maintenance ? > > Regards >
Re: [TOBAGO] tag error
Hello Jean-Francois, I've just tested the fragment in an MyFaces setup without Tobago. The problem still occurs. So, please file an issue at https://issues.apache.org/jira/projects/MYFACES (you will need a login (for free)). It seems to be a problem with Facelets. Regards, Udo Am 26.01.19 um 17:54 schrieb jfrm.mau...@gmail.com: > > Hi, > > Thank you for taking time for this. > > Le 26/01/2019 à 11:31, Udo Schnurpfeil a écrit : >> Which App-Server you are using? > > I use tomEE webprofile 8.0.0-M1. > > I also saw the mixing of tag in html source. I suspected a namespace > mismatch but I was not able to identify the cause playing with the > xhtml source and debug as I don't know much about tobago sources. > > Regards >
Re: [TOBAGO] tag error
Hi, that's weird. When I turn debugging on for the debug writer like this in the logback.xml you can see all start and ent-tags: start element: 'dl' start element: 'dt' start element: 'math' start element: 'mi' end element: 'mi' end element: 'math' *1 start element: 'dd' end element: 'dd' start element: 'dt' start element: 'math' start element: 'mi' end element: 'mi' end element: 'math' start element: 'dd' end element: 'dd' *2 start element: 'dt' start element: 'math' start element: 'mi' end element: 'mi' end element: 'math' start element: 'dd' end element: 'dd' end element: 'dt' end element: 'dt' *3 end element: 'dt' *4 Here you can see the problem. At position *1 and *2 the end tag "dt" is missing, it will be called later at the end *3 and *4. The DebugResponseWriterWrapper class is only for debugging, it turns out something went wrong. It's very strict, so we find problems that we wouldn't. You can turn it off, with enabling the production mode. But that is not a solution, of course. Anyway, the problem can be seen in the Source-View of e.g. Firefox. The HTML is not valid, and the wrong tags a marked red. I've tested with MyFaces and Mojarra and both has the same result. I've tested with Jetty and TomEE and found the problem in Jetty, also with a newer version. The problem occurred to me, while Jetty is reading/parsing the Facelet. The same happens, when replacing with . There is no problem without the namespaces. Which App-Server you are using? Regards, Udo Am 26.01.19 um 09:16 schrieb jfrm.mau...@gmail.com: > > Hi, > > Using Tobago 4.3.0, I see the below error when I use the following > xhtml page. I tried to make this page as small as possible to > reproduce the error. > If I remove one of the group the error is removed. > I work on windows 10 and both firefox or opera have the same behaviour. > > Could you please advice or correct me ? > > Regards > > xhtml page: > --- > > http://java.sun.com/jsf/facelets; > xmlns:xs="http://www.w3.org/2001/XMLSchema; > xmlns:f="http://java.sun.com/jsf/core; > xmlns="http://www.w3.org/1999/xhtml; > xmlns:tc="http://myfaces.apache.org/tobago/component; > xmlns:xhtml="http://www.w3.org/1999/xhtml; > > > > > > http://www.w3.org/1998/Math/MathML; > > N > > > nombre > > http://www.w3.org/1998/Math/MathML;> > C > > > constante > > http://www.w3.org/1998/Math/MathML;> > σ > > > étendue > > > > > ERROR: > - > > janv. 25, 2019 5:50:57 PM > org.apache.myfaces.tobago.internal.webapp.DebugResponseWriterWrapper > endElement > GRAVE: Element end with name='HTML' doesn't match with top element on > the stack='BODY'. > java.lang.IllegalArgumentException > at > org.apache.myfaces.tobago.internal.webapp.DebugResponseWriterWrapper.endElement(DebugResponseWriterWrapper.java:226) > at > org.apache.myfaces.tobago.internal.renderkit.renderer.PageRenderer.encodeEnd(PageRenderer.java:366) > at > javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:675) > at > javax.faces.component.UIComponentBase.encodeAll(UIComponentBase.java:555) > at > javax.faces.component.UIComponentBase.encodeAll(UIComponentBase.java:551) > at > org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.renderView(FaceletViewDeclarationLanguage.java:1897) > at > org.apache.myfaces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:315) > at > javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:73) > at > org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:117) > at > org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:266) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:206) > at > org.apache.tomee.myfaces.TomEEWorkaroundFacesServlet.service(TomEEWorkaroundFacesServlet.java:47) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) > at > org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) > at > org.apache.openejb.server.httpd.EEFilter.doFilter(EEFilter.java:65) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) > at > org.apache.myfaces.tobago.facelets.FixCharacterEncodingFilter.doFilter(FixCharacterEncodingFilter.java:54) > at >
Re: Tobago demo-4-release unreachable
Hi, thank you for the hint. I've just started the service. Happy new year! Regards Udo Am 02.01.19 um 10:28 schrieb jfrm.mau...@gmail.com: > Hi, > > Since several days, I obtain the error message below for : > http://tobago-vm.apache.org/demo-4-release/ > > Service Unavailable > The server is temporarily unable to service your request due to > maintenance downtime or capacity problems. Please try again later. > > Is it really a maintenance downtime ? > > Happy new year to everyone. > > Regards >
[ANNOUNCE] Apache Tobago 2.2.0, 3.1.0 and 4.3.0 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.2.0, 3.1.0 and 4.3.0. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main features Tobago 4.3.0 * New toggle component: * Update to Bootstrap 4.1.3 * Update to jQuery 3 * Vertical align vor Sheets * "plain" attribute * "keepLineBreaks" attribute * Icons in FacesMessages * tooltip for * java.util.Calendar and java.time.DateTime support for * LabelLayout attributes gridLeft, gridRight * Passwords aren't sent to the client * Bugfixes Tobago 3.1.0 * Update to jQuery 3 * Passwords aren't sent to the client * Bugfixes Tobago 2.2.0 * Update to jQuery 3 (IE 8 is no longer supported!) * PageState is usable for layout * Passwords aren't sent to the client * Bugfixes Changes --- Please check the release notes for each version at these URLs for a full list of the changes: Tobago 4.3.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=12342850 Tobago 3.1.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=12342388 Tobago 2.2.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=12342740 For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
Re: Fwd: Tobago 3.0.6 - Encoding problems with tc:textarea etc in tc:tabGroup
Hi Marko, I can't reproduce the issue until now (no WAS 8.0 available). I've a running example with WAS 8.5.5.13, this might help you to find the error. Here's what I've tested: Starting WAS 8.5.5.13 via Docker (see https://hub.docker.com/r/ibmcom/websphere-traditional/) $ echo "test1234">PASSWORD $ docker run --name test -h test -v $(pwd)/PASSWORD:/tmp/PASSWORD -p 9043:9043 -p 9443:9443 -d ibmcom/websphere-traditional:8.5.5.13-profile Browse to https://localhost:9043/ibm/console/ and use wsadmin/test1234 to login. Checkout my example (slightly modified Tobago 3.0.7-SNAPSHOT demo): $ git clone https://github.com/lofwyr14/myfaces-tobago.git test $ cd test $ git checkout test-websphere-umlauts $ mvn Deploy tobago-example/tobago-example-demo/target/tobago-example-demo.war into WAS e.g. on context path /demo Check these URLs (different switchType): https://localhost:9443/demo/faces/content/20-component/070-tab/00-client/tab-client.xhtml https://localhost:9443/demo/faces/content/20-component/070-tab/01-ajax/tab-ajax.xhtml https://localhost:9443/demo/faces/content/20-component/070-tab/02-server/tab-server.xhtml If this is running for you, you may test to deploy the tobago-example-demo.war in your 8.0 WAS. Or you may test to deploy your application into the docker 8.5 WAS. Hope that helps Regards, Udo Am 23.05.18 um 15:35 schrieb Henning Nöth: > FYI > > > Weitergeleitete Nachricht > Betreff: Tobago 3.0.6 - Encoding problems with tc:textarea etc in > tc:tabGroup > Datum: Wed, 23 May 2018 12:54:18 + > Von: Voß, Marko <marko.v...@cgi.com> > Antwort an: MyFaces Discussion <users@myfaces.apache.org> > An: users@myfaces.apache.org <users@myfaces.apache.org> > > Hello, > > we are using Tobago 3.0.6 as we have to support WebSphere 8.0. > > We experience some issues. One of them is that we get encoding issues > when sending german umlauts and other special characters as values of > tc:textArea or tc:selectManyCheckbox as child components of tc:tabGroup. > I validated this issue and figured out, that the encoding issues are > already present in > facesContext.getExternalContext().getRequestParameterMap(). > > For example: Having the text "Örtlichkeit" as a value of a tc:textArea > component with id "test" results in a key-value-pair: > > test=örtlichkeit > > The encoding of the HTML document in the browser is displayed correctly > as UTF-8. > > Please help. > > Kind regards, > > Marko Voß > -- Dipl.-Math. Udo Schnurpfeil - Managing Director IRIAN Deutschland GmbH - Poststr. 1-3 - 26122 Oldenburg - Germany mobile +49 174 9784746 - fax +49 441 99922161 mailto:udo.schnurpf...@irian.eu - http://www.irian.eu/
[ANNOUNCE] Apache Tobago 4.2.1 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 4.2.1. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main features Bugfixes Changes --- Please check the release notes at http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=12342849 for a full list of the changes in this version. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
[ANNOUNCE] Apache Tobago 2.1.1 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.1.1. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main new features of this release - * Bugfixes Changes --- Please check the release notes at https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=Html=12341246 for a full list of the changes in this version. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
[ANNOUNCE] Apache Tobago 4.0.0 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 4.0.0. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript. Main new features - Generally the ideas of Tobago 3 are continued. You can find an overview in the demo: http://tobago-vm.apache.org/demo-4-release/content/10-intro/28-new+in+4+0/new+in+4+0.xhtml A migration guide you will find also in the demo: http://tobago-vm.apache.org/demo-4-release/content/10-intro/50-migration/96-migration/migration40.xhtml Changes --- Please check the release notes at http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=Html=12338728 for a full list of the changes in this version. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
Re: [TOBAGO] How to setup my own PageRenderer in 3.0.6
Hi, I've testet it, and I found 2 additional points in the faces-config.xml: You need to define the render-kit-it: tobago javax.faces.Form Page org.apache.myfaces.tobago.example.demo.DemoPageRenderer and you should define an ordering, to select reliablely the double defined renderer: tobago_core Regards, Udo Am 07.12.17 um 23:02 schrieb Udo Schnurpfeil: > Hi Marko, > > the voting for 4.0.0 ist just done. The release will be available via > the Maven repos very soon. Tomorrow the websites will be updated. > > I'll check the configuration of own renderers, that should work. > > Regards > > Udo > > > Am 07.12.17 um 14:39 schrieb Voß, Marko: >> Hello, >> >> I need to setup my own PageRenderer in Tobago 3.0.6 as we need to setup >> custom Meta information. 4.0.0 is not yet released and we are in a hurry to >> get into production this month. >> >> I tried this in faces-config.xml: >> >> >> >> javax.faces.Form >> Page >> foo.bar.MyRenderer >> >> >> >> MyRenderer extends PageRenderer. >> >> It does not work. MyRenderer is not being used. >> >> Thank you very much. >> >> Kind regards, >> Marko >>
Re: [TOBAGO] How to setup my own PageRenderer in 3.0.6
Hi Marko, the voting for 4.0.0 ist just done. The release will be available via the Maven repos very soon. Tomorrow the websites will be updated. I'll check the configuration of own renderers, that should work. Regards Udo Am 07.12.17 um 14:39 schrieb Voß, Marko: > Hello, > > I need to setup my own PageRenderer in Tobago 3.0.6 as we need to setup > custom Meta information. 4.0.0 is not yet released and we are in a hurry to > get into production this month. > > I tried this in faces-config.xml: > > > > javax.faces.Form > Page > foo.bar.MyRenderer > > > > MyRenderer extends PageRenderer. > > It does not work. MyRenderer is not being used. > > Thank you very much. > > Kind regards, > Marko >
[ANNOUNCE] Apache Tobago 3.0.6 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 3.0.6. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main new features of this release - * Bugfixes Changes --- Please check the release notes at http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=Html=12341574 for a full list of the changes in this version. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
[ANNOUNCE] Apache Tobago 3.0.5 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.1.0. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main new features of this release - * Bugfixes Changes --- Please check the release notes at http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=Html=12340325 for a full list of the changes in this version. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
[ANNOUNCE] Apache Tobago 2.1.0 released
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.1.0. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main new features of this release - * File Upload: Drag and Drop support and AJAX support * Bugfixes Changes --- Please check the release notes at http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=Html=12338208 for a full list of the changes in this version. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
[ANNOUNCE] Apache Tobago 3.0.1
The Apache MyFaces team is pleased to announce the release of Apache Tobago 3.0.1. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript Main new features - * bugfixes * update versions of dependencies Changes --- Please check the release notes at http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=Html=12338730 for a full list of the changes in this version. Known limitations and bugs -- The classic grid layout manager is not working exactly in the same manner as before. Here are some issues, especially for vertical layout. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
[ANNOUNCE] Apache Tobago 3.0.0 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 3.0.0. Apache Tobago is a component library for JavaServer Faces (JSF) that allows to write web-applications without the need of coding HTML, CSS and JavaScript. Main new features - * LayoutManager moved from Server to CSS (or JS in limited cases) * Themes using CSS lib Bootstrap 4 http://getbootstrap.com/ * Responsiveness * Simplify many things by using current technologies * Easier to integrate Tobago in other projects * Easier to integrate libraries in Tobago * In general: do less magic, but more standard A more detailed list you will find in the demo: http://irian.biz/tobago-example-demo/faces/content/10-intro/30-new+in+3+0/new+in+3+0.xhtml Changes --- Please check the release notes at http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273=Html=12325880 for a full list of the changes in this version. A migration guide you will find in the demo: http://irian.biz/tobago-example-demo/faces/content/10-intro/50-migration/97-migration/migration30.xhtml Known limitations and bugs: --- The classic grid layout manager is not working exactly in the same manner as before. Here are some issues, especially for vertical layout. The main focus of this release was segment layout and flex layout. Currently we have only the standard theme. The other themes have only some colors changed, but are not fascinating. So these themes (scarborough, speyside, richmond, charlotteville) are excluded from the release. Also some examples are no longer in active development (test, addressbook). Some of its content should be migrated to the "demo", before removing them, but this may be done later. They are also excluded from the release. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, -The MyFaces team
Re: [ANNOUNCE] Apache Tobago 3.0.0-alpha-3 (xxx -> beta-1) Release
Hi, Matthew,
currently you can't use AJAX in <h:*> tag in Tobago.
You may have seen the main focus of Tobago is using their own tags,
thought all the HTML, CSS and JS stuff resolved automatically.
I think this problem is resolvable, but currently there is no timetable
to make the AJAX running with <h:*> tags.
(Technical detail: For h:-tags the default ClientBehaviorRenderer must
be use and for tc:-tags the TobagoClientBehaviorRenderer. Does anybody
know, if it's possible to wrap the ClientBehaviorRenderer or even get it
via the API?)
growl: currently on the todo list is something similar: TOBAGO-1550
ajaxStatus: Currently there is only a default implementation for that.
Customization whould be a nice feature.
swich: currently not included, but is no problem to build.
You may add feature requests to JIRA:
https://issues.apache.org/jira/browse/TOBAGO/
Regards,
Udo
Am 10.12.16 um 12:25 schrieb Matthew Broadhead:
> yes it looks like it is working now from this end. i have a couple of
> questions:
>
> i added tobago 3.0.0-alpha6 to a project (core and default theme). i was
> looking to replace primefaces calendar control because it didn't work
> for me in a particular situation. once i added the taglib to my xhtml
> header all the ajax commandlinks stopped working (e.g. value="example" action="#{bean.someAction}"> render="@form"/>)
>
> also as i only use a few primefaces controls i wanted to ask if you have
> similar controls to replace those. they are p:growl, p:ajaxStatus,
> p:switch
>
> On 10/12/2016 10:14, Udo Schnurpfeil wrote:
>> Hi,
>>
>> thanks for the hint. You got me not updating the demo to the current
>> beta 1 (this version uses an update of bootstrap which fixes the
>> problem).
>>
>> Now it's up to date, so it should work.
>>
>> Regards,
>>
>> Udo
>>
>>> Am 09.12.2016 um 14:55 schrieb Matthew Broadhead
>>> <matthew.broadh...@nbmlaw.co.uk>:
>>>
>>> Thanks I was not aware of Tobago. I looked through the demo and it
>>> has some great features like the calendar control and popup box among
>>> many other things.
>>>
>>> however on the "Select controls" demo the "Singleselection List",
>>> "Multiselection List" and "Shuttle List" seem to bleed outside their
>>> boundaries. i am using the latest version of Chrome
>>>
>>>> On 09/12/2016 13:58, Udo Schnurpfeil wrote:
>>>> The Apache MyFaces team is pleased to announce the release of Apache
>>>> Tobago 3.0.0-beta-1.
>>>>
>>>> More information at: http://myfaces.apache.org/tobago/
>>>>
>>>> For news to Tobago 3.0 see also (work in progress):
>>>> http://myfaces.apache.org/tobago/migration-3.0.html
>>>>
>>>> Regards,
>>>>
>>>> The MyFaces Team
Re: [ANNOUNCE] Apache Tobago 3.0.0-alpha-3 (xxx -> beta-1) Release
Hi, thanks for the hint. You got me not updating the demo to the current beta 1 (this version uses an update of bootstrap which fixes the problem). Now it's up to date, so it should work. Regards, Udo > Am 09.12.2016 um 14:55 schrieb Matthew Broadhead > <matthew.broadh...@nbmlaw.co.uk>: > > Thanks I was not aware of Tobago. I looked through the demo and it has some > great features like the calendar control and popup box among many other > things. > > however on the "Select controls" demo the "Singleselection List", > "Multiselection List" and "Shuttle List" seem to bleed outside their > boundaries. i am using the latest version of Chrome > >> On 09/12/2016 13:58, Udo Schnurpfeil wrote: >> The Apache MyFaces team is pleased to announce the release of Apache >> Tobago 3.0.0-beta-1. >> >> More information at: http://myfaces.apache.org/tobago/ >> >> For news to Tobago 3.0 see also (work in progress): >> http://myfaces.apache.org/tobago/migration-3.0.html >> >> Regards, >> >> The MyFaces Team
[ANNOUNCE] Apache Tobago 3.0.0-beta-1 Release
Sorry, subject was wrong... Am 09.12.16 um 13:58 schrieb Udo Schnurpfeil: > The Apache MyFaces team is pleased to announce the release of Apache > Tobago 3.0.0-beta-1. > > More information at: http://myfaces.apache.org/tobago/ > > For news to Tobago 3.0 see also (work in progress): > http://myfaces.apache.org/tobago/migration-3.0.html > > Regards, > > The MyFaces Team >
[ANNOUNCE] Apache Tobago 3.0.0-alpha-3 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 3.0.0-beta-1. More information at: http://myfaces.apache.org/tobago/ For news to Tobago 3.0 see also (work in progress): http://myfaces.apache.org/tobago/migration-3.0.html Regards, The MyFaces Team
[ANNOUNCE] Apache Tobago 3.0.0-alpha-6 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 3.0.0-alpha-6. More information at: http://myfaces.apache.org/tobago/ For news to Tobago 3.0 see also (work in progress): http://myfaces.apache.org/tobago/migration-3.0.html Regards, The MyFaces Team
[Tobago] Removal of old ToolBar
Hi, sorry for my last e-mail. (That was the wrong user-list...) But now in English: I'll remove the following tags for Tobago 3.0: tc:toolBar tc:toolBarSeparator tc:toolBarCommand use instead: or and the "bar"-facet. Regards, Udo
Ausbau des alten ToolBar
Hallo, ich werde gleich den alten ToolBar deaktivieren. Soweit ich weiss, wird der ohnehin nicht genutzt, aber falls doch... Diese Tags sind betroffen: tc:toolBar tc:toolBarSeparator tc:toolBarCommand Alternative: bzw. und ggf. die Facette "bar". Gruß Udo -- Dipl.-Math. Udo Schnurpfeil - Managing Director IRIAN Deutschland GmbH - Poststr. 1-3 - 26122 Oldenburg - Germany mobile +49 174 9784746 - fax +49 441 99922161 mailto:udo.schnurpf...@irian.eu - http://www.irian.eu/ signature.asc Description: OpenPGP digital signature
[ANNOUNCE] Apache Tobago 3.0.0-alpha-3 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 3.0.0-alpha-3. More information at: http://myfaces.apache.org/tobago/ For news to Tobago 3.0 see also (work in progress): http://myfaces.apache.org/tobago/migration-3.0.html Regards, The MyFaces Team
[ANNOUNCE] Apache Tobago 2.0.9 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.0.9. More information at: http://myfaces.apache.org/tobago/ For news to Tobago 2.0 see also: http://myfaces.apache.org/tobago/new-2.0.html Regards, The MyFaces Team
[ANNOUNCE] Apache Tobago 3.0.0-alpha-2 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 3.0.0-alpha-2. More information at: http://myfaces.apache.org/tobago/ For news to Tobago 3.0 see also (work in progress): http://myfaces.apache.org/tobago/migration-3.0.html Regards, The MyFaces Team
[ANNOUNCE] Apache Tobago 1.0.42 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 1.0.42. This is a maintenance release. More information at: http://myfaces.apache.org/tobago/ Regards, The MyFaces Team
[ANNOUNCE] Apache Tobago 2.0.8 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.0.8. More information at: http://myfaces.apache.org/tobago/ For news to Tobago 2.0 see also: http://myfaces.apache.org/tobago/new-2.0.html Regards, The MyFaces Team
[ANNOUNCE] Apache Tobago 2.0.5 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.0.5. More information at: http://myfaces.apache.org/tobago/ See also: http://myfaces.apache.org/tobago/new-2.0.html Have a happy christmas, The MyFaces team
[ANNOUNCE] Apache Tobago 2.0.4 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.0.4. More information at: http://myfaces.apache.org/tobago/ See also: http://myfaces.apache.org/tobago/new-2.0.html Have fun, The MyFaces team
[ANNOUNCE] Apache Tobago 2.0.2 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.0.2. Apache Tobago is a component library for JSF. Main new features - Please check the release notes at https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12327500 for a full list of the changes. See also: http://myfaces.apache.org/tobago/new-2.0.html For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, The MyFaces team
[ANNOUNCE] Apache Tobago 2.0.0 Release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The Apache MyFaces team is pleased to announce the release of Apache Tobago 2.0.0. Apache Tobago is a component library for JSF. Main new features - - See: http://myfaces.apache.org/tobago/new-2.0.html Please check the release notes at https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12321253 for a full list of the changes. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/. Have fun, The MyFaces team -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJT0AvjAAoJEAEbRra2zTKA86sP/1HD0qkH5JRZJLwGd58EDrRX mQXm2YhSUSxpjzmO/0E4eJ+9cQX+XS6kQlpUDTTrxjrG5yJC++/GDwWXIN36hhGi ZWyBG5dUqUPYM/tKr9bzOhPT947F+05+tGdkyJZw58l8WweWTmvoRu/pO+4EPe6w wIfgqQOmFZKgQm9XM1Rt1+KkJphnFq7CYwVamwJAH0D06hUI+8EGS6z4xnKXuyAJ 8dZKaVQ4qCqYf0p+KkxSvxD6svUaOU7L6aAtwTecWHIzxcnYyFKIXa92kezwJqev jHkxKcFxPjdpsDjo6acAeJD/LPchac5co1fxZwLQKi0bkoQEJdg9c5TYgJyEdjsH pVjKxEjG9ftK0KYrksW+qIZQjbdJDO+CX5eHlPlpFE8Zw65sn2Q3jFugOholiWHx M93arcCEJ1cvuyL+ucebieuGhaKrgbhZmCdA7eLCTxbARG15ZFonFrZESF3OcF2x PH8Y1Zdq56vSVjPNXOvUEa419QWSoPilYfTFjs9t1VyRucD4t+8S+v0FkMseY1uk 4j+fgZ4QYKvjGGEb7kRy2H1OXwEanWAn3+2KszDTuNVidnqR/T9lPGVGVAMkrwm/ f3V1by7GPvl2vFoXetvRe9gN8ycn+aXnWhzLd4xn2JzrUW9hqnqrZ9C+ZF3z1XJg ZVsH+LkRbtf8a7tbRA4T =X20l -END PGP SIGNATURE-
Re: [Tobago] h:commandButton action are not invoked
Hi, sorry for the late answer... Please use tc:button on Tobago pages. The h: HTML lib is currently not supported in Tobago. The reason for the h:commandButton is not working is, that Tobago uses it's own submit JS function, which encapsulate extended functionality. Regards, Udo Am 07.05.14 17:59, schrieb Anton Sysoev: Hi. I have a project based on Tobago 2.0 alpha 3 + Tomcat 7.0.34 + MyFaces Core 2.1.14 and it works fine. Now I need one page based on only core jsf components. I try this example http://www.mkyong.com/jsf2/jsf-2-actionlistener-example/ inside my project and I get that h:commandButton binded method are not invoked. I have created a new project without Tobago to test example above and it worked. Next I have added tobago jars in WEB-INF/lib and I got h:commandButton binded method are not invoked. Is this a bug or I’m doing something wrong? Thanks.
Re: [Tobago] Tobago Version 1.0.* and Tomcat 7
Hi, Tobago 1.0.x should run on Tomcat 7 and later. I'll update the webside: http://myfaces.apache.org/tobago/compatibility.html I've a running installation of a Tobago 1.0.x Application with Tomcat 7.0.47 Regards Udo Am 15.01.14 00:30, schrieb d.o@gmx.net: Hello all, Could you please let me know whether Tobago 1.0.* is still supported in Tomcat 7 (or later versions)? Thanks a lot for your help and best wishes, Dom
[ANNOUNCE] Apache Tobago 1.5.11 Release
The Apache MyFaces team is pleased to announce the release of Apache Tobago 1.5.11. Apache Tobago is a component library for JSF. Changes --- Please check the release notes at https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12324453 for a full list of the changes in this release. For more information about Apache Tobago, please visit http://myfaces.apache.org/tobago/ Have fun, -The MyFaces team
Re: [Tobago] Configuring of renderer class
Hello Hani,
since Tobago 1.5 the renderers must be configured in the faces-config.xml
This will be done automatically, when using generated components like
from org.apache.myfaces.tobago.internal.taglib.component.BoxTagDeclaration
I'll add a notice in the migration guild.
Hope that helps.
Regards,
Udo
Am 26.07.13 17:25, schrieb Abushammala, Hani (EXTERN: BERIS):
Hi,
I`ve developed a component with own renderer class, but the renderer could
not be called after migration from Tobago 1.0.39 to 1.5.10 .
I don`t know how I can configure the renderer for the new component in Tobago.
We use in the application an own theme, so I added the renderer class to the
resource path of the theme, but it doesn`t work now with Tobago 1.5.10.
Log:
WARN org.apache.myfaces.renderkit.html.HtmlRenderKitImpl - Unsupported
component-family/renderer-type: DynamicPanelFamily/DynamicPanel
Jul 26, 2013 5:15:33 PM org.apache.catalina.core.ApplicationContext log
INFO: No Renderer found for component {Component-Path : [Class:
org.apache.myfaces.tobago.component.UIViewRoot,ViewId:/test.jsp][Class:
org.apache.myfaces.tobago.component.UIPage,Id: page][Class:
org.apache.myfaces.tobago.component.UIPanel,Id: j_id_jsp_106584_5][Class:
org.apache.myfaces.tobago.component.UIPanel,Id: j_id_jsp_106584_7][Class:
org.apache.myfaces.tobago.component.UIPanel,Id:
j_id_jsp_2134803194_1pc10][Class:
org.apache.myfaces.tobago.component.UITabGroup,Id: tabGroupRang][Class:
org.apache.myfaces.tobago.component.UITab,Id:
j_id_jsp_2134803194_44pc10][Class:
org.apache.myfaces.tobago.component.UIBox,Id:
j_id_jsp_2134803194_54pc10][Class:
org.apache.myfaces.tobago.component.UISheet,Id: sheet][Class:
org.apache.myfaces.tobago.component.UIColumn,Id: pnPanel1][Class:
de.volkswagen.prolog.web.components.UIDynamicPanel,Id:
j_id_jsp_2134803194_87pc10]} (component-family=DynamicPanelFamily,
renderer-type=DynamicPanel)
ERROR org.apache.myfaces.tobago.renderkit.TobagoRenderKit - The class which
was found by the ResourceManager cannot be found or instantiated:
classname='DynamicPanel'
WARN javax.faces.component.UIComponentBase - No Renderer found for component
{Component-Path : [Class:
org.apache.myfaces.tobago.component.UIViewRoot,ViewId:/test.jsp][Class:
org.apache.myfaces.tobago.component.UIPage,Id: page][Class:
org.apache.myfaces.tobago.component.UIPanel,Id: j_id_jsp_106584_5][Class:
org.apache.myfaces.tobago.component.UIPanel,Id: j_id_jsp_106584_7][Class:
org.apache.myfaces.tobago.component.UIPanel,Id:
j_id_jsp_2134803194_1pc10][Class:
org.apache.myfaces.tobago.component.UITabGroup,Id: tabGroupRang][Class:
org.apache.myfaces.tobago.component.UITab,Id:
j_id_jsp_2134803194_44pc10][Class:
org.apache.myfaces.tobago.component.UIBox,Id:
j_id_jsp_2134803194_54pc10][Class:
org.apache.myfaces.tobago.component.UISheet,Id: sheet][Class:
org.apache.myfaces.tobago.component.UIColumn,Id: pnPanel1][Class:
de.volkswagen.prolog.web.components.UIDynamicPanel,Id:
j_id_jsp_2134803194_87pc10]} (component-family=DynamicPanelFamily,
renderer-type=DynamicPanel)
WARN org.apache.myfaces.tobago.internal.component.AbstractUISheet - Found no
component inside of a UIColumn: column
id='page:j_id_jsp_2134803194_44pc10:sheet:pnPanel1'. Creating a dummy with
id='page:j_id_jsp_2134803194_44pc10:sheet:j_id101'!
WARN org.apache.myfaces.tobago.internal.component.AbstractUISheet - Found no
component inside of a UIColumn: column
id='page:j_id_jsp_2134803194_135pc10:sheet2:pnPanel2'. Creating a dummy with
id='page:j_id_jsp_2134803194_135pc10:sheet2:j_id102'!
WARN org.apache.myfaces.tobago.layout.PixelMeasure - Not enough space!
value=0
WARN org.apache.myfaces.tobago.util.LayoutInfo - Space left after spreading
: 1262px! clientId='page:j_id_jsp_2134803194_44pc10:sheet'
WARN org.apache.myfaces.tobago.util.LayoutInfo - Space left after spreading
: 1262px! clientId='page:j_id_jsp_2134803194_135pc10:sheet2'
WARN org.apache.myfaces.renderkit.html.HtmlRenderKitImpl - Unsupported
component-family/renderer-type: DynamicPanelFamily/DynamicPanel
ERROR org.apache.myfaces.tobago.renderkit.TobagoRenderKit - The class which
was found by the ResourceManager cannot be found or instantiated:
classname='DynamicPanel'
WARN org.apache.myfaces.renderkit.html.HtmlRenderKitImpl - Unsupported
component-family/renderer-type: DynamicPanelFamily/DynamicPanel
ERROR org.apache.myfaces.tobago.renderkit.TobagoRenderKit - The class which
was found by the ResourceManager cannot be found or instantiated:
classname='DynamicPanel'
Jul 26, 2013 5:15:33 PM org.apache.catalina.core.ApplicationContext log
INFO: No Renderer found for component {Component-Path : [Class:
org.apache.myfaces.tobago.component.UIViewRoot,ViewId:/test.jsp][Class:
org.apache.myfaces.tobago.component.UIPage,Id: page][Class:
org.apache.myfaces.tobago.component.UIPanel,Id: j_id_jsp_106584_5][Class:
Re: [TOBAGO] Stick items at the top
Hi, you are right, please use tc:panel. Regards Udo Am 16.10.12 19:22, schrieb AM: Hi Udo, Thanks for your help, i tried it with the same but instead of tc:cell i used tc:out. i hope i am now right remember about it but: tc:cell shall get banned at any newer version. 2012/10/16 Udo Schnurpfeil udo.schnurpf...@irian.eu Hi, you can fix it, with defining a rows=fixed;* in the layout of the box and putting a tc:cell/ after the panel (which gets the *). Hope that helps Udo Am 12.10.12 13:28, schrieb AM: Hello dear users! (in this case an item is my tc:box) I have a layout-problem only when i use Firefox. My tc:box shown below is centered at the height of my display, but with IE it works well and is also always sticking near my menue-bar at the top. at the faq i found this link: http://myfaces.apache.org/tobago/compatibility.html and i also tried to run my appl. with ff9 :( I use: tobago v 1.0.38 and myfaces 1.1.8 My code (prblem): layout:proj jsp:body f:facet name=layout tc:gridLayout rows=fixed;*/ /f:facet tc:box label=Login f:facet name=layout tc:gridLayout rows=fixed/ /f:facet tc:panel/tc:panel /tc:box tc:out/ /jsp:body /layout:proj My code menubar (if necessary): f:facet name=menuBar tc:menuBar tc:menu .. /tc:menu /tc:menuBar /f:facet thanks a lot and wishing a restful weekend! :)
Re: [TOBAGO] Stick items at the top
Hi, you can fix it, with defining a rows=fixed;* in the layout of the box and putting a tc:cell/ after the panel (which gets the *). Hope that helps Udo Am 12.10.12 13:28, schrieb AM: Hello dear users! (in this case an item is my tc:box) I have a layout-problem only when i use Firefox. My tc:box shown below is centered at the height of my display, but with IE it works well and is also always sticking near my menue-bar at the top. at the faq i found this link: http://myfaces.apache.org/tobago/compatibility.html and i also tried to run my appl. with ff9 :( I use: tobago v 1.0.38 and myfaces 1.1.8 My code (prblem): layout:proj jsp:body f:facet name=layout tc:gridLayout rows=fixed;*/ /f:facet tc:box label=Login f:facet name=layout tc:gridLayout rows=fixed/ /f:facet tc:panel/tc:panel /tc:box tc:out/ /jsp:body /layout:proj My code menubar (if necessary): f:facet name=menuBar tc:menuBar tc:menu .. /tc:menu /tc:menuBar /f:facet thanks a lot and wishing a restful weekend! :)
Re: [Tobago] Is migration to Tobago 1.5.* recommended?
Hi Dom, sorry for the late response. Generally I encourage you to migrate to 1.5.x. I think you should update JSF to 1.2 and Tobago to 1.5.x at the same time. That might be less effort for programming and testing. In special, it depends a little from you application, because we need some API changes using the tc:tree. These changes we make in version 1.6.x. If you are using the tree minor or not, you can migrate to 1.5.x and later to 1.6.x with low effort. If you are using the tree intensively, you may wait until 1.6.x will be release. Both versions will contain bugfixes and important features for a while. Regards, Udo Am 12.04.12 13:13, schrieb d.o@gmx.net: Dear all, I will repeat my question: Would you recommend migrating from Tobago 1.0.* to Tobago 1.5.* at this time (1.5.4)? Furthermore, how would you suggest to proceed: First migrate to JSF 1.2, then to Tobago 1.5 (if that is possible), or migrate both at the same time? Thanks for your help, Dom Original-Nachricht Datum: Thu, 26 Jan 2012 05:40:07 +0100 Von: d.o@gmx.net An: users@myfaces.apache.org Betreff: [Tobago] Is migration to Tobago 1.5.* recommended? Dear developers, dear all, It is good to see that Tobago 1.5 has lost its beta status. Thanks for all the work and time you put into the development. The question is, do you recommend migrating from Tobago 1.0.* to 1.5.* at this stage? The migration guide (http://myfaces.apache.org/tobago/migration-1.5.html) still says work in progress. So is there still information missing in the guide, or is version 1.5.* not yet stable enough? Could you please clarify? Another suggestion: In the migration guide, you could list a few advantages (and disadvantages) to motivate migration. Thanks a lot. Best, Dom -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Re: [Tobago] Problem while determining the view id
Hallo Hani, sorry, but I'm not sure what your scenario is. Where do you use '../faces' and why? In the link attribute of a tc:link or tc:button or in navigation rules? Or in links from outside of JSF? There is a part in JSF that guesses the view id from the URL and it might be a problem when using ../faces. What is the application case? Regards, Udo Am 15.02.12 14:59, schrieb Abushammala, Hani (EXTERN: conceptQ): Hello, I've a problem by determining the view id when using the url '../faces' and '../faces/' to call the web application. Is it a normal behavior of Tobago or jsf that the determined view id null or '/' in this case? I got this error log Assumed extension mapping, but there is no extension in '/faces' or '/faces/'. In this case the RestoreViewExecutor of Tobago tries to create the view from ExternalContext.getRequestServletPath(). With '/faces' as ExternalContext.getRequestServletPath() the redirection doesn't works correctly, the redirection ignores the context path of the application. With '/faces/' as ExternalContext.getRequestServletPath() the restoring or creating the view doesn't works with null as view id. By calling the application with '../faces/' i've also noticed that the determining of ExternalContext.getRequestPathInfo() and ExternalContext.getRequestServletPath() returns different values on different servers (e.g tomcat and Websphere). The application details: Servlet mapping: servlet-mapping servlet-nameFacesServlet/servlet-name url-pattern/faces/*/url-pattern /servlet-mapping Libs: tobago-core-1.0.38.jar myfaces-impl-1.1.9.jar myfaces-api-1.1.9.jar Server: Tomcat 6.0.18 Websphere 6.1 Regards, Hani
Re: [Tobago] Text of labels is too much shifted to the top.
Hi dom, I totally agree with you. Please file a ticket in Jira. Regard, Udo Am 27.10.10 12:02, schrieb d.o@gmx.net: Hi all, the text of all labels is too much shifted to the top. Examples can be seen in the Tobago Demo for any of those themes: Richmond, Speyside, Charlotteville (http://www.irian.biz/tobago-example-demo). This happens to me with Firefox 3.6.11 and Tobago 1.0.30 (and obviously the Tobago version currently used in the demo). So, I think it should rather be vertically centered. Of course, one could do this by manipulating the CSS style, however I think the default behavior should be vertically centered. Since this might simply be a matter of taste, I didn't want to file a ticket in Jira and wanted to discuss it here first. What do you think? Best, dom
Re: [tobago] How to use tc:tree control for navigation
Hi Michael, the navigation of the tobago-example-demo is implemented with tc:tree. For Tobago 1.0 you need a Java object that holds the nodes, see navigation.jsp (you need a facet for action/navigation). For Tobago 1.5 you can also create the node directly in the page, see navigation.xhtml (the tree was reimplemented completely in 1.5). Regards, Udo Am 22.10.10 22:29, schrieb Michael Kakuschky: Hello, how to use the tc:tree control to navigate to pages? Is it possible? And if yes how I can set the outcome? Thanks regards Michael
Re: [Tobago] Multiple dynamically created menu items.
Hi DOM! I'm not sure what you are looking for. You can use this: Am 20.10.10 18:42, schrieb d.o@gmx.net: Dear all, Is it possible to dynamically create multiple tc:menuItems. I am looking for a similar behavior that can be implemented with tc:selectItems for e.g. tx:menuRadio. Something like: tc:menu label=test tc:menuItems tc:selectItems value=foo / /tc:menuItems /tc:menu Where foo references to a ListSelectItem in a backing bean. The elements in this list should be displayed as individual menu items. Thanks a lot for any hints. Greetings, dom
Re: [Tobago] Multiple dynamically created menu items.
(ups, pressed wrong key)
Hi DOM!
I'm not sure what you are looking for.
Do you know you can use this?
tx:menuRadio action=#{clientConfigController.submit}
value=#{clientConfigController.locale}
f:selectItems value=#{clientConfigController.localeItems} /
/tx:menuRadio
Are you looking for a similar to create more than one menuItem with actions?
If so. I think this will not work, because the selectItems doesn't
contains an action.
An other solution might be to use ui:repeat with facelets, but I
didn't tested it.
Regards,
Udo
Am 20.10.10 18:42, schrieb d.o@gmx.net:
Dear all,
Is it possible to dynamically create multiple tc:menuItems. I am looking for a similar behavior
that can be implemented with tc:selectItems for e.g. tx:menuRadio.
Something like:
tc:menu label=test
tc:menuItems
tc:selectItems value=foo /
/tc:menuItems
/tc:menu
Where foo references to a ListSelectItem in a backing bean. The elements
in this list should be displayed as individual menu items.
Thanks a lot for any hints.
Greetings,
dom
Re: [tobago] tx:in update problem
Hi Michael,
the behavior you describe seems to be normal for JSF (in the moment I
doesn't now that this has changed from JSF 1.1 to JSF 1.2).
When readonly is false the value will be submitted, but not written into
the model. After an action with outcome null the same view root will
be rendered again.
So the local value will be used instead of the actual value from the model.
If the action was completed and you do not need old value of other forms
on that page, you should return an outcome different from null to
create a new view.
Hope that helps.
Udo
Am 16.10.10 23:04, schrieb Michael Kakuschky:
Hello, I stripped down my tx:in update problem. In a simple JSP page
I have have to forms. If I click the button in the first form I want
to update the tx:in element in the second form. The update does only
works if the readonly attribute of the tc:in element is set to true.
But them I'm not able to edit the value. Is this a bug or is there a
way fix this behaviour?
Regards Michael
I use tobago 1.0.30 and Myfaces 1.1.18 with tomcat 6.0.18
Here is the page JSP Page
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f%
%@ taglib uri=http://myfaces.apache.org/tobago/component; prefix=tc%
%@ taglib uri=http://myfaces.apache.org/tobago/extension; prefix=tx%
%@ page contentType=text/html;charset=UTF-8 language=java%
f:view
tc:page
f:facet name=layout
tc:gridLayout columns=1* rows=fixed;fixed;* /
/f:facet
tc:form
tc:cell
tc:button label=addone action=#{myTestBean.addOne} /
/tc:cell
/tc:form
tc:form
tc:cell
tc:in value=#{myTestBean.theNumber} readonly=false /
/tc:cell
/tc:form
tc:cell /
/tc:page
/f:view
and the Bean looks like the following
public class MyTestBean {
Integer number = 11880;
public Integer getNumber() {
return number;
}
public void setNumber(Integer number) {
this.number = number;
}
public String addOne() {
number += 1;
return null;
}
}
Re: [tobago] Validation in Popups
Addition (but I don't think the problem rely on that):
Server:
Mac OS 10.6.4, Maven 2.2.1, Java 1.6.0_20
Clients:
Firefox 3.6.10, Mac OS 10.6.4
Safari 5.0.2, Mac OS 10.6.4
Internet Explorer 6.0, Windows XP SP 3
Internet Explorer 8.0, Windows 7
Firefox 3.6.8, Ubuntu 10.4
Am 08.10.10 18:30, schrieb Udo Schnurpfeil:
Hi Michael,
I've just rechecked you sample, but I can't reproduce the problem. So,
it may depends on some odd diffence of my and you environment.
Let be describe what I did:
1. svn co
https://svn.apache.org/repos/asf/myfaces/tobago/tags/tobago-1.0.30/example/demo/
demo
2. cd demo
3. edit src/main/webapp/popup-test.jsp (this is a modified version of
you sniplet, the EL to the Java code was removed)
%@ taglib uri=http://myfaces.apache.org/tobago/component;
prefix=tc %
%@ taglib uri=http://myfaces.apache.org/tobago/extension;
prefix=tx %
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f %
%@ taglib tagdir=/WEB-INF/tags/layout prefix=layout %
layout:overview
jsp:body
tc:box label=Test for Popups to be open in case of an validation
error
f:facet name=layout
tc:gridLayout rows=fixed;1*/
/f:facet
tc:form
tc:panel
f:facet name=layout
tc:gridLayout rows=fixed columns=fixed/
/f:facet
tc:button label=new item
tc:attribute name=renderedPartially value=non_modal_popup1/
f:facet name=popup
tc:popup width=500 height=325 id=non_modal_popup1 modal=true
tc:box label=create new item
f:facet name=layout
tc:gridLayout columns=1* rows=fixed;fixed/
/f:facet
tc:cell
tx:in label=contact name value=some value required=true/
/tc:cell
tc:cell
tc:button width=100 label=add
tc:attribute name=popupClose value=afterSubmit/
/tc:button
/tc:cell
/tc:box
/tc:popup
/f:facet
/tc:button
/tc:panel
/tc:form
/tc:box
/jsp:body
/layout:overview
4. mvn jetty:run-exploded
5. browse: http://localhost:8080/tobago-example-demo/faces/popup-test.jsp
6. click new item - popup opens
7. click add - popup closes
8. click new item - popup opens
9. remove the value of contact name
10. click add - popup keeps open and the input will be colored red
Can you check, if this works the same way on your box.
Regards,
Udo
Am 04.10.10 10:59, schrieb Volker Weber:
Hi Michael,
yes we have validation in Popups, but this is a bit hack like, nothing
to show as example.
The problem is the partial rendering and the popup handling in tobago
1.0.x:
If you need validation inside a popup, you should not close the popup
via popupClose attribute, but rerender the popup content partial and,
on success, close the popup via hidden button and javascript.
something like this should work, if you set the
#{myController.closePopup} value in your newItem action.
tc:cell
f:facet name=layout
tc:gridLayout colums=fixed;1* /
/f:facet
tc:button width=100 label=add action=#{myController.newitem}
tc:attribute name=popupClose value=afterSubmit/
/tc:button
tc:text escape=false
rendered=#{myController.closePopup}
value=script
type=\text/javascript\Tobago.submitAction('full clientId of
hiddenCloseButton');/script /
f:facet name=hiddenCloseButton
tc:button id=hiddenCloseButton
tc:attribute name=popupClose value=afterSubmit/
/tc:button
/f:facet
/tc:cell
In tobago 1.5 this would be easier.
Regards,
Volker
2010/10/4 Michael Kakuschkykakusc...@elbe-net.de:
Does nobody has an working example for validation in popus?
Regards Michael
Am 29.09.2010 08:57, schrieb Michael Kakuschky:
Hello Udo, thanks for the answer but my form is already around the
tc:button which I used to open the popup. Here is a snippset of my
original
version. The popup works and the form data will processed. Only
validations
and required checks doesn't work. In case of missing or wrong data
the pop
is just closing without calling the action method of the popups submit
button. Can you show on this example what's todo or maybe wrong ?
Thanks best regards Michael
tc:form
tc:panel
f:facet name=layout
tc:gridLayout rows=fixed columns=fixed /
/f:facet
tc:button label=new item
tc:attribute name=renderedPartially value=non_modal_popup1/
f:facet name=popup
tc:popup width=500 height=325 id=non_modal_popup1 modal=true
tc:box label=create new item
f:facet name=layout
tc:gridLayout columns=1* rows=fixed;fixed /
/f:facet
tc:cell
tx:in label=contact name
value=#{myController.itemToAdd.contact_name}
required=true /
/tc:cell
tc:cell
tc:button width=100 label=add action=#{myController.newitem}
tc:attribute name=popupClose value=afterSubmit/
/tc:button
/tc:cell
/tc:box
/tc:popup
/f:facet
/tc:button
/tc:panel
/tc:form
Am 28.09.2010 15:12, schrieb Udo Schnurpfeil:
Hello Michael,
please try to put the form outside of the command tag, which opens
the
popup. This should solve your problems.
The background is: The popup must be inside the form to consider
it was
already active.
Regards,
Udo
Am 23.09.10 22:29, schrieb Michael Kakuschky:
Hello, I have a form in a popup. Now it works fine and I add some
validators to it. I checked that they are executed
Re: [tobago] Validation in Popups
Hi Michael,
I've just rechecked you sample, but I can't reproduce the problem. So,
it may depends on some odd diffence of my and you environment.
Let be describe what I did:
1. svn co
https://svn.apache.org/repos/asf/myfaces/tobago/tags/tobago-1.0.30/example/demo/
demo
2. cd demo
3. edit src/main/webapp/popup-test.jsp (this is a modified version of
you sniplet, the EL to the Java code was removed)
%@ taglib uri=http://myfaces.apache.org/tobago/component; prefix=tc %
%@ taglib uri=http://myfaces.apache.org/tobago/extension; prefix=tx %
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f %
%@ taglib tagdir=/WEB-INF/tags/layout prefix=layout %
layout:overview
jsp:body
tc:box label=Test for Popups to be open in case of an validation error
f:facet name=layout
tc:gridLayout rows=fixed;1*/
/f:facet
tc:form
tc:panel
f:facet name=layout
tc:gridLayout rows=fixed columns=fixed/
/f:facet
tc:button label=new item
tc:attribute name=renderedPartially value=non_modal_popup1/
f:facet name=popup
tc:popup width=500 height=325 id=non_modal_popup1 modal=true
tc:box label=create new item
f:facet name=layout
tc:gridLayout columns=1* rows=fixed;fixed/
/f:facet
tc:cell
tx:in label=contact name value=some value required=true/
/tc:cell
tc:cell
tc:button width=100 label=add
tc:attribute name=popupClose value=afterSubmit/
/tc:button
/tc:cell
/tc:box
/tc:popup
/f:facet
/tc:button
/tc:panel
/tc:form
/tc:box
/jsp:body
/layout:overview
4. mvn jetty:run-exploded
5. browse: http://localhost:8080/tobago-example-demo/faces/popup-test.jsp
6. click new item - popup opens
7. click add - popup closes
8. click new item - popup opens
9. remove the value of contact name
10. click add - popup keeps open and the input will be colored red
Can you check, if this works the same way on your box.
Regards,
Udo
Am 04.10.10 10:59, schrieb Volker Weber:
Hi Michael,
yes we have validation in Popups, but this is a bit hack like, nothing
to show as example.
The problem is the partial rendering and the popup handling in tobago 1.0.x:
If you need validation inside a popup, you should not close the popup
via popupClose attribute, but rerender the popup content partial and,
on success, close the popup via hidden button and javascript.
something like this should work, if you set the
#{myController.closePopup} value in your newItem action.
tc:cell
f:facet name=layout
tc:gridLayout colums=fixed;1* /
/f:facet
tc:button width=100 label=add action=#{myController.newitem}
tc:attribute name=popupClose value=afterSubmit/
/tc:button
tc:text escape=false
rendered=#{myController.closePopup}
value=script
type=\text/javascript\Tobago.submitAction('full clientId of
hiddenCloseButton');/script /
f:facet name=hiddenCloseButton
tc:button id=hiddenCloseButton
tc:attribute name=popupClose value=afterSubmit/
/tc:button
/f:facet
/tc:cell
In tobago 1.5 this would be easier.
Regards,
Volker
2010/10/4 Michael Kakuschkykakusc...@elbe-net.de:
Does nobody has an working example for validation in popus?
Regards Michael
Am 29.09.2010 08:57, schrieb Michael Kakuschky:
Hello Udo, thanks for the answer but my form is already around the
tc:button which I used to open the popup. Here is a snippset of my original
version. The popup works and the form data will processed. Only validations
and required checks doesn't work. In case of missing or wrong data the pop
is just closing without calling the action method of the popups submit
button. Can you show on this example what's todo or maybe wrong ?
Thanks best regards Michael
tc:form
tc:panel
f:facet name=layout
tc:gridLayout rows=fixed columns=fixed /
/f:facet
tc:button label=new item
tc:attribute name=renderedPartially value=non_modal_popup1/
f:facet name=popup
tc:popup width=500 height=325 id=non_modal_popup1 modal=true
tc:box label=create new item
f:facet name=layout
tc:gridLayout columns=1* rows=fixed;fixed /
/f:facet
tc:cell
tx:in label=contact name value=#{myController.itemToAdd.contact_name}
required=true /
/tc:cell
tc:cell
tc:button width=100 label=add action=#{myController.newitem}
tc:attribute name=popupClose value=afterSubmit/
/tc:button
/tc:cell
/tc:box
/tc:popup
/f:facet
/tc:button
/tc:panel
/tc:form
Am 28.09.2010 15:12, schrieb Udo Schnurpfeil:
Hello Michael,
please try to put the form outside of the command tag, which opens the
popup. This should solve your problems.
The background is: The popup must be inside the form to consider it was
already active.
Regards,
Udo
Am 23.09.10 22:29, schrieb Michael Kakuschky:
Hello, I have a form in a popup. Now it works fine and I add some
validators to it. I checked that they are executed and throws the
ValidatorException if the input does not match the requirements.
In case of exceptions the action behind the popup form is not executed
but unfortunately the popup is closed without any notification about the
wrong input. Is there a way to keep the popup open so
Re: [tobago] Validation in Popups
Hello Michael, please try to put the form outside of the command tag, which opens the popup. This should solve your problems. The background is: The popup must be inside the form to consider it was already active. Regards, Udo Am 23.09.10 22:29, schrieb Michael Kakuschky: Hello, I have a form in a popup. Now it works fine and I add some validators to it. I checked that they are executed and throws the ValidatorException if the input does not match the requirements. In case of exceptions the action behind the popup form is not executed but unfortunately the popup is closed without any notification about the wrong input. Is there a way to keep the popup open so that the user is informed about the wrong input? thanks regards Michael
Re: [Tobago] FileUpload from popup supported?
Hello Michael, there are two options to use the fileupload, see http://myfaces.apache.org/tobago/faq.html#tobagofileupload The jar-option might be better than the filter-option. You can find an example in the addressbook demo. If you still have problems with the Java exceptions, please sent it, with the Tobago version and the way you chose (jar or filter). Regards, Udo An example you can find in the Am 21.09.10 09:56, schrieb Michael Kakuschky: Hello, I use a form in a popup to submit some data. It worked fine until I add the tx:file component to the form. If I submit the form with a file selected I receive the data but it seems that it corrupts somehow the memory and I got some strange Java exceptions about (existing) methods that can't be found. If the file upload is supported can somebody give me a basic example and maybe tell me which attributes have to be set and which maybe not? KInd regards Michael
Re: MyFaces Test with JSF 1.1
Hi Jakob, there is an easy solution to make myfaces-test12 usable to test applications running with JSF 1.1. I will create an Jira issue and fix that. To make the project build-able with JSF 1.1 is more complex and not needed for me. Regards, Udo Am 14.09.10 16:47, schrieb Jakob Korherr: Hi Udo, I guess the idea of shale-test (= original test12) was to provide support for both JSF 1.1 and 1.2, however test12 now only supports JSF 1.2. If you think it is easily possible to support both versions in one module, I'd prefer that. If not, we could create a test11 module and use the dependency plugin (or the shade plugin) to re-use existing classes from test12. Regards, Jakob 2010/9/14 Udo Schnurpfeilu...@schnurpfeil.de: Hi, in version 1.0.0 there is no support for JSF 1.1, but I've seen some code, that consider JSF 1.1. Is there a plan to make the test12 version also runnable with JSF 1.1? It seems to me, that we can build an artifact, that supports JSF 1.1 and 1.2 coexistent, to keep the management overhead small. Regards, Udo
MyFaces Test with JSF 1.1
Hi, in version 1.0.0 there is no support for JSF 1.1, but I've seen some code, that consider JSF 1.1. Is there a plan to make the test12 version also runnable with JSF 1.1? It seems to me, that we can build an artifact, that supports JSF 1.1 and 1.2 coexistent, to keep the management overhead small. Regards, Udo
Re: [Tobago] Problem using tc:tree and request parameters
Hi, Alf, after taking a close look to your problem, we have discovered a problem in the decision if there is a post back, or not. I've added an issue in JIRA: https://issues.apache.org/jira/browse/TOBAGO-905 You may test the current 1.0.x branch or use the nightly build from tomorrow. Regards, Udo Am 25.06.10 09:30, schrieb Alf Felis: Hi Udo, I noticed that the attachments has been removed from my mail. Should I send them to your email account? Regards, Alf -Ursprüngliche Nachricht- Von: Alf Felisalf.fe...@gmx.de Gesendet: 17.06.2010 13:01:43 An: MyFaces Discussionusers@myfaces.apache.org Betreff: Re: [Tobago] Problem using tc:tree and request parameters Hi Udo, sorry... I forgot the environment information: MyFaces 1.1.6 Tobago 1.0.24 and 1.0.27 The bean has session scope. managed-bean managed-bean-nametobagoTreeTestBean/managed-bean-name managed-bean-classTobagoTreeTestBean/managed-bean-class managed-bean-scopesession/managed-bean-scope /managed-bean I have attached my test bean and the jsp page to this mail. First I thought that the request always contains the state of the navigation, but I checked the request parameters (using a servlet filter) and figured out that the state information will only be sent when I click the navigation tree. Nevertheless reloading the page (browser reload) collapses the tree when using parameters and saves the state without using parameters. In both situations there are no request parameters from the navigation state. Request parameters using parameters: Parameters: param: 123 Request parameters without parameters: Parameters: Request parameters when clicking the tree: Parameters: _idJsp0::form-action: _idJsp0:nav:Number1 jsf_tree: 5 _idJsp0::action-position: 0px,0px,0px,0px _idJsp0::context-path: /Tobago jsf_viewid: /TobagoTreeTest.jsp _idJsp0::form-clientDimension: 913;700 _idJsp0:nav: ;Home;Number1; _idJsp0:nav-marker: _idJsp0:nav:Number1 tobago.dummy: _idJsp0:nav-scrollPosition: Regards, Alf -Ursprüngliche Nachricht- Von: Udo Schnurpfeil Gesendet: 17.06.2010 09:59:42 An: MyFaces Discussion Betreff: Re: [Tobago] Problem using tc:tree and request parameters Hi Alf, I've some questions: Which Tobago version and which JSF implementation and version you are using (and which container)? In which scope is the managed bean that holds the state? I don't exactly know what happens, because I've not the sources of you code. But I can try some supposition... The usual usage of Tobago is to write an application, with one or more pages that will be called by clicking on some controls on the page. It was a difference of calling the URL and clicking atc:button. The click on a button will submit the current expansion state of the tree and sends it to the server (via a hidden input field), which manipulates the tree state object. When calling the URL (manually) the expansion state information is not part of the request. When JSF now restores the UIViewRoot and begins to decode the request it clears the expand state and tries to apply the new information from the browser (which are not available in this case). It is correct, that you want to provide external links (non faces request to faces response)? Are you also use internal actions? If not, you don't need to save the expansion state for each user. You can try to put the tree state in the none scope. Regards, Udo Am 15.06.10 15:51, schrieb Alf Felis: Any idea? Original-Nachricht Datum: Thu, 03 Jun 2010 13:31:44 +0200 Von: Alf Felis[ An: MyFaces Discussion Betreff: [Tobago] Problem using tc:tree and request parameters Hi all, I have a problem with tc:tree. In my code I expand the tree after creation using the TreeState: state.expand(tree, 1); This works fine till I use a request parameter... e.g. http://localhost:8080/Tobago/faces/TobagoTreeTest.jsp?param=123 In this case the first/initial call will show an expanded tree... the second call shows a collapsed tree. - first and second call with parameter: - 1.) Call the URL - tree expanded 2.) Reload the URL - tree collapsed - first call with, second without parameter: - 1.) Call the URL - tree expanded 2.) Call http://localhost:8080/Tobago/faces/TobagoTreeTest.jsp - tree expanded 3.) any call/reload without parameter - tree expanded I figured out that the method 'TreeState.clearExpandState()' will be called, but I can't find any hints on that issue. Regards, Alf
Re: [Tobago] Problem using tc:selectOneChoice
Hi Hani, please report an issue in the Jira. (The problem looks like the known issue with ie6 and select tags in IE6) Regards, Udo Am 29.07.10 12:22, schrieb Abushammala, Hani (EXTERN: FTP): Hi all, I habe a problem by using tc:selectOneChoice in a sheet. Internet Explorer displays the drop down menu in the header of the sheet by scrolling. Rendering with firefox works fine. I don`t know, what it`s wrong? Tabago: 1.0.27 MyFaces: 1.1.7 IE: 6 Best regards, Hani
Re: [Tobago] calling of renderer class
Hallo Hani, I'm not know exactly what you need. I assume, you have a sheet with headers, and the headers should have more than one row? Do you needed wrapping of the text in one header element, or do you need to have two header elements (with border etc.?). A feature like this will be added in Tobago 1.5, but is not scheduled yet. Regards, Udo Am 25.06.10 10:38, schrieb Abushammala, Hani (EXTERN: FTP): Thanks for the Info. I`m trying now to extend the sheet renderer to visualize a label in two rows (or one label for each header row) in the header of the sheet. Is this the best way or is there another way to solve it? Regards, Hani -Ursprüngliche Nachricht- Von: Udo Schnurpfeil [mailto:u...@schnurpfeil.de] Gesendet: Freitag, 25. Juni 2010 07:46 An: users@myfaces.apache.org Betreff: Re: [Tobago] calling of renderer class Hi, there is also an example-theme in the project (https://svn.apache.org/repos/asf/myfaces/tobago/branches/tobago-1.0.x/example/tobago-theme-example/) which overrides the InRenderer. Regards Udo Am 23.06.10 09:45, schrieb Volker Weber: Hi Hani, the easiest way to overwrite a Renderer is to put your own int the tobago-resource-path into your application. e.g. if you use the speyside theme put your renderer, which must be named SheetRenderer, into the package tobago-resource-path/html/standard/speyside/tag/ Regards, Volker 2010/6/21 Abushammala, Hani (EXTERN: FTP) extern.hani.abushamma...@volkswagen.de: Another question. How can i configure another renderer for the tobago component like the sheet component. Any ideas or solutions? Regards, Hani -Ursprüngliche Nachricht- Von: Abushammala, Hani (EXTERN: FTP) [mailto:extern.hani.abushamma...@volkswagen.de] Gesendet: Montag, 21. Juni 2010 09:52 An: MyFaces Discussion Betreff: [Tobago] calling of renderer class Hi, I`ve developed a component to create a dynamic panel with a renderer class, but the renderer could not be called. The rendering works if the compoent class renders the output stream. I don`t know how i can configure the renderer for the new component in tobago. faces-config.xml: component descriptionThe dynamic panel component./description display-nameDynamicPanel/display-name !-- The name for registering the component. -- component-typeextn.DynamicPanel/component-type !-- The implementation class. -- component-classweb.components.UIDynamicPanel/component-class component-extension renderer-typeextn.DynamicPanelRenderer/renderer-type /component-extension /component render-kit renderer descriptionRenderer for DynamicPanel./description component-familyextn.DynamicPanelFamily/component-family renderer-typeextn.DynamicPanelRenderer/renderer-type renderer-classweb.components.DynamicPanelRenderer/renderer-class /renderer /render-kit Regards, Hani
Re: [Tobago] Problem using tc:tree and request parameters
Hi Alf, I think the request parameters are working like expected. Only in the case of reload it will depend, if you make a reload of the get or the reload of a later post request. A reload of a post will normally reposted after the browser has asked the user (may depends on browser and configuration). For solving the problem, I want to understand why you use the get request with the non-jsf parameter (see the last section from my last mail). Regards, Udo Am 17.06.10 13:01, schrieb Alf Felis: Hi Udo, sorry... I forgot the environment information: MyFaces 1.1.6 Tobago 1.0.24 and 1.0.27 The bean has session scope. managed-bean managed-bean-nametobagoTreeTestBean/managed-bean-name managed-bean-classTobagoTreeTestBean/managed-bean-class managed-bean-scopesession/managed-bean-scope /managed-bean I have attached my test bean and the jsp page to this mail. First I thought that the request always contains the state of the navigation, but I checked the request parameters (using a servlet filter) and figured out that the state information will only be sent when I click the navigation tree. Nevertheless reloading the page (browser reload) collapses the tree when using parameters and saves the state without using parameters. In both situations there are no request parameters from the navigation state. Request parameters using parameters: Parameters: param: 123 Request parameters without parameters: Parameters: Request parameters when clicking the tree: Parameters: _idJsp0::form-action: _idJsp0:nav:Number1 jsf_tree: 5 _idJsp0::action-position: 0px,0px,0px,0px _idJsp0::context-path: /Tobago jsf_viewid: /TobagoTreeTest.jsp _idJsp0::form-clientDimension: 913;700 _idJsp0:nav: ;Home;Number1; _idJsp0:nav-marker: _idJsp0:nav:Number1 tobago.dummy: _idJsp0:nav-scrollPosition: Regards, Alf -Ursprüngliche Nachricht- Von: Udo Schnurpfeilu...@schnurpfeil.de Gesendet: 17.06.2010 09:59:42 An: MyFaces Discussionusers@myfaces.apache.org Betreff: Re: [Tobago] Problem using tc:tree and request parameters Hi Alf, I've some questions: Which Tobago version and which JSF implementation and version you are using (and which container)? In which scope is the managed bean that holds the state? I don't exactly know what happens, because I've not the sources of you code. But I can try some supposition... The usual usage of Tobago is to write an application, with one or more pages that will be called by clicking on some controls on the page. It was a difference of calling the URL and clicking atc:button. The click on a button will submit the current expansion state of the tree and sends it to the server (via a hidden input field), which manipulates the tree state object. When calling the URL (manually) the expansion state information is not part of the request. When JSF now restores the UIViewRoot and begins to decode the request it clears the expand state and tries to apply the new information from the browser (which are not available in this case). It is correct, that you want to provide external links (non faces request to faces response)? Are you also use internal actions? If not, you don't need to save the expansion state for each user. You can try to put the tree state in the none scope. Regards, Udo Am 15.06.10 15:51, schrieb Alf Felis: Any idea? Original-Nachricht Datum: Thu, 03 Jun 2010 13:31:44 +0200 Von: Alf Felis[ An: MyFaces Discussion Betreff: [Tobago] Problem using tc:tree and request parameters Hi all, I have a problem with tc:tree. In my code I expand the tree after creation using the TreeState: state.expand(tree, 1); This works fine till I use a request parameter... e.g. http://localhost:8080/Tobago/faces/TobagoTreeTest.jsp?param=123 In this case the first/initial call will show an expanded tree... the second call shows a collapsed tree. - first and second call with parameter: - 1.) Call the URL - tree expanded 2.) Reload the URL - tree collapsed - first call with, second without parameter: - 1.) Call the URL - tree expanded 2.) Call http://localhost:8080/Tobago/faces/TobagoTreeTest.jsp - tree expanded 3.) any call/reload without parameter - tree expanded I figured out that the method 'TreeState.clearExpandState()' will be called, but I can't find any hints on that issue. Regards, Alf
Re: [Tobago] calling of renderer class
Hi, there is also an example-theme in the project (https://svn.apache.org/repos/asf/myfaces/tobago/branches/tobago-1.0.x/example/tobago-theme-example/) which overrides the InRenderer. Regards Udo Am 23.06.10 09:45, schrieb Volker Weber: Hi Hani, the easiest way to overwrite a Renderer is to put your own int the tobago-resource-path into your application. e.g. if you use the speyside theme put your renderer, which must be named SheetRenderer, into the package tobago-resource-path/html/standard/speyside/tag/ Regards, Volker 2010/6/21 Abushammala, Hani (EXTERN: FTP) extern.hani.abushamma...@volkswagen.de: Another question. How can i configure another renderer for the tobago component like the sheet component. Any ideas or solutions? Regards, Hani -Ursprüngliche Nachricht- Von: Abushammala, Hani (EXTERN: FTP) [mailto:extern.hani.abushamma...@volkswagen.de] Gesendet: Montag, 21. Juni 2010 09:52 An: MyFaces Discussion Betreff: [Tobago] calling of renderer class Hi, I`ve developed a component to create a dynamic panel with a renderer class, but the renderer could not be called. The rendering works if the compoent class renders the output stream. I don`t know how i can configure the renderer for the new component in tobago. faces-config.xml: component descriptionThe dynamic panel component./description display-nameDynamicPanel/display-name !-- The name for registering the component. -- component-typeextn.DynamicPanel/component-type !-- The implementation class. -- component-classweb.components.UIDynamicPanel/component-class component-extension renderer-typeextn.DynamicPanelRenderer/renderer-type /component-extension /component render-kit renderer descriptionRenderer for DynamicPanel./description component-familyextn.DynamicPanelFamily/component-family renderer-typeextn.DynamicPanelRenderer/renderer-type renderer-classweb.components.DynamicPanelRenderer/renderer-class /renderer /render-kit Regards, Hani
Re: [Tobago] Problem using tc:tree and request parameters
Hi Alf, I've some questions: Which Tobago version and which JSF implementation and version you are using (and which container)? In which scope is the managed bean that holds the state? I don't exactly know what happens, because I've not the sources of you code. But I can try some supposition... The usual usage of Tobago is to write an application, with one or more pages that will be called by clicking on some controls on the page. It was a difference of calling the URL and clicking a tc:button. The click on a button will submit the current expansion state of the tree and sends it to the server (via a hidden input field), which manipulates the tree state object. When calling the URL (manually) the expansion state information is not part of the request. When JSF now restores the UIViewRoot and begins to decode the request it clears the expand state and tries to apply the new information from the browser (which are not available in this case). It is correct, that you want to provide external links (non faces request to faces response)? Are you also use internal actions? If not, you don't need to save the expansion state for each user. You can try to put the tree state in the none scope. Regards, Udo Am 15.06.10 15:51, schrieb Alf Felis: Any idea? Original-Nachricht Datum: Thu, 03 Jun 2010 13:31:44 +0200 Von: Alf Felisalf.fe...@gmx.de An: MyFaces Discussionusers@myfaces.apache.org Betreff: [Tobago] Problem using tc:tree and request parameters Hi all, I have a problem with tc:tree. In my code I expand the tree after creation using the TreeState: state.expand(tree, 1); This works fine till I use a request parameter... e.g. http://localhost:8080/Tobago/faces/TobagoTreeTest.jsp?param=123 In this case the first/initial call will show an expanded tree... the second call shows a collapsed tree. - first and second call with parameter: - 1.) Call the URL - tree expanded 2.) Reload the URL - tree collapsed - first call with, second without parameter: - 1.) Call the URL - tree expanded 2.) Call http://localhost:8080/Tobago/faces/TobagoTreeTest.jsp - tree expanded 3.) any call/reload without parameter - tree expanded I figured out that the method 'TreeState.clearExpandState()' will be called, but I can't find any hints on that issue. Regards, Alf
Re: [Tobago] foreach in c:sheet
Hi Hani,
didn't you sent the image or removes the list the attachment? If so, you
can also send me the image directly...
Regards,
Udo
Am 31.05.10 09:22, schrieb Abushammala, Hani (EXTERN: FTP):
Sorry, i forget to attach the image.
Regards,
Hani
-Ursprüngliche Nachricht-
Von: Abushammala, Hani (EXTERN: FTP)
[mailto:extern.hani.abushamma...@volkswagen.de]
Gesendet: Freitag, 28. Mai 2010 12:00
An: MyFaces Discussion
Betreff: AW: [Tobago] foreach in c:sheet
Hi Udo,
To explain the problematic i will use the same image in topic [Tobago] dynamic
panels in tc:sheet.
I want to create panel within a column to visualize a list of dynamic items as
icons for each row of the sheet and the elements of the sheet has a list of the
elements to visualize. Also the panel in each row is completely independent, so
that
the number of elements to visualize is not limted and the links of elements has
differnent attributes.
Thank you for the help.
Regards,
Hani
-Ursprüngliche Nachricht-
Von: Udo Schnurpfeil [mailto:u...@schnurpfeil.de]
Gesendet: Freitag, 28. Mai 2010 09:30
An: users@myfaces.apache.org
Betreff: Re: [Tobago] foreach in c:sheet
Hi Hani,
to find the optimal solution for your problem it whould be helpful to
have a screenshot of your app.
The question is: is the number of links in one column limited? Are the
links mostly the same, or are they completely independent?
When we have limited links, we can use static links with rendered
attributes and we don't have to create lots of components in each row.
Regards,
Udo
Am 27.05.10 12:04, schrieb Abushammala, Hani (EXTERN: FTP):
Hi Volker,
By component binding i used actually your tip for using rendered attribut
(thank you!)
After creating the main panel and his children panels for each row of the
sheet, i've
defined the rendered attribut of the children panels with:
ComponentUtil.setBooleanProperty(childPanel /* the i child panel */,
TobagoConstants.ATTR_RENDERED, #{ + sheetVar
+ .index ==
+ item.getIndex() /* for i child panel */
+ });
So that the first panel will be in rendered in the first row and the rest of
panels will be disabled and etc.
It works fine, but i need a better solution. The jstl way works also, but all
panels will be displayed in each row of sheet.
I didn't think about a new implementation of the UIPanel, i will try this one
now.
Thank you
Regards,
Hani
-Ursprüngliche Nachricht-
Von: weber.vol...@googlemail.com [mailto:weber.vol...@googlemail.com] Im
Auftrag von Volker Weber
Gesendet: Donnerstag, 27. Mai 2010 09:45
An: MyFaces Discussion
Betreff: Re: [Tobago] foreach in c:sheet
Hi,
as Udo wrote, you can't use jstl inside tc:sheet!
Or to be more precise: the var param of tc:sheet is not available when
jstl iterates, because jstl evaluates before tobago starts renderring.
I also can't imagine how you do this with component binding, because
this is also done before rendering starts. Can you explain how you do
this?
But there is a way to solve this, you need binding to a extended
UIPanel implementation which drops and recreates children depending on
sheets var in each process* method.
Regards,
Volker
2010/5/27 Abushammala, Hani (EXTERN: FTP)
extern.hani.abushamma...@volkswagen.de:
Hello Udo,
Sorry, i forget to list the important libraries in use:
avalon-framework-4.1.3.jar
tobago-core-1.0.24.jar
jstl-1.1.0.jar
myfaces-impl-1.1.7.jar
myfaces-api-1.1.7.jar
commons-el-1.0.jar
standard-1.1.2.jar
Thank you.
-Ursprüngliche Nachricht-
Von: Abushammala, Hani (EXTERN: FTP)
[mailto:extern.hani.abushamma...@volkswagen.de]
Gesendet: Mittwoch, 26. Mai 2010 15:12
An: MyFaces Discussion
Betreff: AW: [Tobago] foreach in c:sheet
Hello Udo,
I want to add a dynamic panel to a column, which has many elements for each row
in the sheet,
that means the content of the panel for each row is different (like sheet in
sheet).
I could do it with programming of whole panel in java and binding it in the
jsp, but i am looking now for a different way.
I've tried to use jstl, but it doesn`t work to render the right dynamic panel
for right row:
tc:column sortable=false align=left
tc:panel id=headPanel
c:forEach items=${myBean.list} var=x varStatus=status1
tc:panel id=subPanel${x.nr} rendered=${status1.index} ==
${x.nr}
c:forEach items=${x.subList} var=w varStatus=status2
tc:link image=${w.iconUrl} id=link_${x.nr}_${w.nr} /
/c:forEach
/tc:panel
/c:forEach
/tc:panel
/tc:column
I've used jstl 1.1.
Thank you.
-Ursprüngliche Nachricht-
Von: Udo Schnurpfeil [mailto:u...@schnurpfeil.de
Re: [Tobago] foreach in c:sheet
Hi Hani,
I got your image, finally.
When the boxes are a kind of rating, you may use only one image and vary
the value from rating0.gif to rating5.gif
like here http://www.macdesktops.net/core/images/rating2.gif
Another solution may be using tc:progress instead of tc:image.
(Unfortunately there is a little style problem with tc:progress inside
of tc:sheet (line break between the elements, when the column is too
small), but I will fix it in the next version)
Hope that helps
Udo
Am 01.06.10 09:49, schrieb Udo Schnurpfeil:
Hi Hani,
didn't you sent the image or removes the list the attachment? If so,
you can also send me the image directly...
Regards,
Udo
Am 31.05.10 09:22, schrieb Abushammala, Hani (EXTERN: FTP):
Sorry, i forget to attach the image.
Regards,
Hani
-Ursprüngliche Nachricht-
Von: Abushammala, Hani (EXTERN: FTP)
[mailto:extern.hani.abushamma...@volkswagen.de]
Gesendet: Freitag, 28. Mai 2010 12:00
An: MyFaces Discussion
Betreff: AW: [Tobago] foreach in c:sheet
Hi Udo,
To explain the problematic i will use the same image in topic
[Tobago] dynamic panels in tc:sheet.
I want to create panel within a column to visualize a list of dynamic
items as icons for each row of the sheet and the elements of the
sheet has a list of the elements to visualize. Also the panel in each
row is completely independent, so that
the number of elements to visualize is not limted and the links of
elements has differnent attributes.
Thank you for the help.
Regards,
Hani
-Ursprüngliche Nachricht-
Von: Udo Schnurpfeil [mailto:u...@schnurpfeil.de]
Gesendet: Freitag, 28. Mai 2010 09:30
An: users@myfaces.apache.org
Betreff: Re: [Tobago] foreach in c:sheet
Hi Hani,
to find the optimal solution for your problem it whould be helpful to
have a screenshot of your app.
The question is: is the number of links in one column limited? Are the
links mostly the same, or are they completely independent?
When we have limited links, we can use static links with rendered
attributes and we don't have to create lots of components in each row.
Regards,
Udo
Am 27.05.10 12:04, schrieb Abushammala, Hani (EXTERN: FTP):
Hi Volker,
By component binding i used actually your tip for using rendered
attribut (thank you!)
After creating the main panel and his children panels for each row
of the sheet, i've
defined the rendered attribut of the children panels with:
ComponentUtil.setBooleanProperty(childPanel /* the i child panel */,
TobagoConstants.ATTR_RENDERED, #{ + sheetVar
+ .index ==
+ item.getIndex() /* for i child panel */
+ });
So that the first panel will be in rendered in the first row and the
rest of panels will be disabled and etc.
It works fine, but i need a better solution. The jstl way works
also, but all panels will be displayed in each row of sheet.
I didn't think about a new implementation of the UIPanel, i will try
this one now.
Thank you
Regards,
Hani
-Ursprüngliche Nachricht-
Von: weber.vol...@googlemail.com
[mailto:weber.vol...@googlemail.com] Im Auftrag von Volker Weber
Gesendet: Donnerstag, 27. Mai 2010 09:45
An: MyFaces Discussion
Betreff: Re: [Tobago] foreach in c:sheet
Hi,
as Udo wrote, you can't use jstl inside tc:sheet!
Or to be more precise: the var param of tc:sheet is not available when
jstl iterates, because jstl evaluates before tobago starts renderring.
I also can't imagine how you do this with component binding, because
this is also done before rendering starts. Can you explain how you do
this?
But there is a way to solve this, you need binding to a extended
UIPanel implementation which drops and recreates children depending on
sheets var in each process* method.
Regards,
Volker
2010/5/27 Abushammala, Hani (EXTERN: FTP)
extern.hani.abushamma...@volkswagen.de:
Hello Udo,
Sorry, i forget to list the important libraries in use:
avalon-framework-4.1.3.jar
tobago-core-1.0.24.jar
jstl-1.1.0.jar
myfaces-impl-1.1.7.jar
myfaces-api-1.1.7.jar
commons-el-1.0.jar
standard-1.1.2.jar
Thank you.
-Ursprüngliche Nachricht-
Von: Abushammala, Hani (EXTERN: FTP)
[mailto:extern.hani.abushamma...@volkswagen.de]
Gesendet: Mittwoch, 26. Mai 2010 15:12
An: MyFaces Discussion
Betreff: AW: [Tobago] foreach in c:sheet
Hello Udo,
I want to add a dynamic panel to a column, which has many elements
for each row in the sheet,
that means the content of the panel for each row is different (like
sheet in sheet).
I could do it with programming of whole panel in java and binding
it in the jsp, but i am looking now for a different way.
I've tried to use jstl, but it doesn`t work to render the right
dynamic panel for right row:
tc:column sortable=false align
Re: [Tobago] foreach in c:sheet
Hi Hani,
to find the optimal solution for your problem it whould be helpful to
have a screenshot of your app.
The question is: is the number of links in one column limited? Are the
links mostly the same, or are they completely independent?
When we have limited links, we can use static links with rendered
attributes and we don't have to create lots of components in each row.
Regards,
Udo
Am 27.05.10 12:04, schrieb Abushammala, Hani (EXTERN: FTP):
Hi Volker,
By component binding i used actually your tip for using rendered attribut
(thank you!)
After creating the main panel and his children panels for each row of the
sheet, i've
defined the rendered attribut of the children panels with:
ComponentUtil.setBooleanProperty(childPanel /* the i child panel */,
TobagoConstants.ATTR_RENDERED, #{ + sheetVar
+ .index ==
+ item.getIndex() /* for i child panel */
+ });
So that the first panel will be in rendered in the first row and the rest of
panels will be disabled and etc.
It works fine, but i need a better solution. The jstl way works also, but all
panels will be displayed in each row of sheet.
I didn't think about a new implementation of the UIPanel, i will try this one
now.
Thank you
Regards,
Hani
-Ursprüngliche Nachricht-
Von: weber.vol...@googlemail.com [mailto:weber.vol...@googlemail.com] Im
Auftrag von Volker Weber
Gesendet: Donnerstag, 27. Mai 2010 09:45
An: MyFaces Discussion
Betreff: Re: [Tobago] foreach in c:sheet
Hi,
as Udo wrote, you can't use jstl inside tc:sheet!
Or to be more precise: the var param of tc:sheet is not available when
jstl iterates, because jstl evaluates before tobago starts renderring.
I also can't imagine how you do this with component binding, because
this is also done before rendering starts. Can you explain how you do
this?
But there is a way to solve this, you need binding to a extended
UIPanel implementation which drops and recreates children depending on
sheets var in each process* method.
Regards,
Volker
2010/5/27 Abushammala, Hani (EXTERN: FTP)
extern.hani.abushamma...@volkswagen.de:
Hello Udo,
Sorry, i forget to list the important libraries in use:
avalon-framework-4.1.3.jar
tobago-core-1.0.24.jar
jstl-1.1.0.jar
myfaces-impl-1.1.7.jar
myfaces-api-1.1.7.jar
commons-el-1.0.jar
standard-1.1.2.jar
Thank you.
-Ursprüngliche Nachricht-
Von: Abushammala, Hani (EXTERN: FTP)
[mailto:extern.hani.abushamma...@volkswagen.de]
Gesendet: Mittwoch, 26. Mai 2010 15:12
An: MyFaces Discussion
Betreff: AW: [Tobago] foreach in c:sheet
Hello Udo,
I want to add a dynamic panel to a column, which has many elements for each row
in the sheet,
that means the content of the panel for each row is different (like sheet in
sheet).
I could do it with programming of whole panel in java and binding it in the
jsp, but i am looking now for a different way.
I've tried to use jstl, but it doesn`t work to render the right dynamic panel
for right row:
tc:column sortable=false align=left
tc:panel id=headPanel
c:forEach items=${myBean.list} var=x varStatus=status1
tc:panel id=subPanel${x.nr} rendered=${status1.index} ==
${x.nr}
c:forEach items=${x.subList} var=w varStatus=status2
tc:link image=${w.iconUrl} id=link_${x.nr}_${w.nr} /
/c:forEach
/tc:panel
/c:forEach
/tc:panel
/tc:column
I've used jstl 1.1.
Thank you.
-Ursprüngliche Nachricht-
Von: Udo Schnurpfeil [mailto:u...@schnurpfeil.de]
Gesendet: Dienstag, 25. Mai 2010 09:16
An: users@myfaces.apache.org
Betreff: Re: [Tobago] foreach in c:sheet
Hello Hani,
I've never tried to usec:set, so I have no experience with that tag.
Your code will not work, because the content inside of thetc:sheet
will be visited only one time.
The JSTL Tag needs to be called in each row to make it work.
Mixing JSTL and JSF and use of iterators have some drawbacks. This
depends also on the version of the libraries. Which version you are using?
You may try to make your data accessible via the var-attribute of the sheet:
tc:sheet var=row ...
...
tc:column
tc:out value=#{row.subListAsString} /
/tc:column
...
/tc:sheet
Regards,
Udo
Am 20.05.10 16:39, schrieb Abushammala, Hani (EXTERN: FTP):
Hello,
We want to visualize some dynamic content within a column for each row
of sheet with jstl.
We tried to incrment a variable (defined outside of the tc:sheet
element) with:c:set var=counter value=${counter + 1} /to get
the row index, but it doesn't work.
Jsp:
tc:sheet ..
...
tc:column
c:set var=counter value=${counter + 1} /
c:forEach items
Re: [Tobago] foreach in c:sheet
Hello Hani,
I've never tried to use c:set, so I have no experience with that tag.
Your code will not work, because the content inside of the tc:sheet
will be visited only one time.
The JSTL Tag needs to be called in each row to make it work.
Mixing JSTL and JSF and use of iterators have some drawbacks. This
depends also on the version of the libraries. Which version you are using?
You may try to make your data accessible via the var-attribute of the sheet:
tc:sheet var=row ...
...
tc:column
tc:out value=#{row.subListAsString} /
/tc:column
...
/tc:sheet
Regards,
Udo
Am 20.05.10 16:39, schrieb Abushammala, Hani (EXTERN: FTP):
Hello,
We want to visualize some dynamic content within a column for each row
of sheet with jstl.
We tried to incrment a variable (defined outside of the tc:sheet
element) with:c:set var=counter value=${counter + 1} / to get
the row index, but it doesn't work.
Jsp:
tc:sheet ..
...
tc:column
c:set var=counter value=${counter + 1} /
c:forEach items=${bean.itmesList[counter].subList}
var=w varStatus=status
tc:out value=${w} /
/c:forEach
/tc:column
...
/tc:sheet
Is it possible and how?
Thank you.
Re: [TOBAGO] problem selecting current item in tx:selectOneChoice
I've fixed it in the current trunk and the current 1.0.x branch, so it will be available in version 1.0.26. (See my mail form 23. April, 23:19 CEST) Regards Udo I'm not really understanding why the mapping does not works with tc:selectItem but for know I have a working solution.
Re: [TOBAGO] How to add new css to Tobago
Hi,
there is no style class tobago-box-footer defined for any HTML tag. So
the style will not be applied.
When you want to give some panels a different style, you can assign a
markup like:
tc:panel markup=important ...
this will result in HTML with the class tobago-panel-markup-important.
Than you can define a style for that class.
First, you have to register a markup for a renderer. See:
http://myfaces.apache.org/tobago/faq.html#tobagocustommarkup
If you want to see which styles from which files will be applied, you
may use Firebug, or any other browser development tool, which are very
helpful.
Regards,
Udo
Am 26.04.10 20:06, schrieb tobagouser:
Hi Udo,Helmut
Thanks for the info.Its really useful.
My requirements are
1.I want to have a different background color and shade to some of the
panels in the pages.This color and shade should be different from the
default panel css ,so it should have a different css .
2.As mentioned earlier I want to add a new css to the border footer.I added
it similar to the box header css in the speyside style.css file ..like
.tobago-box-footer {
values here...
}
But this footer css never applied on the pages.
please let me know whether tc:style tag applies at the page level only or
applies at the child tags like panel and box.
also please let me know how to add a new css to box footer and why the
above css does not worked.
Thanks,
KSK
Udo Schnurpfeil wrote:
Hi,
The simple way: You can also put a file style/style.css (exactly this
name) in the webapp directory. The ResourceManager will find it and add
it to the list of needed resources. The style will be effect all Tobago
pages in one application.
Helmut solution is also possible. The advantage is, you can decide,
which pages need the style. It is also possible to make changes in more
than one theme, if needed.
If you want to make bigger changes to the design of the pages (specially
for more than one application), you may want to write a Tobago theme,
that contains your custom look and feel.
Regards,
Udo
Am 22.04.10 15:55, schrieb Helmut Swaczinna:
Hi,
wich style.css do you mean exactly? Where is it located? You can add
your own styles with the tc:style tag, e.g.tc:style
style=style/mystyles.css /, under your resource path.
Regards
Helmut
Am 22.04.2010 15:51, schrieb tobagouser:
Any inputs on this please..
tobagouser wrote:
Hi All,
I have tried to add tobago-box-footer to the style.css ,but it never
affected the pages.Please could you let me know how to add a new css to
tobago.
Thanks,
KSK
Re: [TOBAGO] problem selecting current item in tx:selectOneChoice
Hi Michael,
there are more than one solution for that, but as far as I know there is
not cast operator...
1. use a managed bean
faces-config.xml:
managed-bean
managed-bean-nameintValues/managed-bean-name
managed-bean-classjava.util.ArrayList/managed-bean-class
managed-bean-scopeapplication/managed-bean-scope !-- or use none --
list-entries
value-classjava.lang.Integer/value-class
value0/value
value1/value
value2/value
/list-entries
/managed-bean
JSP/Facelet:
tc:selectItem itemValue=#{intValues[1]} itemLabel=suspended/
(simple, scales not good, works with JSF 1.1, 1.2 and JSP and Facelets)
2. write a EL-function
AFAIK: works with facelets and/or JSF 1.2 but may not work with JSP and
JSF 1.1.
What do you are using?
3. write a converter that implements the list, or map interface and use
it as managed bean
(a little bit complicated, scales good, works with JSF 1.1, 1.2 and JSP
and Facelets)
4. write an additional getter/setter activeLong.
(needs Java)
5. use tc:selectItems (instead of tc:selectItem) and you may also
want to use enums.
(may be the best solution but more work, needs Java 1.5, scales good,
refactoring is easy: there is only one position in the code to define
the values, type save: use the enum in your Controller, so you know the
meaning of the value from the enum)
For a simple application or demo I would prefer #1 or #4, for an
enterprise application I would prefer #5...
Regards,
Udo
Am 22.04.10 22:33, schrieb Michael Kakuschky:
Hello Udo, hello Volker,
both together (using braces for EL expression and long data type for
getter and setter) helped to get the tx:selectOneChoice working like
expected :-)
Since I use many int getters and setters where I want to use the
tx:selectOneChoice component it would be nice if there is some way to
convert the int to long in EL. It would help to save a lot of work..
Thanks best regards Michael
Udo Schnurpfeil schrieb:
Hi,
there is still a little problem with that. #{0} is a Long value, so
the getter/setter needs be a also a Long and not an Integer.
I don't know, if in EL there is something like a cast operator...
Regards,
Udo
Am 22.04.10 18:20, schrieb Volker Weber:
Hi Michael,
(btw yes i work together with Dirk Fangohr. sorry for the delay, was a
bit busy last Friday)
the problem is you has int as value in getActive() but String in
select items.
Try
tc:selectItem itemValue=#{2} itemLabel=active/
tc:selectItem itemValue=#{1} itemLabel=suspended/
tc:selectItem itemValue=#{0} itemLabel=inactice/
you don't need a converter!
Regards,
Volker
2010/4/21 Michael Kakuschkykakusc...@elbe-net.de:
Hello,
I have a strange problem selecting the correct item of
tx:selectOneChoice
boxes if the itemValue of the tc:selectItem item is an Integer.
Storing the selected values works fine as aspected. I will find the
correct
values in mybackend database
What does not work is that after rerendering the correct value is
selected.
If in my example the MyController.active Integer attribute has a
value of 1
suspended should be selected. But it's always the first value of the
tc:selectItem elements selected.
I tried already to use a converter because I guessed that there
is an
conversion problem between Integer and String but it does not help.
If the selectItem bind to a String it works fine (sure without the
integerConverter). With the tomahawk h:selectOneMenu component it
works also
with Integers.
Knows anybody how to solve this problem for tobago to use an
Integer as
value attribute?
tc:cell
tx:selectOneChoice value=#{myController.active} label=active
converter=integerConverter
tc:selectItem itemValue=2 itemLabel=active/
tc:selectItem itemValue=1 itemLabel=suspended/
tc:selectItem itemValue=0 itemLabel=inactice/
/tx:selectOneChoice
/tc:cell
public class MyController{
private Integer active = 1;
public Integer getActive() {
return active;
}
public void setActive(Integer active) {
this.active = active;
}
}
public class IntegerConverter implements Converter {
public Object getAsObject(FacesContext context, UIComponent
component,
String value) throws ConverterException {
return Integer.getInteger(value);
}
public String getAsString(FacesContext context, UIComponent component,
Object value) throws ConverterException {
if (value instanceof Integer) {
return ((Integer) value).toString();
}
return ;
}
}
Thanks and best regards
Michael
Re: [TOBAGO] problem selecting current item in tx:selectOneChoice
Hi Michael,
I've thought about that problem and implemented a solution that works
for the most cases.
See: https://issues.apache.org/jira/browse/TOBAGO-877
With the current sources your example should work now, without any of
the modifications I told you.
Which version of JSF you are using? The f:selectItem works not with JSF
1.1, but the tc:selectItem works with 1.1 and 1.2.
Regards,
Udo
Am 23.04.10 09:59, schrieb Udo Schnurpfeil:
Hi Michael,
there are more than one solution for that, but as far as I know there
is not cast operator...
1. use a managed bean
faces-config.xml:
managed-bean
managed-bean-nameintValues/managed-bean-name
managed-bean-classjava.util.ArrayList/managed-bean-class
managed-bean-scopeapplication/managed-bean-scope !-- or use
none --
list-entries
value-classjava.lang.Integer/value-class
value0/value
value1/value
value2/value
/list-entries
/managed-bean
JSP/Facelet:
tc:selectItem itemValue=#{intValues[1]} itemLabel=suspended/
(simple, scales not good, works with JSF 1.1, 1.2 and JSP and Facelets)
2. write a EL-function
AFAIK: works with facelets and/or JSF 1.2 but may not work with JSP
and JSF 1.1.
What do you are using?
3. write a converter that implements the list, or map interface and
use it as managed bean
(a little bit complicated, scales good, works with JSF 1.1, 1.2 and
JSP and Facelets)
4. write an additional getter/setter activeLong.
(needs Java)
5. use tc:selectItems (instead of tc:selectItem) and you may also
want to use enums.
(may be the best solution but more work, needs Java 1.5, scales good,
refactoring is easy: there is only one position in the code to define
the values, type save: use the enum in your Controller, so you know
the meaning of the value from the enum)
For a simple application or demo I would prefer #1 or #4, for an
enterprise application I would prefer #5...
Regards,
Udo
Am 22.04.10 22:33, schrieb Michael Kakuschky:
Hello Udo, hello Volker,
both together (using braces for EL expression and long data type for
getter and setter) helped to get the tx:selectOneChoice working like
expected :-)
Since I use many int getters and setters where I want to use the
tx:selectOneChoice component it would be nice if there is some way to
convert the int to long in EL. It would help to save a lot of work..
Thanks best regards Michael
Udo Schnurpfeil schrieb:
Hi,
there is still a little problem with that. #{0} is a Long value, so
the getter/setter needs be a also a Long and not an Integer.
I don't know, if in EL there is something like a cast operator...
Regards,
Udo
Am 22.04.10 18:20, schrieb Volker Weber:
Hi Michael,
(btw yes i work together with Dirk Fangohr. sorry for the delay, was a
bit busy last Friday)
the problem is you has int as value in getActive() but String in
select items.
Try
tc:selectItem itemValue=#{2} itemLabel=active/
tc:selectItem itemValue=#{1} itemLabel=suspended/
tc:selectItem itemValue=#{0} itemLabel=inactice/
you don't need a converter!
Regards,
Volker
2010/4/21 Michael Kakuschkykakusc...@elbe-net.de:
Hello,
I have a strange problem selecting the correct item of
tx:selectOneChoice
boxes if the itemValue of the tc:selectItem item is an Integer.
Storing the selected values works fine as aspected. I will find
the correct
values in mybackend database
What does not work is that after rerendering the correct value is
selected.
If in my example the MyController.active Integer attribute has a
value of 1
suspended should be selected. But it's always the first value of
the
tc:selectItem elements selected.
I tried already to use a converter because I guessed that there
is an
conversion problem between Integer and String but it does not help.
If the selectItem bind to a String it works fine (sure without the
integerConverter). With the tomahawk h:selectOneMenu component it
works also
with Integers.
Knows anybody how to solve this problem for tobago to use an
Integer as
value attribute?
tc:cell
tx:selectOneChoice value=#{myController.active} label=active
converter=integerConverter
tc:selectItem itemValue=2 itemLabel=active/
tc:selectItem itemValue=1 itemLabel=suspended/
tc:selectItem itemValue=0 itemLabel=inactice/
/tx:selectOneChoice
/tc:cell
public class MyController{
private Integer active = 1;
public Integer getActive() {
return active;
}
public void setActive(Integer active) {
this.active = active;
}
}
public class IntegerConverter implements Converter {
public Object getAsObject(FacesContext context, UIComponent
component,
String value) throws ConverterException {
return Integer.getInteger(value);
}
public String getAsString(FacesContext context, UIComponent
component,
Object value) throws ConverterException {
if (value instanceof Integer) {
return ((Integer) value).toString();
}
return ;
}
}
Thanks and best regards
Michael
Re: [TOBAGO] problem selecting current item in tx:selectOneChoice
Hi,
there is still a little problem with that. #{0} is a Long value, so the
getter/setter needs be a also a Long and not an Integer.
I don't know, if in EL there is something like a cast operator...
Regards,
Udo
Am 22.04.10 18:20, schrieb Volker Weber:
Hi Michael,
(btw yes i work together with Dirk Fangohr. sorry for the delay, was a
bit busy last Friday)
the problem is you has int as value in getActive() but String in select items.
Try
tc:selectItem itemValue=#{2} itemLabel=active/
tc:selectItem itemValue=#{1} itemLabel=suspended/
tc:selectItem itemValue=#{0} itemLabel=inactice/
you don't need a converter!
Regards,
Volker
2010/4/21 Michael Kakuschkykakusc...@elbe-net.de:
Hello,
I have a strange problem selecting the correct item of tx:selectOneChoice
boxes if the itemValue of the tc:selectItem item is an Integer.
Storing the selected values works fine as aspected. I will find the correct
values in mybackend database
What does not work is that after rerendering the correct value is selected.
If in my example the MyController.active Integer attribute has a value of 1
suspended should be selected. But it's always the first value of the
tc:selectItem elements selected.
I tried already to use a converter because I guessed that there is an
conversion problem between Integer and String but it does not help.
If the selectItem bind to a String it works fine (sure without the
integerConverter). With the tomahawk h:selectOneMenu component it works also
with Integers.
Knows anybody how to solve this problem for tobago to use an Integer as
value attribute?
tc:cell
tx:selectOneChoice value=#{myController.active} label=active
converter=integerConverter
tc:selectItem itemValue=2 itemLabel=active/
tc:selectItem itemValue=1 itemLabel=suspended/
tc:selectItem itemValue=0 itemLabel=inactice/
/tx:selectOneChoice
/tc:cell
public class MyController{
private Integer active = 1;
public Integer getActive() {
return active;
}
public void setActive(Integer active) {
this.active = active;
}
}
public class IntegerConverter implements Converter {
public Object getAsObject(FacesContext context, UIComponent component,
String value) throws ConverterException {
return Integer.getInteger(value);
}
public String getAsString(FacesContext context, UIComponent component,
Object value) throws ConverterException {
if (value instanceof Integer) {
return ((Integer) value).toString();
}
return ;
}
}
Thanks and best regards
Michael
Re: [TOBAGO] How to add new css to Tobago
Hi, The simple way: You can also put a file style/style.css (exactly this name) in the webapp directory. The ResourceManager will find it and add it to the list of needed resources. The style will be effect all Tobago pages in one application. Helmut solution is also possible. The advantage is, you can decide, which pages need the style. It is also possible to make changes in more than one theme, if needed. If you want to make bigger changes to the design of the pages (specially for more than one application), you may want to write a Tobago theme, that contains your custom look and feel. Regards, Udo Am 22.04.10 15:55, schrieb Helmut Swaczinna: Hi, wich style.css do you mean exactly? Where is it located? You can add your own styles with the tc:style tag, e.g. tc:style style=style/mystyles.css /, under your resource path. Regards Helmut Am 22.04.2010 15:51, schrieb tobagouser: Any inputs on this please.. tobagouser wrote: Hi All, I have tried to add tobago-box-footer to the style.css ,but it never affected the pages.Please could you let me know how to add a new css to tobago. Thanks, KSK
Re: grid layouts in Tobago
Hi tobagouser, you can put 2 tc:panel in the box like this: tc:box f:facet name=layout tc:gridLayout columns=*;*/ /f:facet tc:panel f:facet name=layout tc:gridLayout rows=fixed;fixed/ /f:facet tc:in/ tc:in/ tc:in/ /tc:panel tc:panel f:facet name=layout tc:gridLayout rows=fixed;fixed/ /f:facet tc:in/ tc:selectOneChoice/ tc:in/ /tc:panel /tc:box but I'm not sure I understand what you need. If I'm wrong please send a little picture of the layout you wish. Regards, Udo Am 16.04.10 11:00, schrieb tobagouser: Any suggestions on this please.. tobagouser wrote: HI All, I am using tobago to put some pages.I have a requirement, Inside a box left part is having input rows (tc:in) and remaining half right part has a separate border and css and has input rows (tc:in and select boxes). I can not have a single grid layout and have them left rows and right rows in different columns.because the input rows in the left half and right half are not in same Order.They are in zigzag manner.so I need to have a separate gridlayout for left half and separate gridlayout for right half. Could you please let me know whether it is separate gridlayouts for left and right portion of the box (screen). Please let me know how to implement it. Thanks KSK
Re: [TOBAGO] Controls self-adjusted in the page
Hi Fernando, a usual solution is to have a start/welcome/waiting page. This page may automatically forwards to your application, after checking the size of the browser (which will be done automatically). You can also use a login page for that. Is this a solution for you? If not, you may call the Tobago page with a script, and add the browser size as parameter, but this is not the preferred solution. I, don't know why you have wrong sizes on your 2nd page. Have you a simple example for that? Regards, Udo Am 23.03.10 04:52, schrieb Fernando Augusto: Hello, While working with my app using TOBAGO 1.0.25-SNAPSOT, I found the following situation: I use GridLayout with * sizes in some rows and columns. When the page is first loaded, the page organization is quite messy, with heights and widths different from the window size. When it first repaints, the controls are ALMOST (by 50px error) aligned correctly. When the screen is repainted in the 2nd time, the controls are correctly placed. How do I fix it, so the controls can be fit the first time the page is loaded??? Best Regards, Fernando Augusto
Re: [TOBAGO] Controls self-adjusted in the page
In Tobago 1.5 the layout management (was rewritten) a moved to core. Udo Am 23.03.10 04:55, schrieb Fernando Augusto: Another question regarding GridLayout class... Why is it inside scarborough theme JAR instead of a core jar, that will be distributed even if I change themes and remove scarborough Fernando Em Ter, 2010-03-23 às 00:52 -0300, Fernando Augusto escreveu: Hello, While working with my app using TOBAGO 1.0.25-SNAPSOT, I found the following situation: I use GridLayout with * sizes in some rows and columns. When the page is first loaded, the page organization is quite messy, with heights and widths different from the window size. When it first repaints, the controls are ALMOST (by 50px error) aligned correctly. When the screen is repainted in the 2nd time, the controls are correctly placed. How do I fix it, so the controls can be fit the first time the page is loaded??? Best Regards, Fernando Augusto
Re: [TOBAGO] Controls self-adjusted in the page
For Tobago 1.0 it is a good thing to put a managed bean in the session,
which manages the layout sizes like:
tc:page state=#{layout} width=#{layout.width} height=#{layout.height}
The bean has to implement PageState or extend PageStateImpl resp.
With this bean you can also influence min/max values for your application.
When the bean in in the session, the sizing also works when the user
reloads a page directly in the browser.
Regards,
Udo
Am 23.03.10 15:25, schrieb Fernando Augusto:
Hey Udo,
Thanks for your support again. I already have a login form in the app,
and what happens is:
1 - Login Form (the login page has a rows/columns problem and the form
doesn't want to be in the center, but I am trying to fix it myself).
User uses ID/PWD and validates itself;
2 - Main Form (with the alignment problem stated here). Clicking in
the buttons or menus and making the page refresh a few times makes the
appearance get better.
@Udo: I am sending you in PVT the URL, with login/pwd for you to see
the problem.
Best Regards,
Fernando Augusto
Udo Schnurpfeil escreveu:
Hi Fernando,
a usual solution is to have a start/welcome/waiting page. This page
may automatically forwards to your application, after checking the
size of the browser (which will be done automatically).
You can also use a login page for that.
Is this a solution for you? If not, you may call the Tobago page with
a script, and add the browser size as parameter, but this is not the
preferred solution.
I, don't know why you have wrong sizes on your 2nd page. Have you a
simple example for that?
Regards,
Udo
Am 23.03.10 04:52, schrieb Fernando Augusto:
Hello,
While working with my app using TOBAGO 1.0.25-SNAPSOT, I found the
following situation: I use GridLayout with * sizes in some rows and
columns. When the page is first loaded, the page organization is quite
messy, with heights and widths different from the window size. When it
first repaints, the controls are ALMOST (by 50px error) aligned
correctly. When the screen is repainted in the 2nd time, the controls
are correctly placed.
How do I fix it, so the controls can be fit the first time the page is
loaded???
Best Regards,
Fernando Augusto
Re: [TOBAGO] SelectOneChoice and Rendered attribute
You may have a type problem. Maybe the itemValue allows only Strings. When you don't set immediate=true you will see an error in that case. You can also use tc:selectItems with a class model. With that integer value should work. The value for tc:attribute is the clientId of the component: This is the chain of all naming containers. On a simple page, you have only tc:page as naming container. Put id=page then you need value=page:panel. You can check the clientId in the HTML Source Code. Am 19.03.10 19:40, schrieb Fernando Augusto: Well... Getting deeper in the problem, I've seen that the problem is in the ajax return, for it does not change the content of the box (or panel). I guess it is something related with the value passed as tc:attribute value. I've seen in a few tutorials and codes around, that addressing nested containers, you should use a long value, full of :, but I couldn't understand that part... Can someone help me with that??? Fernando Augusto escreveu: Hello, I´ve seen that the AJAX part works and the value changes, but the tx:date keeps hidden even with the right value... Any other newbie mistake in the code? Regards, Fernando Augusto Helmut Swaczinna escreveu: I think, yes, this should work too. Helmut Am 19.03.2010 15:58, schrieb ferna...@osmanager.com.br: Helmut, Can I do it with the tc:box they are inside? Regards, Fernando Augusto Hi Fernando, add a command tag to the selectOneChoice and enclose the selectOneChoice and date within a panel: tc:panel id=panel tx:selectOneChoice ... f:facet name=change tc:command tc:attribute name=renderedPartially value=panel/ /tc:command /f:facet /tx:selectOneChoice tx:date ... /tc:panel Now the panel gets reloaded by Ajax, when the selection changes. Regards Helmut
Re: [TOBAGO] tx:date in a popup
Hi Fernando, we have fixed the bug in IE. Can you please test the 1.0.25-SNAPSHOT if it works for you? You have to build it by yourself. Is this okay for you? Regards Udo Am 18.03.10 14:29, schrieb Udo Schnurpfeil: Hi, It seems to be a bug. It is correct that you tested it with Internet Explorer? With Firefox it works fine. On the demo app, the AJAX variant to open the popup hasn't this bug. Maybe this is a quick workaround for you. Regards, Udo Am 17.03.10 17:41, schrieb Fernando Augusto: Hello, I am using Tobago 1.0.24 and just ran in a weird situation... I have a form inside a popup, that uses tx:date. When I click in the calendar icon, only the modal DIV appears, behind the popup. I must click the calendar again to show it correctly. I already tried to change the modal property of the popup window to false, but the behavior continues... How can I make the calendar icon to appear in a single click, while the form is inside the popup? Best Regards, Fernando Augusto
Re: [Tobago] Problem using JSP tags with attributes
Hi Alf,
The expression #{${dataBean}.errors} works in older Servlet APIs with
Tobago.
It should work until Tomcat 5.5, but doen't work with Tomcat 6.0.
It also doesn't work with Facelets, but in Facelets you may use
#{dataBean.errors} instead.
For JSPs #{dataBean.errors} will work, when dataBean is in some context,
it depends on your application, what is the best way to put in in the
context.
Regards,
Udo
Am 18.03.10 09:26, schrieb Alf Felis:
Hi all,
I have a problem using jsp tags with attributes in tobago.
Tobago version: 1.0.24-SNAPSHOT
Myfaces version: 1.1.6
Tomcat version: 6.0.18
I'm using a tag with the attribute %@ attribute name=dataBean %.
If I try to access this attribute inside the tag I get a ParseException.
Access:
---
tc:sheet value=#{${dataBean}.errors} ...
Exception:
--
org.apache.commons.el.parser.ParseException: Encountered { at line 1, column
4.
Was expecting one of:
} ...
. ...
...
gt ...
Is there a problem with the EL parser? Do I have to use a different one?
Best regards,
Alf
Re: [TOBAGO] formatting fields with tx:in
Hi Fernando, this feature is not implemented yet. A global solution might be, sending the String via AJAX on blur to the Converter and let him Format it. We should add this into JIRA. But I don't know, if I want that while typing. It may be irritating the user. Nevertheless you can realize it for your application writing JavaScript. Regards, Udo Am 17.03.10 17:44, schrieb Fernando Augusto: Hello, Is there a way to make tx:in to format the string passed (like a phone number, or anything like) while the user is typing? I tried f:convertNumber to make the currency format but it is not working. Any help on the issue? Best Regards, Fernando Augusto
Re: [TOBAGO] tx:date in a popup
Hi, It seems to be a bug. It is correct that you tested it with Internet Explorer? With Firefox it works fine. On the demo app, the AJAX variant to open the popup hasn't this bug. Maybe this is a quick workaround for you. Regards, Udo Am 17.03.10 17:41, schrieb Fernando Augusto: Hello, I am using Tobago 1.0.24 and just ran in a weird situation... I have a form inside a popup, that uses tx:date. When I click in the calendar icon, only the modal DIV appears, behind the popup. I must click the calendar again to show it correctly. I already tried to change the modal property of the popup window to false, but the behavior continues... How can I make the calendar icon to appear in a single click, while the form is inside the popup? Best Regards, Fernando Augusto
Re: [Tobago] Problem using JSP tags with attributes
Okay, I think I understand what you need.
In Tobago the tx:-library was similar. Take some components and combine
it to a new one. But because of the disadvantages of Tag-Files we coded
it with Java-Code :-(
Did you tried running your app with Tomcat 5.5?
There are different solutions. The old solutions doesn't work in new
Containers with the new JSF spec.
When using Facelets, this will work also with JSF 1.1 and JSF 1.2.
There might be an ugly solution, but I didn't tried it:
JSP:
% request.put(x, Foo) %
my:tag/
% request.put(x, Bar) %
my:tag/
Tag-File:
tc:label value=#{x} /
It is ugly, because the parameter x can't be seen and I think it will
run only with JSF 1.1, but not with JSF 1.2.
You can't use % % in Tag-Files, so you can't nest it.
My suggestions is: Use Facelets when you can.
The good end: The JSF 2.0 Composite Components is the *real* solution
for that issue :-)
Regards,
Udo
Am 18.03.10 16:17, schrieb Alf Felis:
I will try to discribe what I am going to do...
For example I will create a sheet (panel, box, etc.) which I can use in
different pages. The sheet content should be filled from different beans. Some
pages should contain the sheet twice with two different beans containing the
data to be displayed.
How do I solve this problem?
My approach was using jsp tag files containing the sheet part with%@ attribute
name=... %, but apparently this doesn't work.
Possibly there is a better solution?
Best regards,
Alf
Re: [TOBAGO] Master-Detail
Hello Fernando,
here are the allowedValues = {click, dblclick} of event in
tc:columnEvent (I've added this to the docu, now).
The tc:attribute is the Tobago-version for f:attribute. The allowed (and
reasonable) values for name and value depends on the parent UIComponent.
Regards,
Udo
Fernando Augusto schrieb:
Thanks for your help, Marcus.
But now comes the doubt... Where can I find which column events can I
work with? and, already referring to the last msg I sent, which
attributes does tc:attribute accepts and when?
Regards,
Fernando Augusto
Marcus Kröger escreveu:
Hi Fernando,
pls have a look at the tobago addressbook example. There you can find a
solution how to react on click-events in a tobago sheet. For
example, by
using
tc:columnEvent event=dblclick
tc:command action=#{controller.editAddress}/
/tc:columnEvent
you would react on a double click on the row. The addressbook example
can be
found in the current build 1.0.24 below /example/addressbook and can be
started by using mvn jetty:run-expploded in the war directory.
Cheers
Marcus
2010/3/9 Fernando Augusto ferna...@osmanager.com.br
Hello,
I am new to Tobago and to JSF, and I got a problem while thinking in
a way
to implement a master-detail form, or any way to show the details of
a row
when clicked on somewhere. The problem is: that action needs to be
performed
by a *single click* action, for usability reasons. I cant make the
user to
select a row AND click a button.
I was doing it with plain JSF using a commandLink and f:param tag
passing
the row ID to a method called by the actionListener and then
redirecting,
using a static action, to another page. But my boss have seen how
easy is to
make popups and form rendering in Tobago, and asked me to make a Tobago
version of our system. Everything seems to be pretty straightforward in
tobago, RANT except this and those weird and undocumented
tc:attribute
uses... I still need to find anything about them... /RANT
So, is there a way to implement Master-Detail approach in Tobago???
Best Regards,
Fernando Augusto
Re: Tobago Renderer with JSF RI
Hi, generally Tobago can not be combined with any other tags libs freely. You can use f: tags, but not h: tags. The main reason is, that in Tobago every container has a layout-manager which set the position of the component. You may use tc:link instead of h:commandLink. An other effect is, that the tc:link will be rendered with the configured theme automatically. Hope that helps. Udo Pierre Martin schrieb: Hi all, I got this project that runs basically with simple JSF RI components. Now I'm trying to include Tobago components in the project. Since I included all the libs required, it seems taht my RI components are trying to get rendered by my tobago renderer. In glassfish I got this stack : Wrong type: Need org.apache.myfaces.tobago.component.UICommand, but was javax.faces.component.html.HtmlCommandLink I'm very new to tobago. Am I doing something wrong? Here is my tobago-config.xml tobago-config theme-config default-themerichmond/default-theme /theme-config resource-dirtobago-resource/resource-dir resource-dirorg/apache/myfaces/tobago/renderkit/resource-dir /tobago-config tanx! -- A man is rich in proportion to the number of things he can afford to let alone. - Thoreau
Re: [Tobago] Locale changed when handling exceptions
Hi Alf, where do you call FacesContext.getCurrentInstance().getViewRoot().setLocale(selectedLocale)? Do you use the f:view locale= attribute? Refards, Udo Alf Felis schrieb: Hi all, my assumption was wrong that the session will be invalidated! But my problem still exist... the locale will be overwritten. Any ideas? Regards, Alf -Ursprüngliche Nachricht- Von: Alf Felis alf.fe...@gmx.de Gesendet: 20.01.10 15:27:27 An: MyFaces Discussion users@myfaces.apache.org Betreff: Re: [Tobago] Locale changed when handling exceptions Hi again :) I noticed, that apparently the whole session will be invalidated, because some other attributes will be lost, too. Is there any parameter or something else to disable this behaviour? Regards, Alf - original Nachricht Betreff: [Tobago] Locale changed when handling exceptions Gesendet: Mi, 20. Jan 2010 Von: Alf Felisalf.fe...@gmx.de Hi all, I have a problem with the locale and the error handling. My application provides the possibility to choose the preferred language. I set the selected locale with the following code FacesContext.getCurrentInstance().getViewRoot().setLocale(selectedLocale); Everything works fine until the error page is called. For any exception I use one error page set within the web.xml. error-page exception-typejava.lang.Throwable/exception-type location/faces/ErrorPage.jsp/location /error-page If now an error occurred the locale set by my code above will be overridden and set to the browser locale. How can I avoid this? Best regards, Alf --- original Nachricht Ende
Re: [Tobago] File upload tc:file tx:file
Hi,
I've just tested the two actual wars (1.0.24-SNAPSHOT and
1.5.0-alpha-2-SNAPSHOT).
I've hot-deployed it with copying to webapps/ROOT.war in a new installed
tomcat 6.0.20.
In both version the upload.jsp works fine.
So I can't reproduce the problem sadly.
Regards
Udo
Søren Hjarlvig schrieb:
Hi again,
Now I have found the cause for the no styles-error:
My own app is deployed in the ROOT-context (/), if I deploy it under some
other context (e.g. /somewebapp) upload works!
If I deploy the example-demo app in the ROOT-context, upload fails there
too, e.g.:
Context path=/
docBase=C:/work/myfaces-tobago-1.0.23/tobago-example-demo-1.0.23 /
Best regards
Soeren
2009/10/24 Søren Hjarlvig s...@bluewhale.dk
Hi Udo,
Thank you for your reply.
I have applied the suggested changes to the example-demo application and,
as you said, it works fine.
So now I know that the problem is not related to my Tomcat or Java
installation. I must try to figure out the difference between my own app and
the example-demo app...
Best regards
Soeren
2009/10/22 Udo Schnurpfeil u...@schnurpfeil.de
Hi Søren,
I've checked the upload and can't find problems. The reference/upload.jsp
file in the demo is not full functional yet. So I added some stuff. You may
apply these changes on tobago-example-demo on your system and look if it
works fine or at any differences.
Hope that helps.
Regards
Udo
--
reference/upload.jsp
tx:file label=Upload file: value=#{upload.file} /
tc:button label=Submit defaultCommand=true
action=#{upload.upload} /
--
faces-config.xml
managed-bean
managed-bean-nameupload/managed-bean-name
managed-bean-classorg.apache.myfaces.tobago.example.reference.Upload/managed-bean-class
managed-bean-scopesession/managed-bean-scope
/managed-bean
--
Upload.java (new)
package org.apache.myfaces.tobago.example.reference;
import org.apache.commons.fileupload.FileItem;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
public class Upload {
private static final Log LOG = LogFactory.getLog(Upload.class);
private FileItem file;
public String upload() {
LOG.info(type= + file.getContentType());
LOG.info(file= + file.get().length);
LOG.info(name= + file.getName());
return null;
}
public FileItem getFile() {
return file;
}
public void setFile(FileItem file) {
this.file = file;
}
}
--
Søren Hjarlvig schrieb:
Hi,
I'm attempting to use the tc:file / tx:file control to upload a file.
But when I click the button responsible for submitting the page the
associated action is not invoked, the page is refreshed and showed without
any styles (!?).
Without the tx:file-tag everything works fine.
JSP:
tx:file value=#{controller.fileItem} required=false label=Upload
file /
tc:button action=#{controller.save} label=Save/
I have added the following to my web.xml:
filter
filter-namemultipartFormdataFilter/filter-name
filter-classorg.apache.myfaces.tobago.webapp.TobagoMultipartFormdataFilter/filter-class
init-param
descriptionSet the size limit for uploaded
files.../description
param-nameuploadMaxFileSize/param-name
param-value20m/param-value
/init-param
init-param
descriptionSet the upload repository path for uploaded
files. Default value is java.io.tmpdir./description
param-nameuploadRepositoryPath/param-name
param-valuec:/tmp/param-value
/init-param
/filter
filter-mapping
filter-namemultipartFormdataFilter/filter-name
url-pattern/faces/*/url-pattern
/filter-mapping
There are no errors or warnings, the debug log says:
...
DEBUG 21 okt 16:38:30
org.apache.myfaces.tobago.webapp.TobagoMultipartFormdataFilter - Wrapping
org.apache.catalina.connector.RequestFacade with
ContentType=multipart/form-data;
boundary=---209722283024901 into
TobagoMultipartFormdataRequest
...
DEBUG 21 okt 16:38:30
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.FileRenderer
- Uploaded file name : image001.gif size = 5558
...
I'm using Tobago 1.0.23 / MyFaces 1.1.6 / Tomcat 6.0.20 / Java 6u15.
I hope someone can provide a hint. Thanks.
Best regards
Soeren
--
Med venlig hilsen / Best regards
Søren Hjarlvig
Partner, M.Sc.E
Bluewhale ApS
Fruebjergvej 3, boks 1
DK-2100 Copenhagen Ø
Denmark
(+45) 39 17 99 72 Phone
(+45) 39 17 99 73 Support
(+45) 22 85 70 04 Mobile
Re: [Tobago] File upload tc:file tx:file
Hi Søren,
I've checked the upload and can't find problems. The
reference/upload.jsp file in the demo is not full functional yet. So I
added some stuff. You may apply these changes on tobago-example-demo on
your system and look if it works fine or at any differences.
Hope that helps.
Regards
Udo
--
reference/upload.jsp
tx:file label=Upload file: value=#{upload.file} /
tc:button label=Submit defaultCommand=true
action=#{upload.upload} /
--
faces-config.xml
managed-bean
managed-bean-nameupload/managed-bean-name
managed-bean-classorg.apache.myfaces.tobago.example.reference.Upload/managed-bean-class
managed-bean-scopesession/managed-bean-scope
/managed-bean
--
Upload.java (new)
package org.apache.myfaces.tobago.example.reference;
import org.apache.commons.fileupload.FileItem;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
public class Upload {
private static final Log LOG = LogFactory.getLog(Upload.class);
private FileItem file;
public String upload() {
LOG.info(type= + file.getContentType());
LOG.info(file= + file.get().length);
LOG.info(name= + file.getName());
return null;
}
public FileItem getFile() {
return file;
}
public void setFile(FileItem file) {
this.file = file;
}
}
--
Søren Hjarlvig schrieb:
Hi,
I'm attempting to use the tc:file / tx:file control to upload a file.
But when I click the button responsible for submitting the page the
associated action is not invoked, the page is refreshed and showed
without any styles (!?).
Without the tx:file-tag everything works fine.
JSP:
tx:file value=#{controller.fileItem} required=false label=Upload
file /
tc:button action=#{controller.save} label=Save/
I have added the following to my web.xml:
filter
filter-namemultipartFormdataFilter/filter-name
filter-classorg.apache.myfaces.tobago.webapp.TobagoMultipartFormdataFilter/filter-class
init-param
descriptionSet the size limit for uploaded
files.../description
param-nameuploadMaxFileSize/param-name
param-value20m/param-value
/init-param
init-param
descriptionSet the upload repository path for uploaded
files. Default value is java.io.tmpdir./description
param-nameuploadRepositoryPath/param-name
param-valuec:/tmp/param-value
/init-param
/filter
filter-mapping
filter-namemultipartFormdataFilter/filter-name
url-pattern/faces/*/url-pattern
/filter-mapping
There are no errors or warnings, the debug log says:
...
DEBUG 21 okt 16:38:30
org.apache.myfaces.tobago.webapp.TobagoMultipartFormdataFilter -
Wrapping org.apache.catalina.connector.RequestFacade with
ContentType=multipart/form-data;
boundary=---209722283024901 into
TobagoMultipartFormdataRequest
...
DEBUG 21 okt 16:38:30
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.FileRenderer
- Uploaded file name : image001.gif size = 5558
...
I'm using Tobago 1.0.23 / MyFaces 1.1.6 / Tomcat 6.0.20 / Java 6u15.
I hope someone can provide a hint. Thanks.
Best regards
Soeren
Re: Trinidad vs Tobago
Hi Helmut, it is an important goal to make it possible to run a Tobago 1.0.21 application with Tobago 1.1 with little or without effort. In particular cases, there a some changes to do, but the main idea is, that applications will run. To be compatible, you should not use code which is marked as deprecated, of course. For your project, you may start with 1.0 and switch to 1.1 if we have a stable release. Regards, Udo Helmut Swaczinna schrieb: Hi Udo, well, this sounds good. But what about the release plan for a stable 1.1.0 version? We're thinking about lauching a new project starting with 1.1.0 to have the benefits of the new layout manager. But our project schedule is very short, so we don't have the time to deal with new bugs etc. How about the compatibility between 1.0.x and 1.1.x. Is it possible to port a 1.0.x app to 1.1.x with little effort and vice versa? Regards Helmut Udo Schnurpfeil schrieb: Hi all, let me explain the actual status of the Tobago development: We have branched the development into the tobago-1.0.x branch and the trunk which is the next major release. The tobago-1.0.x branch is stable and basis of the actual releases. The next release (1.0.21) will come up in the next days. This branch contains bugfixes and some (smaller) new features. You can see the changes of the next release here: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310273fixfor=12313470 The trunk (1.1.x) is an area of many refactorings and implementation of new features. But the status is still alpha. Here is a list of issues for the next major release: * Reimplementation of the layout management: - make renderer more independent from the layout management. - more flexible - more type of layout managers - better testability (unit tests) - better support for browser-window resizing * New tree implementation * Better support for integrating 3rd party components * Client side coordinates of action event on server side (mouse event, click event) * simplify css and javascript files * support for many tabs * improved sheet performance * more support for other renderkits and many internal refactorings (plan) * Generating tag classes and components * Enhanced tobago lifecyle with buildView layoutView (registerResource) / encodeView (renderResponse) * UIPopup should be a subform * UITab should be a naming container (which tab contains a component with a Message) * Z-Index Provider * replace prototype with dojo * replace commons-logging with slf4j * Remove deprecated methods and classes * public and internal packages(public api and internal api) * remove some static classes * improved TobagoResponseWriter for javascript (JSON) * TabGroup should be an ActionSource * TabChangeEvent should be an ActionEvent * requiredMessage validatorMessage converterMessage for all EditableValueHolder in Tobago Regards Udo kanth99 schrieb: Hi all, Thanks for your replies. Groovie wrote: On Thu, Jun 4, 2009 at 2:21 AM, Christian Groove groo...@groovesytems.de wrote: Salut Hi All, We are developing a web application with myfaces. That's fine, JSF is the cool think. I worked with Tobago, that comes with a great layout manager and some cool widgets. It is not my intention to overwhelm that nice project but it seems to be dead. The development that's totally wrong ... I hope you are right, but i looks like (for me) that the development activity slowed down. 2008 was a great year an i was lucky using this wonderful component library. Could you give us a short insight of the current development ? I switched to Richfaces and found it also useful for me. What are the advantages or drawback of one lib comparing the other? Thanks Groovy of new widgets seems not to proceed so you may better look to other Taglibs like Richfaces, Icefaces. Groovy This application needs proper navigation and UI .I have observed Trinidad has good navigation practices and other utilities.Tobago has some good layouts but not good navigation practices.both these technologies have featurs like PPR. Trinidat looks a little bit old-fashioned to me, anyway there seems to be only a little support for AJAX. could some one plaese advice us which is the better technology and the distinct features of these technologies. Thanks, Srikanth
Re: Trinidad vs Tobago
Hi all, let me explain the actual status of the Tobago development: We have branched the development into the tobago-1.0.x branch and the trunk which is the next major release. The tobago-1.0.x branch is stable and basis of the actual releases. The next release (1.0.21) will come up in the next days. This branch contains bugfixes and some (smaller) new features. You can see the changes of the next release here: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310273fixfor=12313470 The trunk (1.1.x) is an area of many refactorings and implementation of new features. But the status is still alpha. Here is a list of issues for the next major release: * Reimplementation of the layout management: - make renderer more independent from the layout management. - more flexible - more type of layout managers - better testability (unit tests) - better support for browser-window resizing * New tree implementation * Better support for integrating 3rd party components * Client side coordinates of action event on server side (mouse event, click event) * simplify css and javascript files * support for many tabs * improved sheet performance * more support for other renderkits and many internal refactorings (plan) * Generating tag classes and components * Enhanced tobago lifecyle with buildView layoutView (registerResource) / encodeView (renderResponse) * UIPopup should be a subform * UITab should be a naming container (which tab contains a component with a Message) * Z-Index Provider * replace prototype with dojo * replace commons-logging with slf4j * Remove deprecated methods and classes * public and internal packages(public api and internal api) * remove some static classes * improved TobagoResponseWriter for javascript (JSON) * TabGroup should be an ActionSource * TabChangeEvent should be an ActionEvent * requiredMessage validatorMessage converterMessage for all EditableValueHolder in Tobago Regards Udo kanth99 schrieb: Hi all, Thanks for your replies. Groovie wrote: On Thu, Jun 4, 2009 at 2:21 AM, Christian Groove groo...@groovesytems.de wrote: Salut Hi All, We are developing a web application with myfaces. That's fine, JSF is the cool think. I worked with Tobago, that comes with a great layout manager and some cool widgets. It is not my intention to overwhelm that nice project but it seems to be dead. The development that's totally wrong ... I hope you are right, but i looks like (for me) that the development activity slowed down. 2008 was a great year an i was lucky using this wonderful component library. Could you give us a short insight of the current development ? I switched to Richfaces and found it also useful for me. What are the advantages or drawback of one lib comparing the other? Thanks Groovy of new widgets seems not to proceed so you may better look to other Taglibs like Richfaces, Icefaces. Groovy This application needs proper navigation and UI .I have observed Trinidad has good navigation practices and other utilities.Tobago has some good layouts but not good navigation practices.both these technologies have featurs like PPR. Trinidat looks a little bit old-fashioned to me, anyway there seems to be only a little support for AJAX. could some one plaese advice us which is the better technology and the distinct features of these technologies. Thanks, Srikanth
Re: Tobago style sheet problem:
Hi, I didn't get what you want to change, sorry. Do you want to change one component on every page, or the general background, or only for a single page? Generally Firebug (for Firefox) is a great tool to find out the structure of the html and check which style effects a component. I agree, that the structure is sometimes not plain, that is an issue to to the Tobago 1.1 release. Regards, Udo kanth99 schrieb: Hi All, I have been modifying the Example demo of Tobago.I wanted to change the color of layout page ,so same will be applicable to all the pages.I modified the div tags in 'style.css' in the primary theme and the other supported themes.But the color of page has not changed. There are so many divs (for example tobago-gridLayout-default ,tobago-tab-link etc..).By changing hte color of which div element will change the color of layout,also how to quickly identify divs related to the components?I think Naming conventions are confusing. Thanks
Re: Trinidad vs Tobago
Hi Christian, I know the issue with the forEach. There are many aspects to notice with the interation stuff. I've written a sample for tobago 1.0.x which works with the c:forEach from the JSTL. But this not works with Facelets and also not with JSP-Tag-Files (because scriptlets are not allowed). I think we will find a solution for Tobago 1.1, but I can't promise it in the moment. An other aproach might be using a binding to a UIPanel, an building the components with Java-Code. That is not nice and has some pitfalls, but may a solution for you. Hope that helps Udo Christian Groove schrieb: Salut Udo, Hi all, let me explain the actual status of the Tobago development: We have branched the development into the tobago-1.0.x branch and the trunk which is the next major release. looks like, . that i was wrong. Tobago is still alive, great. The trunk (1.1.x) is an area of many refactorings and implementation of new features. But the status is still alpha. Here is a list of issues for the next major release: * Reimplementation of the layout management: (...) Another topic you may not thought before. Please reactivate the foreach! I had to code a database driven form with a couple of altering types of input-fields and selection boxes. The jsf-page was programmed as a dynamic formular engine. The taglib met almost all requirements i needed, with one exception: foreach !!! For this reason i hat to abuse the table tag, cause this was the only remaining container-element, that acts like a foreach. This solution had one drawback, the table size does not grow with its contents. So i estimated the size by couting the containing elements and patch the rows/size of the table, b. [stage direction to the audience] time to boo Groovie Voilá, that was the reason, why i needed foreach! Groovy Regards Udo Thanks for your good job. Does your company still uses Tobago ?
Re: Trinidad vs Tobago
I forgot the link: http://svn.apache.org/repos/asf/myfaces/tobago/branches/tobago-1.0.x/example/demo/src/main/webapp/best-practice/for-each.jsp Udo Schnurpfeil schrieb: Hi Christian, I know the issue with the forEach. There are many aspects to notice with the interation stuff. I've written a sample for tobago 1.0.x which works with the c:forEach from the JSTL. But this not works with Facelets and also not with JSP-Tag-Files (because scriptlets are not allowed). I think we will find a solution for Tobago 1.1, but I can't promise it in the moment. An other aproach might be using a binding to a UIPanel, an building the components with Java-Code. That is not nice and has some pitfalls, but may a solution for you. Hope that helps Udo Christian Groove schrieb: Salut Udo, Hi all, let me explain the actual status of the Tobago development: We have branched the development into the tobago-1.0.x branch and the trunk which is the next major release. looks like, . that i was wrong. Tobago is still alive, great. The trunk (1.1.x) is an area of many refactorings and implementation of new features. But the status is still alpha. Here is a list of issues for the next major release: * Reimplementation of the layout management: (...) Another topic you may not thought before. Please reactivate the foreach! I had to code a database driven form with a couple of altering types of input-fields and selection boxes. The jsf-page was programmed as a dynamic formular engine. The taglib met almost all requirements i needed, with one exception: foreach !!! For this reason i hat to abuse the table tag, cause this was the only remaining container-element, that acts like a foreach. This solution had one drawback, the table size does not grow with its contents. So i estimated the size by couting the containing elements and patch the rows/size of the table, b. [stage direction to the audience] time to boo Groovie Voilá, that was the reason, why i needed foreach! Groovy Regards Udo Thanks for your good job. Does your company still uses Tobago ?
Re: [Tobago] Problem migrating to 1.0.15
I've build a simple demo page. It works in the tobago-example-demo on my
box. You may try it.
Regards,
Udo
yazid schrieb:
Still not work, please Help
I've tried the h:selectOneMenu.but I prefer tc:selectOneChoice ...better
for facet.
yazid wrote:
Hi All;
I've migrated last week to 1.0.15; most of component are OK, except for
tc:selectOneChoice inside a sheet columns, it's not rendred at all
tc:column label=.
tc:selectOneChoice value=#{b.name}
f:selectItems value=#{b.items} /
/tc:selectOneChoice
Is that a bug in 1.0.15 or should I do a special use of select...
Thanks
%--
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the License); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an AS IS BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
--%
%@ taglib uri=http://myfaces.apache.org/tobago/component; prefix=tc %
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f %
%@ taglib tagdir=/WEB-INF/tags/layout prefix=layout %
f:view
tc:page width=500px height=500px
f:facet name=layout
tc:gridLayout/
/f:facet
tc:sheet value=#{demo.solarList} columns=*;2* var=bean rows=10
showPageRange=left
tc:column label=Number
tc:in value=#{bean.name} required=true/
/tc:column
tc:column label=Select
tc:selectOneChoice value=#{bean.population}
f:selectItems value=#{demo.toolbarIconItems}/
/tc:selectOneChoice
/tc:column
/tc:sheet
/tc:page
/f:view
Re: [Tobago] Problem migrating to 1.0.15
Hi there,
I've tested it and I didn't found any problems. Can you build a simple
standalone JSP of your problem?
You may also check, if you've set the columns attribute of the sheet
correctly.
Regards,
Udo
yazid schrieb:
Hi All;
I've migrated last week to 1.0.15; most of component are OK, except for
tc:selectOneChoice inside a sheet columns, it's not rendred at all
tc:column label=.
tc:selectOneChoice value=#{b.name}
f:selectItems value=#{b.items} /
/tc:selectOneChoice
Is that a bug in 1.0.15 or should I do a special use of select...
Thanks
Re: Fw: Pb installing Tobago examples app.
Hello, the demo (1.0.11 and 1.0.12-SNAPSHOT) is running on my tomcat 6 (MacOSX 10.4, Java 6) without problems. Which OS and which Java you are using? Do you using Tomcat standalone? I've seen Glassfish in the first stacktrace. Regards Udo clec schrieb: Hello, About my previous email, I scanned the log more closely and there is an exception preceeding the one I mentionned when the application starts. However, the '/WEB-INF/tobago-config.xml' IS present in the application directory !! Thanks to anyone that has ideas of what could be wrong, there. Clec - GRAVE: Exception lors de l'envoi de l'évènement contexte initialisé (context initialized) à l'instance de classe d'écoute (listener) org.apache.myfaces.tobago.webapp.TobagoServletContextListener java.lang.RuntimeException: Error while deploy process. Tobago can't be initialized! Application will not run! at org.apache.myfaces.tobago.webapp.TobagoServletContextListener.contextInitialized(TobagoServletContextListener.java:72) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) === Caused by: javax.faces.FacesException: No config file found: '/WEB-INF/tobago-config.xml'. Tobago can't run without configuration. === at org.apache.myfaces.tobago.config.TobagoConfigParser.parse(TobagoConfigParser.java:112) at org.apache.myfaces.tobago.config.TobagoConfigParser.parse(TobagoConfigParser.java:50) at org.apache.myfaces.tobago.webapp.TobagoServletContextListener.contextInitialized(TobagoServletContextListener.java:53) Créez votre adresse électronique [EMAIL PROTECTED] 1 Go d'espace de stockage, anti-spam et anti-virus intégrés.
Re: [tobago] how can I have a list of radio boxes in a sheet (one in each line) and belonging to the same group
Hallo Zied,
there is a special tag for almost this job: tc:columnSelector.
But AFAIK in the moment the only selection model is multiselect. This
tag should be extended to other selection models like singleselect.
You may add a JIRA issue for this.
Regards
Udo
Zied Hamdi schrieb:
is it possible to do sth like:
tc:sheet id=phones columns=50px;15*;18px;18px value=
#{personCtrl.current.bean.phones} var=phone
...
tc:column label=#{i18n.main} sortable =true
tc:selectOneRadio id= main value=#{phone.main}
f:selectItem id= mainPhone itemValue=false itemLabel= /
/tc:selectOneRadio /tc:column
...
/tc:sheet and join occurences with a group name (to have the radio
buttons behaviour) ???. Note: maybe if it's not possible today, may we
extend the taglib selectOneRadio to see if the same id is many times
in the sheet...
Re: [Tobago] tx:date EndDate not before BeginDate
I only see 2 options, both standard JSF:
1. check manually in the action method, use facesContext.addMessage()
2. write your own validator
I don't know a more declarative way in the moment.
Regards,
Udo
Clemens Sietas schrieb:
Hello,
I have another question regarding the datepicker.
Can I easily ensure in JSF-coding that the
selectedVldtyEnd cannot be selected with a smaller date
than the selectedVldtyBeg?
For example with f:validate...
Regards,
Clemens
tx:date id=vldtyBeg
value=#{controller.selectedVldtyBeg}
label=#{controller.keyLblValidityBegin}
readonly=#{controller.forEditSelected}
f:convertDateTime pattern=dd.MM./
/tx:date
tx:date id=vldtyEnd
value=#{controller.selectedVldtyEnd}
label=#{controller.keyLblValidityEnd}
f:convertDateTime pattern=dd.MM./
/tx:date
