Re: Option for NavigationHandler to support viewIds as outcome
Hi again, Thank you very much for your opinions and insights. I understand now that there are doubts supporting such a feature. What I understood these are mainly about encouraging users to use not best practise approaches. IMO this is for sure a duty of teachers or books, but a webdevelopment framework? I'm not so sure about that. I think users should be provided with as much flexibility as possible rather than trying to force them to share all our philosophy. And also this is as martin and mattias pointed out usable in small scale applications tiny prototypes and so on. Seeing competitions as ruby on rails and php features like that could make JSF also more attractive for prototyping. But thats just my opinion and I'm for sure not starting to do something not approved by the community again. So what is the desicion? 1.) Seperate NavigationHandlerImpl 2.) Configurable Option 3.) Custom NH code in the wiki with a discouraged note 4.) Not at all regards Ernst On 10/30/06, Matthias Wessendorf [EMAIL PROTECTED] wrote: I am really fine with adding this NH_Impl to Tomahawk. Here are my rules for that: -It is not used by default! -it is not configured to a bogus web.xml context param -it should be used in the app's faces-cfg.xml file the cons and pros are like Do you like Rails, or not :) Well, somethimes that makes sense; sometimes not. The fun is, that you can choose! Just put it to your faces-cfg. I have heard that requirement before that thread. I don't think it's a not understanding JSF thing. Sorta lazy guy approach ... -M On 10/30/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 10/30/06, Mario Ivankovits [EMAIL PROTECTED] wrote: In reality there is a dependency between two pages, there is a silent contract how to prepare the managed beans so that the destination page knows what to display (and I think the f:param stuff is useless here). So more often than not you'll use a updateActionListener to set stuff on the destination backing bean. And voilla, you'll have hard dependency between these two pages. This is an important point, no matter how you architect your navigation. shameless-plug That is why Shale's view controller has a prerender() method ... you are encouraged to use that method in the destination page to pull data that this page needs out of the model, rather than having the origin page push data into the destination page (or some request scoped objects whose names are known to both). That way, coupling is minimized to something like passing primary keys -- and I like the convention of always passing, say, a customerId, in the same place throughout the application (independent of particular pages), to minimize direct coupling between any two particular pages. This approach also makes it *much* easier for your application to support bookmarkable GET URLs that pass primary keys with request parameters. /shameless-plug Craig -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: Option for NavigationHandler to support viewIds as outcome
Hi! 1.) Seperate NavigationHandlerImpl IMHO, this is a must! I think we should *not* implement stuff which silently changes/enhances the behaviour - especially in myfaces-impl!! The TCK might forbid this change anyway ... 2.) Configurable Option not required, as everyone can configure this NH in faces-config.xml. 3.) Custom NH code in the wiki with a discouraged note This might be a good compromise. 4.) Not at all I do not mind ;-) 5) Add the new NH to the sandbox (but not configured by default) I like it to put stuff to the sandbox first and see if the community is willing to use them something like the time will tell if its worth. Ciao, Mario
Re: Option for NavigationHandler to support viewIds as outcome
As an outcome of this discussion, I'm +1 for 1. regards, Martin On 10/31/06, Mario Ivankovits [EMAIL PROTECTED] wrote: Hi! 1.) Seperate NavigationHandlerImpl IMHO, this is a must! I think we should *not* implement stuff which silently changes/enhances the behaviour - especially in myfaces-impl!! The TCK might forbid this change anyway ... 2.) Configurable Option not required, as everyone can configure this NH in faces-config.xml. 3.) Custom NH code in the wiki with a discouraged note This might be a good compromise. 4.) Not at all I do not mind ;-) 5) Add the new NH to the sandbox (but not configured by default) I like it to put stuff to the sandbox first and see if the community is willing to use them something like the time will tell if its worth. Ciao, Mario -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
[jira] Created: (TOBAGO-167) Enable rendering popups by ajax request
Enable rendering popups by ajax request --- Key: TOBAGO-167 URL: http://issues.apache.org/jira/browse/TOBAGO-167 Project: MyFaces Tobago Issue Type: Improvement Reporter: Volker Weber Assigned To: Volker Weber Priority: Minor Fix For: 1.0.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TOMAHAWK-760) modalDialog shows in page instead of being a popup in Internet Explorer
modalDialog shows in page instead of being a popup in Internet Explorer --- Key: TOMAHAWK-760 URL: http://issues.apache.org/jira/browse/TOMAHAWK-760 Project: MyFaces Tomahawk Issue Type: Bug Affects Versions: 1.1.5-SNAPSHOT Reporter: Ernst Fastl Fix For: 1.1.5-SNAPSHOT modalDialog shows in page instead of being a popup in Internet Explorer since the lates changes in the DojoUtils stuff I couldn't figure out why this doesn't work anymore so far but it could be related to ressource loading since the page seems to try to load something for a rather long time -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MYFACES-1478) Implement JSR-252 core tag: convertDateTimeTag
[ http://issues.apache.org/jira/browse/MYFACES-1478?page=all ] Andreas Berger updated MYFACES-1478: Status: Patch Available (was: Open) Implement JSR-252 core tag: convertDateTimeTag -- Key: MYFACES-1478 URL: http://issues.apache.org/jira/browse/MYFACES-1478 Project: MyFaces Core Issue Type: Sub-task Reporter: Andreas Berger -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1484) Implement JSR-252 core tag: phaseListenerTag
Implement JSR-252 core tag: phaseListenerTag Key: MYFACES-1484 URL: http://issues.apache.org/jira/browse/MYFACES-1484 Project: MyFaces Core Issue Type: Sub-task Reporter: Andreas Berger -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Ajax/ActiveMQ supports MyFaces, Portlets, Spring frameworks ??
Thanks Arash. I will go through the link and get back to you if i have any queries. cheers jagdip Arash Rajaeeyan wrote: myfaces uses DOJO check this tag: http://myfaces.apache.org/tomahawk/dojoInitializer.html may be you can do what ever you want with dojo. On 10/30/06, jt_rm [EMAIL PROTECTED] wrote: [EMAIL PROTECTED], We would like to use Ajax/ActiveMQ (AMQ servlets) for server-push feature in some of our usecases in the webapplication project. We are shortlisting to use opensource AppFuse application using MyFaces - Spring - Hibernbate frameworks for our webapplication development. We would like to know whether ActiveMQ-Ajax servlets provides:- -integration with myFaces -integrates with Spring -portlets support In the opensource AppFuse application, DWR integrates with Spring and MyFaces and also supports portlets. Hence, We are contemplating whether to use DWR or Ajax/ActiveMQ to provide server-push feature in our application, based on the above clarifications. We greatly appreciate your advise for the above queries. thanks and regards jt_rm -- View this message in context: http://www.nabble.com/Ajax-ActiveMQ-supports-MyFaces%2C-Portlets%2C-Spring-frameworkstf2540298.html#a7077304 Sent from the My Faces - Dev mailing list archive at Nabble.com. -- Arash Rajaeeyan -- View this message in context: http://www.nabble.com/Ajax-ActiveMQ-supports-MyFaces%2C-Portlets%2C-Spring-frameworkstf2540298.html#a7092891 Sent from the My Faces - Dev mailing list archive at Nabble.com.
How to dynamically show different components for each row in a table
I have a Table that has a column containing buttons for operations on each row. Each row may have different operations applicable to it, so the buttons for each row need to be determined dynamically based on the contents of row. I have seen code to dynamically create buttons, but what I would like to know is how to do this on a per-row basis, so that row 1 would might have 1 button, row 2 would have 3 buttons and so on. I would like to avoid the solution of creating all of the possible types of buttons and hiding the ones that do not apply to the current row. -- View this message in context: http://www.nabble.com/How-to-dynamically-show-different-components-for-each-row-in-a-table-tf2545575.html#a7093117 Sent from the My Faces - Dev mailing list archive at Nabble.com.
[jira] Updated: (MYFACES-1484) Implement JSR-252 core tag: phaseListenerTag
[ http://issues.apache.org/jira/browse/MYFACES-1484?page=all ] Andreas Berger updated MYFACES-1484: Status: Patch Available (was: Open) Implement JSR-252 core tag: phaseListenerTag Key: MYFACES-1484 URL: http://issues.apache.org/jira/browse/MYFACES-1484 Project: MyFaces Core Issue Type: Sub-task Reporter: Andreas Berger Attachments: PhaseListenerTag.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1485) Implement JSR-252 core tag: FacetTag
Implement JSR-252 core tag: FacetTag Key: MYFACES-1485 URL: http://issues.apache.org/jira/browse/MYFACES-1485 Project: MyFaces Core Issue Type: Sub-task Reporter: Andreas Berger -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TOBAGO-168) DatePicker needs extra height when time controll is used
DatePicker needs extra height when time controll is used Key: TOBAGO-168 URL: http://issues.apache.org/jira/browse/TOBAGO-168 Project: MyFaces Tobago Issue Type: Bug Reporter: Volker Weber Assigned To: Volker Weber Fix For: 1.0.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: How to dynamically show different components for each row in a table
My table maybe each row(column) need different UI component(radio,button,checkbox,textbox,etc), so,use rendered attribute,it's not enough, I need ,dynamically creat my table depending data type from select from database data, btw,thanks you advise -- View this message in context: http://www.nabble.com/How-to-dynamically-show-different-components-for-each-row-in-a-table-tf2545575.html#a7095132 Sent from the My Faces - Dev mailing list archive at Nabble.com.
[jira] Resolved: (TOBAGO-168) DatePicker needs extra height when time controll is used
[ http://issues.apache.org/jira/browse/TOBAGO-168?page=all ] Volker Weber resolved TOBAGO-168. - Resolution: Fixed DatePicker needs extra height when time controll is used Key: TOBAGO-168 URL: http://issues.apache.org/jira/browse/TOBAGO-168 Project: MyFaces Tobago Issue Type: Bug Reporter: Volker Weber Assigned To: Volker Weber Fix For: 1.0.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: How to dynamically show different components for each row in a table
I had a similar problem where I wanted to display different UI input components depending on the type of data in the row (ie String, Date, Double etc). I found the easiest way to do this was to add ALL the options and select which is displayed using the rendered attribute. I also did not want to just 'hide' the ones that did not apply, however as far as I know the rendered attribute doesn't just hide the component, it doesn't even create it. I needed this behaviour otherwise I would have got runtime errors eg trying to call a String method on a Double. Hope this helps, Nick kevin_zhai wrote: I have a Table that has a column containing buttons for operations on each row. Each row may have different operations applicable to it, so the buttons for each row need to be determined dynamically based on the contents of row. I have seen code to dynamically create buttons, but what I would like to know is how to do this on a per-row basis, so that row 1 would might have 1 button, row 2 would have 3 buttons and so on. I would like to avoid the solution of creating all of the possible types of buttons and hiding the ones that do not apply to the current row. -- View this message in context: http://www.nabble.com/How-to-dynamically-show-different-components-for-each-row-in-a-table-tf2545575.html#a7094611 Sent from the My Faces - Dev mailing list archive at Nabble.com.
Re: Option for NavigationHandler to support viewIds as outcome
On 10/31/06, Mario Ivankovits [EMAIL PROTECTED] wrote: Hi! 1.) Seperate NavigationHandlerImpl IMHO, this is a must! I think we should *not* implement stuff which silently changes/enhances the behaviour - especially in myfaces-impl!! The TCK might forbid this change anyway ... +1 ! 2.) Configurable Option not required, as everyone can configure this NH in faces-config.xml. right! adding stuff to the web.xml for that is blech! 3.) Custom NH code in the wiki with a discouraged note This might be a good compromise. like we do with the JBoss stuff ? I don't mind that 4.) Not at all I do not mind ;-) 5) Add the new NH to the sandbox (but not configured by default) I like it to put stuff to the sandbox first and see if the community is willing to use them something like the time will tell if its worth. Yes, my understanding is that EVERY new Tomahawk stuff goes to Sandbox first. Components AND framework features. Go ahead Ernstl -M Ciao, Mario -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
[jira] Created: (TOMAHAWK-761) inputCalendar doesn't work as popup in tomahawk-1.1.3
inputCalendar doesn't work as popup in tomahawk-1.1.3 - Key: TOMAHAWK-761 URL: http://issues.apache.org/jira/browse/TOMAHAWK-761 Project: MyFaces Tomahawk Issue Type: Bug Components: Calendar Affects Versions: 1.1.3 Environment: Websphere 6 Reporter: Travis Delph When using the inputCalendar component, it will not render correctly as a popup with the tomahawk-1.1.3 jar. I have it working with just displaying to the page (non-popup). It seems that this issue is directly related with the popup component not working properly either. Has anyone solved this issue? Thanks in advance, Travis -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Tomcat SNAPSHOT is missing, 1.2 impl cannot be built
Looks like the 1.2 branch [2] does not work on a fresh co because the tomcat jars have been removed from the apache repo [1]. Does anyone know where they have gone to? I seem to remember the Mortbay jars working quite well for us. Is there any reason this was changed? Dennis Byrne [1] http://people.apache.org/repo/m2-snapshot-repository/org/apache/ [2] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.tomcat:jasper-el:jar:6.0.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=jasper-e l \ -Dversion=6.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.myfaces.core:myfaces-api:jar:1.2.0-SNAPSHOT 2) org.apache.tomcat:jasper-el:jar:6.0.0-SNAPSHOT 2) org.apache.tomcat:el-api:jar:6.0.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=el-api \ -Dversion=6.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.myfaces.core:myfaces-api:jar:1.2.0-SNAPSHOT 2) org.apache.tomcat:el-api:jar:6.0.0-SNAPSHOT -- 2 required artifacts are missing. for artifact: org.apache.myfaces.core:myfaces-api:jar:1.2.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (https://maven-repository.dev.java.net/nonav/repository), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), myfaces-repo (http://myfaces.zones.apache.org/dist/maven-repository)
Re: Option for NavigationHandler to support viewIds as outcome
I think we should be very careful about adding a feature that encourages people to drift away from the spec. I agree with the reasons that Craig laid out for why the outcomes behave the way they do now. Its true that its not our job to force people to do follow certain standards. Its also true that we shouldn't be putting code into a shared codebase that serves the needs of a minority of the participants. I am not hearing a lot of enthusiastic support for this idea. Reactions are ranging from as long as its optional to this has no place in JSF. I think we should keep this out of Tomahawk. People are free to do whatever they want with their own code so this seems to be a case where that is most appropriate. Use it in your personal code and writeup a wiki or blog entry on it if you want to share it. Not everything has to make it in and it seems like enough people have reservations about it. My .02 Sean On 10/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote: On 10/31/06, Mario Ivankovits [EMAIL PROTECTED] wrote: Hi! 1.) Seperate NavigationHandlerImpl IMHO, this is a must! I think we should *not* implement stuff which silently changes/enhances the behaviour - especially in myfaces-impl!! The TCK might forbid this change anyway ... +1 ! 2.) Configurable Option not required, as everyone can configure this NH in faces-config.xml. right! adding stuff to the web.xml for that is blech! 3.) Custom NH code in the wiki with a discouraged note This might be a good compromise. like we do with the JBoss stuff ? I don't mind that 4.) Not at all I do not mind ;-) 5) Add the new NH to the sandbox (but not configured by default) I like it to put stuff to the sandbox first and see if the community is willing to use them something like the time will tell if its worth. Yes, my understanding is that EVERY new Tomahawk stuff goes to Sandbox first. Components AND framework features. Go ahead Ernstl -M Ciao, Mario -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: Option for NavigationHandler to support viewIds as outcome
On 10/31/06, Mario Ivankovits [EMAIL PROTECTED] wrote: Hi! 1.) Seperate NavigationHandlerImplIMHO, this is a must! I think we should *not* implement stuff whichsilently changes/enhances the behaviour - especially in myfaces-impl!!The TCK might forbid this change anyway ... 2.) Configurable Optionnot required, as everyone can configure this NH in faces-config.xml.In particular, if you decide to implement this feature, consider packaging it inside a separate JAR file with its own embedded META-INF/faces- config.xml file that defines the custom navigation handler. That way, it is self configuring -- to use the feature, just drop the JAR into your app.Craig 3.) Custom NH code in the wiki with a discouraged noteThis might be a good compromise. 4.) Not at allI do not mind ;-)5) Add the new NH to the sandbox (but not configured by default) I like it to put stuff to the sandbox first and see if the community iswilling to use them something like the time will tell if its worth.Ciao,Mario
Re: How to dynamically show different components for each row in a table
This is probably best discussed on the users list. The dev list is for discussion of new components and general project coordination. Sean On 10/31/06, kevin_zhai [EMAIL PROTECTED] wrote: My table maybe each row(column) need different UI component(radio,button,checkbox,textbox,etc), so,use rendered attribute,it's not enough, I need ,dynamically creat my table depending data type from select from database data, btw,thanks you advise -- View this message in context: http://www.nabble.com/How-to-dynamically-show-different-components-for-each-row-in-a-table-tf2545575.html#a7095132 Sent from the My Faces - Dev mailing list archive at Nabble.com.
XML-Schema for the Tags
Hello, the spec for 1.2 says, that JSF implementations that are part of a Java EE technology-compliant implementation are required to validate the application resource file against the XML schema for structural correctness. So should we use XML-Schema for the Tag*.tld as well? (html and core) If so, we have to adjust the xslt to work with XML-Schema. Also all include-entities have to be adjusted. And I think we have to rename the *.tdl to *.xsl, isn't it? cheers Andreas
Re: Option for NavigationHandler to support viewIds as outcome
2.) Configurable Option not required, as everyone can configure this NH in faces-config.xml. In particular, if you decide to implement this feature, consider packaging it inside a separate JAR file with its own embedded META-INF/faces- config.xml file that defines the custom navigation handler. That way, it is self configuring -- to use the feature, just drop the JAR into your app. You are right with that (that also what you do in Shale - Tiles for instance). Shale Tiles is different. It makes sense in that world to do that. For this NH, we should ensure to have it not that convenient to get it working. They should need to put it manually in their faces-cfg.xml, to be aware they know what they are doing. By adding random-myfaces-xxx jars you can cause confusion to the users. Adding it to the faces-cfg.xml is sorta marker interfaces pattern (sure a poor one :)) Thanks! Matt Craig 3.) Custom NH code in the wiki with a discouraged note This might be a good compromise. 4.) Not at all I do not mind ;-) 5) Add the new NH to the sandbox (but not configured by default) I like it to put stuff to the sandbox first and see if the community is willing to use them something like the time will tell if its worth. Ciao, Mario -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
[jira] Resolved: (TOBAGO-7) Add default values for calendar popup size
[ http://issues.apache.org/jira/browse/TOBAGO-7?page=all ] Bernd Bohmann resolved TOBAGO-7. Resolution: Fixed I think it is already done. Add default values for calendar popup size -- Key: TOBAGO-7 URL: http://issues.apache.org/jira/browse/TOBAGO-7 Project: MyFaces Tobago Issue Type: Bug Components: Themes Reporter: Volker Weber set default values for width and height of calendar popups in theme-config-properties -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TOBAGO-163) Calculation of component-height doesn't work correctly
[ http://issues.apache.org/jira/browse/TOBAGO-163?page=comments#action_12446079 ] Bernd Bohmann commented on TOBAGO-163: -- Can you test it with the nightly build, please. Calculation of component-height doesn't work correctly -- Key: TOBAGO-163 URL: http://issues.apache.org/jira/browse/TOBAGO-163 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.8 Environment: WinXP Tomcat 5.5.20 IE 6 Reporter: Tobias Glensk Priority: Minor I have a box component inside a panel with three nested components. The rows attribute of the box component is set to fixed. The heigt of the box component isn't calculated correctly if all nested components have the heigth attribute rows=fixed, for example: tc:panel f:facet name=layout tc:gridLayout margin=10px rows=1*;fixed;1* / /f:facet .. tc:box label=the outer box f:facet name=layout tc:gridLayout margin=10px rows=fixed;fixed;fixed / /f:facet tc:messages / tx:in label=SerachCriteria value= / tc:panel f:facet name=layout tc:gridLayout margin=10px columns=5*;1* / /f:facet tc:cell / tc:button action= label=Search defaultCommand=true / /tc:panel /tc:box .. /tc:panel These are the messages which Tobago generates: org.apache.myfaces.tobago.util.LayoutInfo:101 - There are columns left but no more space! cellsLeft=1, tokens=fixed;fixed;fixed org.apache.myfaces.tobago.util.LayoutInfo:103 - calculated spaces = 1;20;-1 The same happens if the 3rd component in the box has 1* as row-height. org.apache.myfaces.tobago.util.LayoutInfo:101 - There are columns left but no more space! cellsLeft=1, tokens=fixed;fixed;1* org.apache.myfaces.tobago.util.LayoutInfo:103 - calculated spaces = 1;20;-1 The workaround ist to set the row-height of the third component explicit, e.g. rows=fixed;fixed;20px. The type of the 3rd component is not relevant (I used tc:button instead of tc:panel to test it). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TOBAGO-164) Faces initialisation doesn't work if Tomcat installation path contains spaces
[ http://issues.apache.org/jira/browse/TOBAGO-164?page=comments#action_12446082 ] Bernd Bohmann commented on TOBAGO-164: -- Which version of myfaces core are you using? Faces initialisation doesn't work if Tomcat installation path contains spaces - Key: TOBAGO-164 URL: http://issues.apache.org/jira/browse/TOBAGO-164 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.8 Environment: WinXP Tomcat 5.5.20 Reporter: Tobias Glensk Attachments: stacktrace.txt I have installed Tomcat 5.5.20 in the directory C:\Programme\Apache Software Foundation\apache-tomcat-5.5.20 and deployed a web application. The error message I received is the following: 2006-10-26 11:27:33 http-8080-Processor24 ERROR - org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/web-app]:675 - StandardWrapper.Throwable java.lang.IllegalStateException: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; listener listener-classorg.apache.myfaces.webapp.StartupServletContextListener/listener-class /listener at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:90) at javax.faces.webapp.FacesServlet.init(FacesServlet.java:88) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:757) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:641) ... After that I installed Tomcat in a directory containing no spaces like C:\Programme\apache-tomcat-5.5.20 and deployed the same web application it works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TOBAGO-162) Date not rendered correctly without f:convertDateTime pattern=dd/MM/yyyy /
[ http://issues.apache.org/jira/browse/TOBAGO-162?page=comments#action_12446083 ] Bernd Bohmann commented on TOBAGO-162: -- ping Date not rendered correctly without f:convertDateTime pattern=dd/MM/ / Key: TOBAGO-162 URL: http://issues.apache.org/jira/browse/TOBAGO-162 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.0.9 Environment: Windows XP, GlassFish, Myfaces jsf or JSF RI 1.2 Reporter: Hari R whenever date field is retrieved from oracle database the date rendered is one day before whenever the component tc:out, tc:in tx:in is not formatted with f:convertDateTime pattern=dd/MM/ / same is the case with tc:date and tx:date. I presume the problem is conversion used in myfaces core. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TOBAGO-163) Calculation of component-height doesn't work correctly
[ http://issues.apache.org/jira/browse/TOBAGO-163?page=comments#action_12446092 ] Volker Weber commented on TOBAGO-163: - Bernd, did you change something in the calculation? I think the margin is missing on layoutcalculation in the layout manager. Assign this to me if i should take a deeper look into. Calculation of component-height doesn't work correctly -- Key: TOBAGO-163 URL: http://issues.apache.org/jira/browse/TOBAGO-163 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.8 Environment: WinXP Tomcat 5.5.20 IE 6 Reporter: Tobias Glensk Priority: Minor I have a box component inside a panel with three nested components. The rows attribute of the box component is set to fixed. The heigt of the box component isn't calculated correctly if all nested components have the heigth attribute rows=fixed, for example: tc:panel f:facet name=layout tc:gridLayout margin=10px rows=1*;fixed;1* / /f:facet .. tc:box label=the outer box f:facet name=layout tc:gridLayout margin=10px rows=fixed;fixed;fixed / /f:facet tc:messages / tx:in label=SerachCriteria value= / tc:panel f:facet name=layout tc:gridLayout margin=10px columns=5*;1* / /f:facet tc:cell / tc:button action= label=Search defaultCommand=true / /tc:panel /tc:box .. /tc:panel These are the messages which Tobago generates: org.apache.myfaces.tobago.util.LayoutInfo:101 - There are columns left but no more space! cellsLeft=1, tokens=fixed;fixed;fixed org.apache.myfaces.tobago.util.LayoutInfo:103 - calculated spaces = 1;20;-1 The same happens if the 3rd component in the box has 1* as row-height. org.apache.myfaces.tobago.util.LayoutInfo:101 - There are columns left but no more space! cellsLeft=1, tokens=fixed;fixed;1* org.apache.myfaces.tobago.util.LayoutInfo:103 - calculated spaces = 1;20;-1 The workaround ist to set the row-height of the third component explicit, e.g. rows=fixed;fixed;20px. The type of the 3rd component is not relevant (I used tc:button instead of tc:panel to test it). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Tomcat SNAPSHOT is missing, 1.2 impl cannot be built
mmm, I guess, because it is the (Apache) tomcat ? no idea. Jetty is fine with me too. -M On 10/31/06, Dennis Byrne [EMAIL PROTECTED] wrote: Looks like the 1.2 branch [2] does not work on a fresh co because the tomcat jars have been removed from the apache repo [1]. Does anyone know where they have gone to? I seem to remember the Mortbay jars working quite well for us. Is there any reason this was changed? Dennis Byrne [1] http://people.apache.org/repo/m2-snapshot-repository/org/apache/ [2] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.tomcat:jasper-el:jar:6.0.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=jasper-e l \ -Dversion=6.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.myfaces.core:myfaces-api:jar:1.2.0-SNAPSHOT 2) org.apache.tomcat:jasper-el:jar:6.0.0-SNAPSHOT 2) org.apache.tomcat:el-api:jar:6.0.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=el-api \ -Dversion=6.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.myfaces.core:myfaces-api:jar:1.2.0-SNAPSHOT 2) org.apache.tomcat:el-api:jar:6.0.0-SNAPSHOT -- 2 required artifacts are missing. for artifact: org.apache.myfaces.core:myfaces-api:jar:1.2.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (https://maven-repository.dev.java.net/nonav/repository), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), myfaces-repo (http://myfaces.zones.apache.org/dist/maven-repository) -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: Tomcat SNAPSHOT is missing, 1.2 impl cannot be built
On 10/31/06, Dennis Byrne [EMAIL PROTECTED] wrote: Looks like the 1.2 branch [2] does not work on a fresh co because the tomcat jars have been removed from the apache repo [1]. Does anyone know where they have gone to? I seem to remember the Mortbay jars working quite well for us. Is there any reason this was changed? Sorry, I didn't see this over here; we've been discussing it on [EMAIL PROTECTED] This is more fallout from the death of minotaur (people.apache.org) during the infrastructure move. The EL jars were lost when it was restored from an old backup. I'll deploy new 6.0.1-SNAPSHOT jars tonight. -- Wendy
Re: Tomcat SNAPSHOT is missing, 1.2 impl cannot be built
On 10/31/06, Dennis Byrne [EMAIL PROTECTED] wrote: Looks like the 1.2 branch [2] does not work on a fresh co because the tomcat jars have been removed from the apache repo [1].Does anyone know where they have gone to?I seem to remember the Mortbay jars working quite well for us.Is there any reason this was changed? Dennis Byrne[1] http://people.apache.org/repo/m2-snapshot-repository/org/apache/[2][INFO] [ERROR] BUILD ERROR[INFO] [INFO] Failed to resolve artifact.Missing:--1) org.apache.tomcat:jasper-el:jar:6.0.0-SNAPSHOT Didn't Tomcat 6.0 just go final? If so, it'd probably be worth updating to the final version number.Craig Try downloading the file manually from the project website.Then, install it using the command:mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=jasper-el \-Dversion= 6.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/filePath to dependency:1) org.apache.myfaces.core:myfaces-api:jar:1.2.0-SNAPSHOT2) org.apache.tomcat:jasper-el:jar:6.0.0-SNAPSHOT2) org.apache.tomcat:el-api:jar:6.0.0-SNAPSHOTTry downloading the file manually from the project website.Then, install it using the command:mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=el-api \ -Dversion=6.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/filePath to dependency:1) org.apache.myfaces.core:myfaces-api:jar:1.2.0-SNAPSHOT2) org.apache.tomcat:el-api:jar:6.0.0-SNAPSHOT --2 required artifacts are missing.for artifact:org.apache.myfaces.core:myfaces-api:jar:1.2.0-SNAPSHOTfrom the specified remote repositories:central ( http://repo1.maven.org/maven2),java.net (https://maven-repository.dev.java.net/nonav/repository),apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),myfaces-repo (http://myfaces.zones.apache.org/dist/maven-repository )
Re: Tomcat SNAPSHOT is missing, 1.2 impl cannot be built
On 10/31/06, Craig McClanahan [EMAIL PROTECTED] wrote: Didn't Tomcat 6.0 just go final? If so, it'd probably be worth updating to the final version number. Not yet... 6.0.0 exists, but the only vote I've seen was on the release plan. I'm working with them to get Tomcat 6 into the central Maven repo when it's time. -- Wendy
Re: Tomcat SNAPSHOT is missing, 1.2 impl cannot be built
thanks! weren't they available? or was it just a *temp* thing ? On 10/31/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 10/31/06, Craig McClanahan [EMAIL PROTECTED] wrote: Didn't Tomcat 6.0 just go final? If so, it'd probably be worth updating to the final version number. Not yet... 6.0.0 exists, but the only vote I've seen was on the release plan. I'm working with them to get Tomcat 6 into the central Maven repo when it's time. -- Wendy -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: Tomcat SNAPSHOT is missing, 1.2 impl cannot be built
It's not official...http://tomcat.apache.org/download-60.cgiOn 10/31/06, Wendy Smoak [EMAIL PROTECTED] wrote:On 10/31/06, Craig McClanahan [EMAIL PROTECTED] wrote: Didn't Tomcat 6.0 just go final?If so, it'd probably be worth updating to the final version number.Not yet... 6.0.0 exists, but the only vote I've seen was on the release plan.I'm working with them to get Tomcat 6 into the centralMaven repo when it's time.--Wendy
[jira] Commented: (TOBAGO-163) Calculation of component-height doesn't work correctly
[ http://issues.apache.org/jira/browse/TOBAGO-163?page=comments#action_12446110 ] Bernd Bohmann commented on TOBAGO-163: -- I have added the example code to http://svn.apache.org/repos/asf/myfaces/tobago/trunk/example/test/src/main/webapp/layout.jsp I did not get any warning from the LayoutInfo. Calculation of component-height doesn't work correctly -- Key: TOBAGO-163 URL: http://issues.apache.org/jira/browse/TOBAGO-163 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.8 Environment: WinXP Tomcat 5.5.20 IE 6 Reporter: Tobias Glensk Priority: Minor I have a box component inside a panel with three nested components. The rows attribute of the box component is set to fixed. The heigt of the box component isn't calculated correctly if all nested components have the heigth attribute rows=fixed, for example: tc:panel f:facet name=layout tc:gridLayout margin=10px rows=1*;fixed;1* / /f:facet .. tc:box label=the outer box f:facet name=layout tc:gridLayout margin=10px rows=fixed;fixed;fixed / /f:facet tc:messages / tx:in label=SerachCriteria value= / tc:panel f:facet name=layout tc:gridLayout margin=10px columns=5*;1* / /f:facet tc:cell / tc:button action= label=Search defaultCommand=true / /tc:panel /tc:box .. /tc:panel These are the messages which Tobago generates: org.apache.myfaces.tobago.util.LayoutInfo:101 - There are columns left but no more space! cellsLeft=1, tokens=fixed;fixed;fixed org.apache.myfaces.tobago.util.LayoutInfo:103 - calculated spaces = 1;20;-1 The same happens if the 3rd component in the box has 1* as row-height. org.apache.myfaces.tobago.util.LayoutInfo:101 - There are columns left but no more space! cellsLeft=1, tokens=fixed;fixed;1* org.apache.myfaces.tobago.util.LayoutInfo:103 - calculated spaces = 1;20;-1 The workaround ist to set the row-height of the third component explicit, e.g. rows=fixed;fixed;20px. The type of the 3rd component is not relevant (I used tc:button instead of tc:panel to test it). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Tomcat SNAPSHOT is missing, 1.2 impl cannot be built
Remy,I was just answering Craig's question. Alpha != Final.Cheers,Z.On 10/31/06, Remy Maucherat [EMAIL PROTECTED] wrote:Zubin Wadia wrote: It's not official... http://tomcat.apache.org/download-60.cgiIt's official, but it's an alpha release, which to me is a lot betterthan a random build (it has a svn tag, for starters). At the moment, I am doing some Jasper changes, so it's not a good idea to use a snapshotanyway.Rémy
development attribute in dojoInitializer
development attribute in dojoInitializer, is in DojoInitializerTag.java but it is not in TLD class, half documented in xdoc web site.is it removed or what?Arash Rajaeeyan
Re: XML-Schema for the Tags
Yes, we will use the schemas. I have been lately working in the maven-faces-plugin that will allow us to autogenerate the component/tags/tlds/config files from a set of XMLs describing the components etc, the way Trinidad is doing it's build. So the xslt transformation would not be needed anymore after we rewrite the XMLs. Right at this moment, the generation of components for myfaces works and I am dealing with the tag generation (I guess tomorrow I will have it). Then we can start testing and writing the XMLs. You can check the XML in the trinidad-build module of the trinidad project [2] to see how the XMLs will look like. The maven-faces-plugin is awesome and will help to ease the burden of create and maintain the jsf components... cheers, Bruno [1] http://svn.apache.org/repos/asf/incubator/adffaces/branches/myfaces-1_2-maven-faces-plugin [2] http://svn.apache.org/repos/asf/incubator/adffaces/branches/faces-1_2/trinidad/trinidad-build On 10/31/06, Andreas Berger [EMAIL PROTECTED] wrote: Hello, the spec for 1.2 says, that JSF implementations that are part of a Java EE technology-compliant implementation are required to validate the application resource file against the XML schema for structural correctness. So should we use XML-Schema for the Tag*.tld as well? (html and core) If so, we have to adjust the xslt to work with XML-Schema. Also all include-entities have to be adjusted. And I think we have to rename the *.tdl to *.xsl, isn't it? cheers Andreas
Re: Tomcat SNAPSHOT is missing, 1.2 impl cannot be built
On 10/31/06, Wendy Smoak [EMAIL PROTECTED] wrote: I'll deploy new 6.0.1-SNAPSHOT jars tonight. This is done, and the poms for the 1.2 branch have been updated. It builds for me after downloading the snapshots, please let me know if you have any trouble. -- Wendy
