[jira] [Created] (TRINIDAD-2095) Mojara and PWC4011: Unable to set request character encoding to UTF-8
Mojara and PWC4011: Unable to set request character encoding to UTF-8 - Key: TRINIDAD-2095 URL: https://issues.apache.org/jira/browse/TRINIDAD-2095 Project: MyFaces Trinidad Issue Type: Bug Components: Archetype Affects Versions: 1.2.14-core Reporter: Tomas Havelka The problem with annoying warning message with Mojarra and Glassfish still remains. Within each request TrinidadFilterImpl creates the ServletExternalContext multiple times which causes Mojarra to log this message PWC4011: Unable to set request character encoding to UTF-8 many many times (cca 4x per request). This causes the log file is getting large unreasonably. The problem is descibed in this thread http://www.mail-archive.com/dev@myfaces.apache.org/msg37786.html. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TOBAGO-995) TextArea applies always style class tobago-TextArea-required
TextArea applies always style class tobago-TextArea-required Key: TOBAGO-995 URL: https://issues.apache.org/jira/browse/TOBAGO-995 Project: MyFaces Tobago Issue Type: Bug Components: Themes Environment: All Reporter: Helmut Swaczinna Priority: Minor After clicking in an empty tc:textarea the style class tobago-TextArea-required is applied to this component, but attribute required is set to false. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TOBAGO-995) TextArea applies always style class tobago-TextArea-required
[ https://issues.apache.org/jira/browse/TOBAGO-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Helmut Swaczinna updated TOBAGO-995: Status: Patch Available (was: Open) TextArea applies always style class tobago-TextArea-required Key: TOBAGO-995 URL: https://issues.apache.org/jira/browse/TOBAGO-995 Project: MyFaces Tobago Issue Type: Bug Components: Themes Environment: All Reporter: Helmut Swaczinna Priority: Minor After clicking in an empty tc:textarea the style class tobago-TextArea-required is applied to this component, but attribute required is set to false. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-995) TextArea applies always style class tobago-TextArea-required
[
https://issues.apache.org/jira/browse/TOBAGO-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027628#comment-13027628
]
Helmut Swaczinna commented on TOBAGO-995:
-
The bug is in TextAreaRenderer encodeEnd(). This is the fix:
if (required || maxLength 0) {
String rendererName = HtmlRendererUtil.getRendererName(facesContext,
input);
final String[] cmds = {
new Tobago.In(\ + input.getClientId(facesContext) + \, +
required + ,\
+ StyleClasses.PREFIX + rendererName + \ + (maxLength
-1? , + maxLength: ) + );
};
HtmlRendererUtil.writeScriptLoader(facesContext, null, cmds);
}
TextArea applies always style class tobago-TextArea-required
Key: TOBAGO-995
URL: https://issues.apache.org/jira/browse/TOBAGO-995
Project: MyFaces Tobago
Issue Type: Bug
Components: Themes
Environment: All
Reporter: Helmut Swaczinna
Priority: Minor
After clicking in an empty tc:textarea the style class
tobago-TextArea-required is applied to this component, but attribute required
is set to false.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TOMAHAWK-1574) t:inputCalendar is not triggering f:ajax
[ https://issues.apache.org/jira/browse/TOMAHAWK-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved TOMAHAWK-1574. -- Resolution: Fixed Fix Version/s: 1.1.11-SNAPSHOT Assignee: Leonardo Uribe t:inputCalendar is not triggering f:ajax Key: TOMAHAWK-1574 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1574 Project: MyFaces Tomahawk Issue Type: Bug Components: AJAX Form Components, Calendar Affects Versions: 1.1.11-SNAPSHOT Environment: Win XP, JDK 1.6.0.20, Tomcat 6.0.29, MyFaces 2.0.5 - Snapshots (api + impl at revision 1085804), Tomahawk20-1.1.11 Snapshot (at revision 1084269) Reporter: Oliver Bayer Assignee: Leonardo Uribe Fix For: 1.1.11-SNAPSHOT I've had this problem some time ago (see TOMAHAWK-1515) but after the bugfixes it worked. After the upgrade to the current snapshots (see environment description) it's not working anymore (therefore I've created this new ticket). Testcase: User fills in birthday, the ajax event valueChange gets triggered and returns the calulated age. Test scenarios: 1) using two h:inputText for inputting the birthday and outputting the age --- works 2) using two t:inputText for inputting the birthday and outputting the age --- works too 3) using t:inputCalendar and t:inputText --- doesn't work If I'm debugging the setBirthday method the jvm stopps at the breakpoint in case of scenario 1) and 2) but the setter isn't called in case 3) at all. Looking at the HTTP post data send in case 3): - the birthday field contains the date selected by the t:inputCalender popup - event: valueChange - partial ajax: true - id of the triggering element: seems correct - id of the element to render: seems correct HTH Oli -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOMAHAWK-1574) t:inputCalendar is not triggering f:ajax
[ https://issues.apache.org/jira/browse/TOMAHAWK-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027647#comment-13027647 ] Leonardo Uribe commented on TOMAHAWK-1574: -- Hi Oliver Sorry for the late response. Yes, you're right, I fixed the first one and for the second one the solution was add a property to inputTextHelp to override the targetClientId used for render client behaviors, so javax.faces.partial.execute could be set to inputCalendar clientId. Thanks a lot for you help debugging this issue and your interest on it. It is a valuable contribution. I'll close this issue as fixed. t:inputCalendar is not triggering f:ajax Key: TOMAHAWK-1574 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1574 Project: MyFaces Tomahawk Issue Type: Bug Components: AJAX Form Components, Calendar Affects Versions: 1.1.11-SNAPSHOT Environment: Win XP, JDK 1.6.0.20, Tomcat 6.0.29, MyFaces 2.0.5 - Snapshots (api + impl at revision 1085804), Tomahawk20-1.1.11 Snapshot (at revision 1084269) Reporter: Oliver Bayer Fix For: 1.1.11-SNAPSHOT I've had this problem some time ago (see TOMAHAWK-1515) but after the bugfixes it worked. After the upgrade to the current snapshots (see environment description) it's not working anymore (therefore I've created this new ticket). Testcase: User fills in birthday, the ajax event valueChange gets triggered and returns the calulated age. Test scenarios: 1) using two h:inputText for inputting the birthday and outputting the age --- works 2) using two t:inputText for inputting the birthday and outputting the age --- works too 3) using t:inputCalendar and t:inputText --- doesn't work If I'm debugging the setBirthday method the jvm stopps at the breakpoint in case of scenario 1) and 2) but the setter isn't called in case 3) at all. Looking at the HTTP post data send in case 3): - the birthday field contains the date selected by the t:inputCalender popup - event: valueChange - partial ajax: true - id of the triggering element: seems correct - id of the element to render: seems correct HTH Oli -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MYFACES-3122) Create xsd schemas for .view.xml pages
Create xsd schemas for .view.xml pages -- Key: MYFACES-3122 URL: https://issues.apache.org/jira/browse/MYFACES-3122 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.1.0-SNAPSHOT Reporter: Leonardo Uribe Assignee: Leonardo Uribe With the introduction of JSF 2.1 .view.xml extension, it is necessary to put proper schemas on META-INF/schema path, so users can just take and use them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MYFACES-3122) Create xsd schemas for .view.xml pages
[ https://issues.apache.org/jira/browse/MYFACES-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-3122. - Resolution: Fixed Fix Version/s: 2.1.0 Create xsd schemas for .view.xml pages -- Key: MYFACES-3122 URL: https://issues.apache.org/jira/browse/MYFACES-3122 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.1.0-SNAPSHOT Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 2.1.0 With the introduction of JSF 2.1 .view.xml extension, it is necessary to put proper schemas on META-INF/schema path, so users can just take and use them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MYFACES-3091) Implement UIComponent.ATTRS_WITH_DECLARED_DEFAULT_VALUES behavior
[ https://issues.apache.org/jira/browse/MYFACES-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-3091. - Resolution: Fixed Assignee: Leonardo Uribe Implement UIComponent.ATTRS_WITH_DECLARED_DEFAULT_VALUES behavior - Key: MYFACES-3091 URL: https://issues.apache.org/jira/browse/MYFACES-3091 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.1.0-SNAPSHOT Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 2.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MYFACES-3093) Check FacesServlet description for support servlet 3.0 spec
[ https://issues.apache.org/jira/browse/MYFACES-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-3093. - Resolution: Fixed Assignee: Leonardo Uribe I checked and corrected the required stuff to comply with FacesServlet description on the javadoc. To do that, I had to create a new module called shaded-impl and take myfaces core impl 2.0.5 jar and uncompress the sources, to allow use myfaces impl SPI API in implee6 module. In the future this hack will be removed. Check FacesServlet description for support servlet 3.0 spec Key: MYFACES-3093 URL: https://issues.apache.org/jira/browse/MYFACES-3093 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.1.0-SNAPSHOT Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 2.1.0 The description says this: .. If the application is running in a Servlet 3.0 (and beyond) container, the runtime must provide an implementation of the ServletContainerInitializer interface that declares the following classes in its javax.servlet.annotation.HandlesTypes annotation. * ResourceDependencies * ResourceDependency * javax.faces.bean.ManagedBean * FacesComponent * UIComponent * Converter * FacesConverter * ListenerFor * ListenersFor * FacesBehaviorRenderer * Renderer * FacesValidator * Validator This servlet must automatically be mapped if it is not explicitly mapped in web.xml or web-fragment.xml and one or more of the following conditions are true. * A faces-config.xml file is found in WEB-INF * A faces-config.xml file is found in the META-INF directory of a jar in the application's classpath. * A filename ending in .faces-config.xml is found in the META-INF directory of a jar in the application's classpath. * The javax.faces.CONFIG_FILES context param is declared in web.xml or web-fragment.xml. * The Set of classes passed to the onStartup() method of the ServletContainerInitializer implementation is not empty. If the runtime determines that the servlet must be automatically mapped, it must be mapped to the following url-pattern entries. * /faces * *.jsf * *.faces ... In theory, MyFaces has already that class (MyFacesContainerInitializer on implee6), but we need to check if it complies with the spec. Note the part that says UIComponent and Renderer classes should be added as HandlesTypes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Myfaces 2.1.x now is trunk
Hi I have changed the links on current20, current21 and relocated the branches for core 2.1.x and shared 4.1.x, so now these projects are now on trunk, as proposed previously. JSF 2.0 related links are: https://svn.apache.org/repos/asf/myfaces/core/branches/2.0.x/ https://svn.apache.org/repos/asf/myfaces/shared/trunk_4.0.x/ regards, Leonardo Uribe
[jira] [Updated] (TOMAHAWK-1578) Quotes are not escaped in TableAutoSuggest in ajax requests
[ https://issues.apache.org/jira/browse/TOMAHAWK-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe updated TOMAHAWK-1578: - Resolution: Fixed Fix Version/s: 1.1.11-SNAPSHOT Assignee: Leonardo Uribe Status: Resolved (was: Patch Available) Thanks to Marcus Büttner for provide this patch Quotes are not escaped in TableAutoSuggest in ajax requests --- Key: TOMAHAWK-1578 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1578 Project: MyFaces Tomahawk Issue Type: Bug Reporter: Marcus Büttner Assignee: Leonardo Uribe Fix For: 1.1.11-SNAPSHOT Attachments: TOMAHAWK-1578.patch TableSuggestAjaxRenderer doesn't escape quotes if it's rendering ajax response. I add a patch which should resolve this problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3101) NavigationHandlerImpl throws NullpointerException if view is expired
[ https://issues.apache.org/jira/browse/MYFACES-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027692#comment-13027692 ] alex musort commented on MYFACES-3101: -- Hello... I'm new using this technology and it's nice to see the problem I'm facing is solved. Could anyone tell me where can I get the jars files with the solution implemented?? thx NavigationHandlerImpl throws NullpointerException if view is expired Key: MYFACES-3101 URL: https://issues.apache.org/jira/browse/MYFACES-3101 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.4 Reporter: Martin Stockhammer Fix For: 2.0.6-SNAPSHOT Attachments: MYFACES-3101-v2.patch, MYFACES-3101.patch I tried to use the NavigationHandler inside a Faces exception handler to deal with ViewExpiredException as mentioned here: http://www.nfjsone.com/blog/ed_burns/2009/09/dealing_gracefully_with_viewexpiredexception_in_jsf2. The example does not work with myfaces, because org.apache.myfaces.application.NavigationHandlerImpl throws a NullpointerException while handleNavigation() is called. The exception occurs in line 160: String viewId = facesContext.getViewRoot().getViewId(); I think the cause is that the viewroot is not set anymore when the ViewExpiredException is thrown. The official API for NavigationHandler.handleNavigation tells, that the NullpointerException is thrown only if the given facescontext is null. NullPointerException - if context is null -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TOMAHAWK-1479) CLONE -t:inputCalendar displays year 1900 when an incorrect date is entered
[ https://issues.apache.org/jira/browse/TOMAHAWK-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe updated TOMAHAWK-1479: - Resolution: Fixed Fix Version/s: 1.1.11-SNAPSHOT Status: Resolved (was: Patch Available) Thanks to Pavel Blinov for provide this patch. CLONE -t:inputCalendar displays year 1900 when an incorrect date is entered --- Key: TOMAHAWK-1479 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1479 Project: MyFaces Tomahawk Issue Type: Bug Components: Calendar Affects Versions: 1.1.9 Reporter: Pavel Blinov Assignee: Leonardo Uribe Priority: Minor Fix For: 1.1.11-SNAPSHOT Attachments: TOMAHAWK-1479.patch, calendar.jpg When the user provides an incorrect date value (e.g. 12 when the popupDateFormat is dd/MM/) the popup will display year 1900 instead of the current year. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TOMAHAWK-1581) selectText() javascript function not found
selectText() javascript function not found -- Key: TOMAHAWK-1581 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1581 Project: MyFaces Tomahawk Issue Type: Bug Components: Calendar Affects Versions: 1.1.10 Reporter: Leonardo Uribe Assignee: Leonardo Uribe selectText() function from inputTextHelp component is not found, because the resource is not added to the view. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TOMAHAWK-1581) selectText() javascript function not found
[ https://issues.apache.org/jira/browse/TOMAHAWK-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved TOMAHAWK-1581. -- Resolution: Fixed Fix Version/s: 1.1.11-SNAPSHOT selectText() javascript function not found -- Key: TOMAHAWK-1581 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1581 Project: MyFaces Tomahawk Issue Type: Bug Components: Calendar Affects Versions: 1.1.10 Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 1.1.11-SNAPSHOT selectText() function from inputTextHelp component is not found, because the resource is not added to the view. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Myfaces 2.1.x now is trunk
Thanks Leonardo, I hope we can start with 2.2 soon :-) Regards Bernd On Mon, May 2, 2011 at 4:25 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi I have changed the links on current20, current21 and relocated the branches for core 2.1.x and shared 4.1.x, so now these projects are now on trunk, as proposed previously. JSF 2.0 related links are: https://svn.apache.org/repos/asf/myfaces/core/branches/2.0.x/ https://svn.apache.org/repos/asf/myfaces/shared/trunk_4.0.x/ regards, Leonardo Uribe
[jira] [Commented] (MYFACES-3101) NavigationHandlerImpl throws NullpointerException if view is expired
[ https://issues.apache.org/jira/browse/MYFACES-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027737#comment-13027737 ] Jakob Korherr commented on MYFACES-3101: Hi, Because there was no release since the patch was committed, you will have to use 2.0.6-SNAPSHOT. You can get it from our snapshots repo (see [1]) our by checking out current20 (see [2]) using svn checkout and building it yourself using maven! [1] https://repository.apache.org/content/groups/snapshots/org/apache/myfaces/core/ [2] https://svn.apache.org/repos/asf/myfaces/current20/ NavigationHandlerImpl throws NullpointerException if view is expired Key: MYFACES-3101 URL: https://issues.apache.org/jira/browse/MYFACES-3101 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.4 Reporter: Martin Stockhammer Fix For: 2.0.6-SNAPSHOT Attachments: MYFACES-3101-v2.patch, MYFACES-3101.patch I tried to use the NavigationHandler inside a Faces exception handler to deal with ViewExpiredException as mentioned here: http://www.nfjsone.com/blog/ed_burns/2009/09/dealing_gracefully_with_viewexpiredexception_in_jsf2. The example does not work with myfaces, because org.apache.myfaces.application.NavigationHandlerImpl throws a NullpointerException while handleNavigation() is called. The exception occurs in line 160: String viewId = facesContext.getViewRoot().getViewId(); I think the cause is that the viewroot is not set anymore when the ViewExpiredException is thrown. The official API for NavigationHandler.handleNavigation tells, that the NullpointerException is thrown only if the given facescontext is null. NullPointerException - if context is null -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3093) Check FacesServlet description for support servlet 3.0 spec
[ https://issues.apache.org/jira/browse/MYFACES-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027741#comment-13027741 ] Jakob Korherr commented on MYFACES-3093: I think a better idea than the myfaces-shaded-impl hack would be to create a myfaces-spi module, which contains MyFaces' SPI classes (of course, only the abstract ones, not the implementation classes) and which will be shaded into myfaces-impl at build time. In this way myfaces-implee6 could use the myfaces-spi module and the myfaces-shaded-impl module could be removed. What do you think of that solution, Leo? Check FacesServlet description for support servlet 3.0 spec Key: MYFACES-3093 URL: https://issues.apache.org/jira/browse/MYFACES-3093 Project: MyFaces Core Issue Type: Task Components: JSR-314 Affects Versions: 2.1.0-SNAPSHOT Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 2.1.0 The description says this: .. If the application is running in a Servlet 3.0 (and beyond) container, the runtime must provide an implementation of the ServletContainerInitializer interface that declares the following classes in its javax.servlet.annotation.HandlesTypes annotation. * ResourceDependencies * ResourceDependency * javax.faces.bean.ManagedBean * FacesComponent * UIComponent * Converter * FacesConverter * ListenerFor * ListenersFor * FacesBehaviorRenderer * Renderer * FacesValidator * Validator This servlet must automatically be mapped if it is not explicitly mapped in web.xml or web-fragment.xml and one or more of the following conditions are true. * A faces-config.xml file is found in WEB-INF * A faces-config.xml file is found in the META-INF directory of a jar in the application's classpath. * A filename ending in .faces-config.xml is found in the META-INF directory of a jar in the application's classpath. * The javax.faces.CONFIG_FILES context param is declared in web.xml or web-fragment.xml. * The Set of classes passed to the onStartup() method of the ServletContainerInitializer implementation is not empty. If the runtime determines that the servlet must be automatically mapped, it must be mapped to the following url-pattern entries. * /faces * *.jsf * *.faces ... In theory, MyFaces has already that class (MyFacesContainerInitializer on implee6), but we need to check if it complies with the spec. Note the part that says UIComponent and Renderer classes should be added as HandlesTypes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Myfaces 2.1.x now is trunk
Thanks Leo, that's great news! I just created a blog post for it [1]. Regards, Jakob [1] http://www.jakobk.com/2011/05/myfaces-2-1-is-now-trunk/ 2011/5/2 Bernd Bohmann bernd.bohm...@atanion.com: Thanks Leonardo, I hope we can start with 2.2 soon :-) Regards Bernd On Mon, May 2, 2011 at 4:25 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi I have changed the links on current20, current21 and relocated the branches for core 2.1.x and shared 4.1.x, so now these projects are now on trunk, as proposed previously. JSF 2.0 related links are: https://svn.apache.org/repos/asf/myfaces/core/branches/2.0.x/ https://svn.apache.org/repos/asf/myfaces/shared/trunk_4.0.x/ regards, Leonardo Uribe -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
Re: [RESULTS] Release of Trinidad 2.0.0
Any news about the release? Any date? Thanks, Glauco P. Gomes Em 18-04-2011 16:38, Scott O'Bryan escreveu: Thanks to everyone who voted. The vote to release of Trinidad 2.0.0 passed [1] with the following results: +1 (5): Matt Cooper, Werner Punz, Bruno Aranda, Andrew Robinson, Scott O'Bryan And no +0 or -1 votes. Thanks, Scott O'Bryan [1] http://mail-archives.apache.org/mod_mbox/myfaces-dev/201104.mbox/%3c4da77e81.6030...@gmail.com%3E
[jira] [Resolved] (TOMAHAWK-1557) InputDate calendar popup does not render correctly on IE7
[
https://issues.apache.org/jira/browse/TOMAHAWK-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved TOMAHAWK-1557.
--
Resolution: Fixed
Fix Version/s: 1.1.11-SNAPSHOT
Assignee: Leonardo Uribe
I think in this part it is better to replace the code with Element.setStyle()
method of prototype. This one do what the proposal says internally, and has
another fix of opacity property.
InputDate calendar popup does not render correctly on IE7
-
Key: TOMAHAWK-1557
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1557
Project: MyFaces Tomahawk
Issue Type: Bug
Components: Calendar
Environment: Using Tomahawk 1.2 Jar file tomahawk12-1.1.9.jar
Browser is IE7 on Windows XP
Reporter: Frank Davis
Assignee: Leonardo Uribe
Fix For: 1.1.11-SNAPSHOT
Popup calendar does not render correctly on IE7 but renders OK of FF. In IE7
the popup takes the full width of the browser screen.
Following tag used to generate the popup
t:inputDate id=#{id} value=#{value}
renderAsPopup=#{true} popupButtonImageUrl=images/icon_date.gif
popupDateFormat=dd/MM/
renderPopupButtonAsImage=true
popupCalendar=#{true} converterMessage=#{id}
is in wrong format/
Issue appears to be a feature of IE7 where the setAttribute method in
javascript does not work correctly. In the javascript used to generate the
popup the width is set in the javascript
org_apache_myfaces_PopupCalendar.prototype.init as follows
mainTable.setAttribute(cssText, width: + ((this.initData.showWeekNumber
== 1)?250:220) + px;);
This does not appear to set the width correctly. The recommended workaround
(which works for both IE7 and FF) is to set the cssText directly as follows:
mainTable.style.cssText = width: + ((this.initData.showWeekNumber
== 1)?250:220) + px;;
I have tested this on both IE7 and FF and it seems to work OK.
There are a number of other places in the javascript where the setAttribute
is used to set the width and other style attributes - I assume these have the
same problem - I have changed these and the popup appears to work OK
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [RESULTS] Release of Trinidad 2.0.0
Argh.. :) Yes, the release is basically done but I was going to get the site updated before making the announcement and trying to fix an issue with the tag doc. :) Thanks for reminding me. :) You should be able to find the maven artifacts though and the release artifacts should be available at http://www.apache.org/dyn/closer.cgi/myfaces/binaries/trinidad-2.0.0-dist.tar.gz. I'll get the website updated tonight and get out the release email. Thanks Glauco.. On 05/02/2011 12:18 PM, Glauco P. Gomes wrote: Any news about the release? Any date? Thanks, Glauco P. Gomes Em 18-04-2011 16:38, Scott O'Bryan escreveu: Thanks to everyone who voted. The vote to release of Trinidad 2.0.0 passed [1] with the following results: +1 (5): Matt Cooper, Werner Punz, Bruno Aranda, Andrew Robinson, Scott O'Bryan And no +0 or -1 votes. Thanks, Scott O'Bryan [1] http://mail-archives.apache.org/mod_mbox/myfaces-dev/201104.mbox/%3c4da77e81.6030...@gmail.com%3E
[jira] [Resolved] (TOMAHAWK-1480) Calendar shows wrong year in Opera
[ https://issues.apache.org/jira/browse/TOMAHAWK-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved TOMAHAWK-1480. -- Resolution: Fixed Fix Version/s: 1.1.11-SNAPSHOT Assignee: Leonardo Uribe I tested it with opera 10.10 and it is present. In opera 11 the problem is not present anymore. The solution is use getFullYear() instead and comment the code that adds 1900 to the year. This function is supported by all major browsers and by IE since 5.5 (ECMAScript 3). Anyway thanks for the patch. Calendar shows wrong year in Opera -- Key: TOMAHAWK-1480 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1480 Project: MyFaces Tomahawk Issue Type: Bug Components: Calendar Environment: Opera 10.10 Reporter: Guilherme Garnier Assignee: Leonardo Uribe Priority: Minor Fix For: 1.1.11-SNAPSHOT Attachments: popcalendar.js.diff When using Opera, the calendar opens in the wrong year (current year + 1900), although it´s correctly displayed in the calendar footer. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOMAHAWK-1574) t:inputCalendar is not triggering f:ajax
[ https://issues.apache.org/jira/browse/TOMAHAWK-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027852#comment-13027852 ] Oliver Bayer commented on TOMAHAWK-1574: Hi Leonardo, just FYI the forceId-attribute I've copy and paste from the examples without knowing the internal details on how this would affect the ajax handling. With an older snapshot -if I remember right 2.0.3- it has been working even with this attribute. But now with your latest calendar commits and without forceId it's working as expected. Thanks for the bugfixes :). t:inputCalendar is not triggering f:ajax Key: TOMAHAWK-1574 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1574 Project: MyFaces Tomahawk Issue Type: Bug Components: AJAX Form Components, Calendar Affects Versions: 1.1.11-SNAPSHOT Environment: Win XP, JDK 1.6.0.20, Tomcat 6.0.29, MyFaces 2.0.5 - Snapshots (api + impl at revision 1085804), Tomahawk20-1.1.11 Snapshot (at revision 1084269) Reporter: Oliver Bayer Assignee: Leonardo Uribe Fix For: 1.1.11-SNAPSHOT I've had this problem some time ago (see TOMAHAWK-1515) but after the bugfixes it worked. After the upgrade to the current snapshots (see environment description) it's not working anymore (therefore I've created this new ticket). Testcase: User fills in birthday, the ajax event valueChange gets triggered and returns the calulated age. Test scenarios: 1) using two h:inputText for inputting the birthday and outputting the age --- works 2) using two t:inputText for inputting the birthday and outputting the age --- works too 3) using t:inputCalendar and t:inputText --- doesn't work If I'm debugging the setBirthday method the jvm stopps at the breakpoint in case of scenario 1) and 2) but the setter isn't called in case 3) at all. Looking at the HTTP post data send in case 3): - the birthday field contains the date selected by the t:inputCalender popup - event: valueChange - partial ajax: true - id of the triggering element: seems correct - id of the element to render: seems correct HTH Oli -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TRINIDAD-2096) Change when the UIXCollection adds its component context change
[ https://issues.apache.org/jira/browse/TRINIDAD-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Robinson resolved TRINIDAD-2096. --- Resolution: Fixed Fix Version/s: 2.0.1 Change when the UIXCollection adds its component context change --- Key: TRINIDAD-2096 URL: https://issues.apache.org/jira/browse/TRINIDAD-2096 Project: MyFaces Trinidad Issue Type: Improvement Components: Components Affects Versions: 2.0.0-beta-1 Reporter: Andrew Robinson Assignee: Andrew Robinson Fix For: 2.0.1 During my initial authoring of the UIXCollection component context change, it was possible for code that did not reset the row key back to its original value, to leave a context change dangling off of the stack. This causes issue with other components that use context changes. I am changing the code to only use the component context change when the component is being processed. This way it is sure to be cleaned up as a try/finally block would be feasible. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TRINIDAD-2096) Change when the UIXCollection adds its component context change
Change when the UIXCollection adds its component context change --- Key: TRINIDAD-2096 URL: https://issues.apache.org/jira/browse/TRINIDAD-2096 Project: MyFaces Trinidad Issue Type: Improvement Components: Components Affects Versions: 2.0.0-beta-1 Reporter: Andrew Robinson Assignee: Andrew Robinson During my initial authoring of the UIXCollection component context change, it was possible for code that did not reset the row key back to its original value, to leave a context change dangling off of the stack. This causes issue with other components that use context changes. I am changing the code to only use the component context change when the component is being processed. This way it is sure to be cleaned up as a try/finally block would be feasible. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TOMAHAWK-1359) activeOnViewIds toggleActive does not work properly
[ https://issues.apache.org/jira/browse/TOMAHAWK-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved TOMAHAWK-1359. -- Resolution: Fixed Fix Version/s: 1.1.11-SNAPSHOT Assignee: Leonardo Uribe Fixed documentation that says semicolon instead comma. Thanks for point the bug on the documentation. activeOnViewIds toggleActive does not work properly --- Key: TOMAHAWK-1359 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1359 Project: MyFaces Tomahawk Issue Type: Bug Components: Panel Navigation2 Reporter: Markus Alvermann Assignee: Leonardo Uribe Fix For: 1.1.11-SNAPSHOT We are using commandNavigation2 with the proprety activeOnViewIds to prevent the menu from collapsing if we use a button to navigate on the next side (instead of the panelNavigation2). Unfortunately the property only works if you enter exactly on jsp. If you use more than one jsp, the toggleActive method overwrites the active state for every every jsp present in the activeOnViewIds-property, i.e. the pages a.jsp;b.jsp;c.jsp are in the property and you navigate to b.jsp the else branch in toggleActive sets the activity to false for.a.jsp than works properly for b.jsp but for c.jsp the active state is set to false again. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
