[jira] Commented: (MYFACES-2933) Our archetype poms are not entirely correctly understood by Netbeans
[ https://issues.apache.org/jira/browse/MYFACES-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916810#action_12916810 ] Werner Punz commented on MYFACES-2933: -- Sure This is a netbeans bug, I would not even call it a bug, more a deficit, but do we have to make it extra hard for the users, if we can find a clean way which also provides netbeans compatibility? Just my 2c regarding all this. Our archetype poms are not entirely correctly understood by Netbeans Key: MYFACES-2933 URL: https://issues.apache.org/jira/browse/MYFACES-2933 Project: MyFaces Core Issue Type: Bug Components: Archetype Affects Versions: 2.0.2 Environment: all Reporter: Werner Punz We have a small structural problem in the myfaces archetypes. This is not a bug in our code, but nevertheless easily fixable. The problem is the way we handle the profiles which is not correctly understood by Netbeans 6.9. We have following code: profiles profile idmyfaces/id activation property name!jsf/name /property /activation and profile !-- Activate by adding -Djsf=mojarra -- idmojarra/id activation property namejsf/name valuemojarra/value /property /activation No this structure just should ensure that if no jsf=... is set myfaces is chosen automatically. This makes netbeans go haiwire if you chosse mojarra as profile because suddenly we have the mojarra and myfaces dependencies parallely in the project. Since this structure is mostly a hack we should replace it with the correct way to do things here: activation activeByDefaulttrue/activeByDefault property namejsf/name valuemyfaces/value /property /activation instead of !jsf so if no value is given we activate the myfaces profile by default -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] Release Tobago 1.0.30
Hello, I would like to release Tobago 1.0.30 with TOBAGO-921. For a detail list please consult the release notes: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12315336 The version is available at the nexus staging repository. Staging repository: https://repository.apache.org/content/repositories/orgapachemyfaces-001/ The Vote is open for 72h. [ ] +1 [ ] +0 [ ] -1 Regards Bernd
Re: [VOTE] Release Tobago 1.0.30
+1 Am 01.10.10 09:29, schrieb Bernd Bohmann: Hello, I would like to release Tobago 1.0.30 with TOBAGO-921. For a detail list please consult the release notes: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12315336 The version is available at the nexus staging repository. Staging repository: https://repository.apache.org/content/repositories/orgapachemyfaces-001/ The Vote is open for 72h. [ ] +1 [ ] +0 [ ] -1 Regards Bernd
Re: [core] FacesEL vs. UEL vs. UEL 2.2
I strongly recommend using the following artifact instead of javax.el: dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-el_2.2_spec/artifactId version1.0/version /dependency LieGrue, strub --- On Fri, 10/1/10, Leonardo Uribe lu4...@gmail.com wrote: From: Leonardo Uribe lu4...@gmail.com Subject: Re: [core] FacesEL vs. UEL vs. UEL 2.2 To: MyFaces Development dev@myfaces.apache.org Date: Friday, October 1, 2010, 1:54 AM Hi 2010/9/30 Martin Koci martin.kocicak.k...@gmail.com Hi, there is a disorder in Expression Lauguage names in myfaces core. Currently myfaces (method javax.faces.validator._ExternalSpecifications.isUnifiedELAvailable() for example) output a log: MyFaces Unified EL support enabled But this is a little misleading: there should be Unified EL 2.2 support enabled because it tests presence of EL 2.2. Unified EL support enabled does not make sence at all because JSF use Unified EL as core technology and that cannot be disabled. There are three major versions of ELs: 1) javax.faces.el - old and depreceated 2) javax.el 2.0, 2.1 (from JSP 2.0, 2.1) Isn't javax.el version 1.0 on maven repo? 3) javax.el 2.2 from JSP 2.2, part of Java EE 6, EL with method invocations Suggestions: Rename isUnifiedELAvailable to isUnifiedEL22Available, TagValueExpressionUEL to TagValueExpressionUEL22 and so on. For EL 2.3 (not released yet) we can add similar methods/classes. Change log to MyFaces Unified EL 2.2 support enabled (method invocations are available). I'll add similiar log MyFaces Faces EL (javax.faces.el) support disabled as part of disabling old technologies WDYT ? Sounds reasonable for me. The message about MyFaces Faces EL really is not necessary at all in my personal opinion, but if it is added no problem. regards, Leonardo Kočičák
[jira] Created: (TOMAHAWK-1550) Problem
Problem --- Key: TOMAHAWK-1550 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1550 Project: MyFaces Tomahawk Issue Type: Bug Components: Data List Affects Versions: 1.1.9 Environment: windows xp tomcat 6.0.18 mojarra jsf 2.0 Reporter: Federico Belli When i click on a commandLink n-th action from a t:dataList i get from the action linked to the element the element itself, but the element returned is not the 1st but the n-th Step to reproduce bug: 1. datalist with command links 2. click on 4 element for example 3. the returned element is the 1st -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (EXTCDI-69) CODI sometimes locks up if started under heavy load
CODI sometimes locks up if started under heavy load --- Key: EXTCDI-69 URL: https://issues.apache.org/jira/browse/EXTCDI-69 Project: MyFaces CODI Issue Type: Bug Reporter: Mark Struberg From time to time my server hangs at 100% CPU with a kill -3 revealing the following stack trace in most threads: http-8080-exec-150 daemon prio=10 tid=0x4b03b800 nid=0x57b1 runnable [0x4e568000] java.lang.Thread.State: RUNNABLE at java.util.Collections$UnmodifiableCollection$1.hasNext(Collections.java:1009) at org.apache.myfaces.extensions.cdi.core.impl.config.ConfigProducer$1.resolve(ConfigProducer.java:96) at sun.reflect.GeneratedMethodAccessor115.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.webbeans.intercept.InterceptorHandler.invoke(InterceptorHandler.java:283) at org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:98) at org.javassist.tmp.java.lang.Object_$$_javassist_76.resolve(Object_$$_javassist_76.java) at org.apache.myfaces.extensions.cdi.javaee.jsf.impl.scope.conversation.WindowContextManagerObserver.cleanup(WindowContextManagerObserver.java:56) at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.webbeans.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:256) at org.apache.webbeans.event.NotificationManager.fireEvent(NotificationManager.java:441) at org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:404) at org.apache.webbeans.event.EventImpl.fire(EventImpl.java:74) at org.apache.myfaces.extensions.cdi.javaee.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster.broadcastAfterEvent(JsfRequestLifecycleBroadcaster.java:66) at org.apache.myfaces.extensions.cdi.javaee.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener.afterPhase(JsfRequestLifecyclePhaseListener.java:44) at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersAfter(PhaseListenerManager.java:111) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:185) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at org.apache.myfaces.extensions.cdi.javaee.jsf2.impl.listener.phase.CodiLifecycleWrapper.execute(CodiLifecycleWrapper.java:55) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [core] FacesEL vs. UEL vs. UEL 2.2
Agreed. I usually don't like numbers in method names, but in this case it's more correct. /JK On 30 sep. 2010, at 23:04, Martin Koci martin.kocicak.k...@gmail.com wrote: Hi, there is a disorder in Expression Lauguage names in myfaces core. Currently myfaces (method javax.faces.validator._ExternalSpecifications.isUnifiedELAvailable() for example) output a log: MyFaces Unified EL support enabled But this is a little misleading: there should be Unified EL 2.2 support enabled because it tests presence of EL 2.2. Unified EL support enabled does not make sence at all because JSF use Unified EL as core technology and that cannot be disabled. There are three major versions of ELs: 1) javax.faces.el - old and depreceated 2) javax.el 2.0, 2.1 (from JSP 2.0, 2.1) 3) javax.el 2.2 from JSP 2.2, part of Java EE 6, EL with method invocations Suggestions: Rename isUnifiedELAvailable to isUnifiedEL22Available, TagValueExpressionUEL to TagValueExpressionUEL22 and so on. For EL 2.3 (not released yet) we can add similar methods/classes. Change log to MyFaces Unified EL 2.2 support enabled (method invocations are available). I'll add similiar log MyFaces Faces EL (javax.faces.el) support disabled as part of disabling old technologies WDYT ? Kočičák
[ANNOUNCE] release of MyFaces Tomahawk v 1.1.10
The Apache MyFaces team is pleased to announce the release of Apache MyFaces Tomahawk 1.1.10. MyFaces Tomahawk provides a series of JavaServer Faces components that go beyond the JSF specification. These components are compatible with the Sun JSF 1.1 Reference Implementation (RI) or any other JSF 1.1 compatible implementation. Of course the custom components can also be used with the Apache JSF implementation MyFaces Core. There are also artifacts (tomahawk12 and tomahawk20) with enhanced compatibility with JSF 1.2 and JSF 2.0 MyFaces Tomahawk 1.1.10 is available in both binary and source distributions. * http://myfaces.apache.org/download.html MyFaces Tomahawk is also available in the central Maven repository under Group ID org.apache.myfaces.tomahawk. Release Notes - MyFaces Tomahawk - Version 1.1.10 Bug * [TOMAHAWK-800] - IinputHTML editor does not work for objectembed * [TOMAHAWK-827] - inputHtml * [TOMAHAWK-1217] - InputCalendar references a message from a MyFaces property file (Does not work when being used with Sun RI) * [TOMAHAWK-1352] - The Status of DataTable wasn't saved when use HashMap to reserve DataSource. * [TOMAHAWK-1358] - getTableIndex: Integer to String (ClassCastException) * [TOMAHAWK-1375] - t:selectItems without var causes NullPointerException under Pluto * [TOMAHAWK-1378] - DetailStamp values overwritten if no datatable * [TOMAHAWK-1403] - t:selectItems behaviour with Map values is weird * [TOMAHAWK-1426] - Next and Previous facets * [TOMAHAWK-1439] - org.apache.myfaces.webapp.filter.servlet.ServletExternalContextWrapper does not wrap getRequestCharacterEncoding() * [TOMAHAWK-1443] - StreamingAddResource introduces memory leak * [TOMAHAWK-1447] - Invalid JavaScript in myFacesUtils.js in function myFacesKupuFormSubmit() * [TOMAHAWK-1448] - InputHtmlRenderer: Missing xmlns:i18n declarations in various HTML elements * [TOMAHAWK-1454] - [myfaces-example-simple-1.1.9] Panel stack example fails with NPE * [TOMAHAWK-1460] - ClassCastException when testing Tomahawk 1.1.9 table demos when preserveDataModel=true * [TOMAHAWK-1463] - Data Scroller renders the paginator twice. * [TOMAHAWK-1469] - CAPTCHA renderer throws exception when session is missing * [TOMAHAWK-1475] - NullPointerException in UpdateActionListener caused by getType() * [TOMAHAWK-1482] - HtmlTableRendererBase produces invalid html if row is not available * [TOMAHAWK-1483] - Build Failure on Maven 2.2.1 * [TOMAHAWK-1487] - ClassCastException when rendering HtmlDataScroller with core 2.0 * [TOMAHAWK-1489] - inputHtml does not work with firefox 3.6 * [TOMAHAWK-1494] - HtmlMessageRenderer evaluates value expressions of not rendered components * [TOMAHAWK-1496] - HtmlTreeRenderer 'background-image' incorrect html style attribute * [TOMAHAWK-1509] - t:documentBody should call ExtensionsPhaseListener.writeCodeBeforeBodyEnd() only for AddResource instances that does not buffer * [TOMAHAWK-1510] - Add t:documentHead and t:documentBody ability to render target panels (head,body). * [TOMAHAWK-1515] - f:ajax event not triggered inside t:calendar * [TOMAHAWK-1516] - t:toggleLink render end when enabledOnUserRole is used * [TOMAHAWK-1517] - t:selectOneRow does not handle integers * [TOMAHAWK-1519] - t:selectManyPicklist does not handle displayValueOnly * [TOMAHAWK-1520] - t:popup implements EventAware but does not render all properties * [TOMAHAWK-1531] - Components does not render id when required * [TOMAHAWK-1534] - t:dataTable detailStamp facet sometimes is not saved * [TOMAHAWK-1535] - t:dataTable detailStamp does not work well with jsf 2 ajax * [TOMAHAWK-1536] - t:dataList needs to implement invokeOnComponent and visitTree * [TOMAHAWK-1537] - t:datatable updateModelFromPreservedDataModel does not take into account vb.getType could not return the right type * [TOMAHAWK-1539] - t:tree2 uses UIGraphic as component for render navigation, but on ri it does not render border=0 * [TOMAHAWK-1540] - t:tree2 navigation, expand and collapse image component manipulation does not work well with PSS on JSF 2 * [TOMAHAWK-1541] - detailStamp state should be deleted on deleteRowStateForRow in t:dataTable * [TOMAHAWK-1544] - org.apache.myfaces.custom.date.HtmlDateRenderer.encodeEnd() broken * [TOMAHAWK-1545] - Components inside detailStamp facet requires clientId reset each time setRowIndex is called * [TOMAHAWK-1549] - t:commandNavigation and t:commandNavigation2 has wrong DEFAULT_RENDERER_TYPE Improvement * [TOMAHAWK-769] - Datascroller - context sensitive previous, next links * [TOMAHAWK-799] - Use of the actionListener event of datascroller to maintain the index of the first row inside a managed bean. * [TOMAHAWK-1194] - SelectOneRow: The attribute GroupName can't contain EL * [TOMAHAWK-1433] - Add attribute itemOnclick to datalist * [TOMAHAWK-1500] - t:inputHtml
[jira] Commented: (TRINIDAD-1922) In Facelets, Partial Refreshing tr:inputText Not Working
[
https://issues.apache.org/jira/browse/TRINIDAD-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917038#action_12917038
]
Mamallan Uthaman commented on TRINIDAD-1922:
@Cedric: Sorry, your patch didn't fix this issue.
After a few more testing, I found this problem is Mojarra specific as with
Myfaces I cound't repro this problem. We need to investigate if we miss any
parameter before calling Mojarra's Ajax apis or it is simply a bug in Mojarra.
In Facelets, Partial Refreshing tr:inputText Not Working
--
Key: TRINIDAD-1922
URL: https://issues.apache.org/jira/browse/TRINIDAD-1922
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 2.0.0.3-core
Environment: Any browser
Reporter: Mamallan Uthaman
Trinidad currently has an issue partial refreshing an tr:inputText. This
problem is specific to facelets where we use JSF Ajax apis. I tested with the
latest code from our trunk, and below is my test page:
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
ui:composition xmlns:ui=http://java.sun.com/jsf/facelets;
xmlns:f=http://java.sun.com/jsf/core;
xmlns:tr=http://myfaces.apache.org/trinidad;
xmlns:trd=http://myfaces.apache.org/trinidad/demo;
xmlns:trh=http://myfaces.apache.org/trinidad/html;
tr:document id=d1 title=Client Behavior Support
tr:form id=f1
tr:panelHeader text=Ajax Issue/
tr:panelHorizontalLayout
tr:commandLink text=Press id=cb1 partialSubmit=true
tr:setActionListener from=Success
to=#{sessionScope.status}/
/tr:commandLink
tr:inputText value=#{sessionScope.status}
partialTriggers=cb1 columns=6/
/tr:panelHorizontalLayout
/tr:form
/tr:document
/ui:composition
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2936) Add new utility class for init parameters WebConfigParamUtils
Add new utility class for init parameters WebConfigParamUtils - Key: MYFACES-2936 URL: https://issues.apache.org/jira/browse/MYFACES-2936 Project: MyFaces Core Issue Type: Improvement Components: JSR-314 Affects Versions: 2.0.2 Reporter: Leonardo Uribe Assignee: Leonardo Uribe It could be good to have an utility class to handle init parameters, instead do the same code again and again over multiple classes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2936) Add new utility class for init parameters WebConfigParamUtils
[ https://issues.apache.org/jira/browse/MYFACES-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2936. - Fix Version/s: 2.0.3-SNAPSHOT Resolution: Fixed Add new utility class for init parameters WebConfigParamUtils - Key: MYFACES-2936 URL: https://issues.apache.org/jira/browse/MYFACES-2936 Project: MyFaces Core Issue Type: Improvement Components: JSR-314 Affects Versions: 2.0.2 Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 2.0.3-SNAPSHOT It could be good to have an utility class to handle init parameters, instead do the same code again and again over multiple classes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2935) SystemEvent Acid Test
[ https://issues.apache.org/jira/browse/MYFACES-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917056#action_12917056 ] Kennard Consulting commented on MYFACES-2935: - I should mention that MyFaces 2.0.2 passes 1/3 of the Acid Tests. Mojarra 2.0.3 passes 0/3, but they have recently done some fixes in their nightly builds so that now they pass 2/3. I'd be hugely grateful if you could download it and at least confirm you can reproduce the problem. Then we can have a fight to see which team passes the Acid Test first! SystemEvent Acid Test - Key: MYFACES-2935 URL: https://issues.apache.org/jira/browse/MYFACES-2935 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.2 Reporter: Kennard Consulting Attachments: EventTest.myfaces.zip Hi guys, First - thanks for the great work you do with MyFaces. It's an awesome product and it's wonderful to have an independent implementation of the JSF spec! I am the author of Metawidget (http://metawidget.org), a JSF component that does a lot of runtime component tree manipulation. This was unreliable under JSF 1, but JSF 2 introduced SystemEvents which promise to make this more solid. I believe Metawidget exercises SystemEvents more than most, and as such I am seeing problems both in MyFaces (2.0.2) and in Mojarra (2.0.3). As a bit of fun I have created a small Acid Test (inspired by http://acidtests.org) for SystemEvents. I would be most grateful if you could work through the 3 tests and get MyFaces working with them. Basically the tests all use a combination of PreRenderViewEvent and tree manipulation. Full instructions are included on each JSF page. Of course, there may be bugs in the test itself in which case feel free to point them out :) Regards, Richard. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MFCOMMONS-13) Update MessageUtils to new implementation in shared
Update MessageUtils to new implementation in shared --- Key: MFCOMMONS-13 URL: https://issues.apache.org/jira/browse/MFCOMMONS-13 Project: MyFaces Commons Issue Type: Improvement Components: myfaces-commons-utils Reporter: Leonardo Uribe Assignee: Leonardo Uribe Update MessageUtils to new implementation in shared, to allow different default bundles per component. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MFCOMMONS-14) Add new utility class for init parameters WebConfigParamUtils
Add new utility class for init parameters WebConfigParamUtils -- Key: MFCOMMONS-14 URL: https://issues.apache.org/jira/browse/MFCOMMONS-14 Project: MyFaces Commons Issue Type: Improvement Components: myfaces-commons-utils Reporter: Leonardo Uribe Assignee: Leonardo Uribe -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MFCOMMONS-14) Add new utility class for init parameters WebConfigParamUtils
[ https://issues.apache.org/jira/browse/MFCOMMONS-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MFCOMMONS-14. - Fix Version/s: 1.0.1-SNAPSHOT Resolution: Fixed Add new utility class for init parameters WebConfigParamUtils -- Key: MFCOMMONS-14 URL: https://issues.apache.org/jira/browse/MFCOMMONS-14 Project: MyFaces Commons Issue Type: Improvement Components: myfaces-commons-utils Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 1.0.1-SNAPSHOT -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MFCOMMONS-13) Update MessageUtils to new implementation in shared
[ https://issues.apache.org/jira/browse/MFCOMMONS-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MFCOMMONS-13. - Fix Version/s: 1.0.1-SNAPSHOT Resolution: Fixed Update MessageUtils to new implementation in shared --- Key: MFCOMMONS-13 URL: https://issues.apache.org/jira/browse/MFCOMMONS-13 Project: MyFaces Commons Issue Type: Improvement Components: myfaces-commons-utils Reporter: Leonardo Uribe Assignee: Leonardo Uribe Fix For: 1.0.1-SNAPSHOT Update MessageUtils to new implementation in shared, to allow different default bundles per component. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1881) In Blackberry 4.7, f:ajax fails with Trinidad, but works with Mojarra components
[ https://issues.apache.org/jira/browse/TRINIDAD-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917067#action_12917067 ] Mamallan Uthaman commented on TRINIDAD-1881: Myfaces has recently fixed this problem, but to make things complicated, BB4.7 browser simply crashes during a facelets' page-loading. However, both MyFaces and Trinidad works well in isolation, but in a facelets page where both Trinidad and myfaces' JavaScript files are downloaded, BB simply crashes. It hard to tell where the problem could be as both MyFaces and Trinidad works well in isolation. Interestingly, I didn't face this issue before, so probably, some recent changes in Myfaces' JS code interact with Trinidad's JS and crashed BB 4.7 or vice versa :) In Blackberry 4.7, f:ajax fails with Trinidad, but works with Mojarra components -- Key: TRINIDAD-1881 URL: https://issues.apache.org/jira/browse/TRINIDAD-1881 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.0-alpha Environment: Blackberry 4.7 Reporter: Mamallan Uthaman In Blackberry (BB) 4.7, f:ajax works with Mojarra components, but using f:ajax with Trinidad components simply crashes BB4.7 browser. The problem need not be in Trinidad as I presume, but we need further investigation to ascertain what is responsible for the crash. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1825) Mobile Browsers - PPR broken in Facelets
[ https://issues.apache.org/jira/browse/TRINIDAD-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917111#action_12917111 ] Mamallan Uthaman commented on TRINIDAD-1825: Unlike MyFaces, Mojarra is still not ready to handle mobile browser. I have raised this issue to Mojarra team, but it seems they can fix only in JSF2.2 release. Of course, even after Mojarra fix is ready, we will have some work like TRINIDAD-1881to enable JSF Ajax instead of legacy PPR in mobile platforms. Until all the above issues are resolved, we can use our legacy PPR code as a temporary fix . Mobile Browsers - PPR broken in Facelets Key: TRINIDAD-1825 URL: https://issues.apache.org/jira/browse/TRINIDAD-1825 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.0-alpha-2 Environment: Windows Mobile 6, Blackberry 4.6 Reporter: Mamallan Uthaman Currently, PPR in Windows Mobile 6 neither performs a partial submit nor a full-page submit. I guess, for mobile browsers, we need to revert the PPR handling to old legacy way than JSF2 APIs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] release for myfaces tomahawk v 1.1.10
+1 On Thu, Sep 30, 2010 at 5:02 PM, Werner Punz werner.p...@gmail.com wrote: +1 Am 28.09.10 02:42, schrieb Leonardo Uribe: Hi, I was running the needed tasks to get the 1.1.10 release of Apache MyFaces Tomahawk out. Release notes can be found at [4]. Please note that this vote concerns all of the following parts: 1. Maven artifact group org.apache.myfaces.tomahawk v1.1.10 [1] The artifacts are deployed to my private Apache account ([1]). There is also binary and source packages available on [2] Please take a look at the 1.1.10 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] http://repository.apache.org/content/repositories/orgapachemyfaces-017/org/apache/myfaces/tomahawk [2] http://people.apache.org/~lu4242/tomahawk1110binsrc [3] http://www.apache.org/foundation/voting.html#ReleaseVotes [4] http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310272styleName=Htmlversion=12315371 http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310272styleName=Htmlversion=12315371 -- Hazem Ahmed Saleh Ahmed Author of (The Definitive Guide to Apache MyFaces and Facelets): http://www.amazon.com/Definitive-Guide-Apache-MyFaces-Facelets/dp/1590597370 http://www.amazon.com/-/e/B002M052KY Web blog: http://www.jroller.com/HazemBlog [Web 2.0] Mashups Integration with JSF: http://code.google.com/p/mashups4jsf/
[jira] Commented: (TRINIDAD-1723) Trinidad 2: ClassCastEXception while running componentDemos.jspx
[ https://issues.apache.org/jira/browse/TRINIDAD-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917120#action_12917120 ] Pavitra Subramaniam commented on TRINIDAD-1723: --- Should 3c. above be the following? Trinidad 2: ClassCastEXception while running componentDemos.jspx Key: TRINIDAD-1723 URL: https://issues.apache.org/jira/browse/TRINIDAD-1723 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.0-alpha-2 Reporter: Max Starets Grab the latest trinidad-2.0.x branch and try running componentDemos.jspx. The following exception will be thrown: java.lang.ClassCastException: org.apache.myfaces.trinidadinternal.uinode.UIComponentUINode cannot be cast to org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode at org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode.__getAdapter(UIXComponentUINode.java:439) at org.apache.myfaces.trinidadinternal.uinode.UINodeRendererBase.encodeEnd(UINodeRendererBase.java:65) at org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:852) at org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:70) at org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:509) at org.apache.myfaces.trinidad.render.CoreRenderer.encodeAllChildren(CoreRenderer.java:531) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.renderContent(PanelPartialRootRenderer.java:70) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.renderContent(BodyRenderer.java:151) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.encodeAll(PanelPartialRootRenderer.java:153) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.encodeAll(BodyRenderer.java:80) at org.apache.myfaces.trinidad.render.CoreRenderer.delegateRenderer(CoreRenderer.java:546) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer.encodeAll(DocumentRenderer.java:82) This does not seem to be JSF 2 specific, but I have not had time to try it on the latest MAIN. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TRINIDAD-1723) Trinidad 2: ClassCastEXception while running componentDemos.jspx
[ https://issues.apache.org/jira/browse/TRINIDAD-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917120#action_12917120 ] Pavitra Subramaniam edited comment on TRINIDAD-1723 at 10/1/10 8:10 PM: Should 3c. above be the following? c. ImplProject depends on the APIProject's deployment profile (instead of on Build Output) ? was (Author: pasubra): Should 3c. above be the following? Trinidad 2: ClassCastEXception while running componentDemos.jspx Key: TRINIDAD-1723 URL: https://issues.apache.org/jira/browse/TRINIDAD-1723 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.0-alpha-2 Reporter: Max Starets Grab the latest trinidad-2.0.x branch and try running componentDemos.jspx. The following exception will be thrown: java.lang.ClassCastException: org.apache.myfaces.trinidadinternal.uinode.UIComponentUINode cannot be cast to org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode at org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode.__getAdapter(UIXComponentUINode.java:439) at org.apache.myfaces.trinidadinternal.uinode.UINodeRendererBase.encodeEnd(UINodeRendererBase.java:65) at org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:852) at org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:70) at org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:509) at org.apache.myfaces.trinidad.render.CoreRenderer.encodeAllChildren(CoreRenderer.java:531) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.renderContent(PanelPartialRootRenderer.java:70) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.renderContent(BodyRenderer.java:151) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.encodeAll(PanelPartialRootRenderer.java:153) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.encodeAll(BodyRenderer.java:80) at org.apache.myfaces.trinidad.render.CoreRenderer.delegateRenderer(CoreRenderer.java:546) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer.encodeAll(DocumentRenderer.java:82) This does not seem to be JSF 2 specific, but I have not had time to try it on the latest MAIN. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [core] FacesEL vs. UEL vs. UEL 2.2
Yeah, saw this in the logs and wondered, 'caus EL was working well. Good to know this in case a customer asks :-). +1 for all your suggestions. Best regards, Ganesh Am 30.09.2010 23:04, schrieb Martin Koci: Hi, there is a disorder in Expression Lauguage names in myfaces core. Currently myfaces (method javax.faces.validator._ExternalSpecifications.isUnifiedELAvailable() for example) output a log: MyFaces Unified EL support enabled But this is a little misleading: there should be Unified EL 2.2 support enabled because it tests presence of EL 2.2. Unified EL support enabled does not make sence at all because JSF use Unified EL as core technology and that cannot be disabled. There are three major versions of ELs: 1) javax.faces.el - old and depreceated 2) javax.el 2.0, 2.1 (from JSP 2.0, 2.1) 3) javax.el 2.2 from JSP 2.2, part of Java EE 6, EL with method invocations Suggestions: Rename isUnifiedELAvailable to isUnifiedEL22Available, TagValueExpressionUEL to TagValueExpressionUEL22 and so on. For EL 2.3 (not released yet) we can add similar methods/classes. Change log to MyFaces Unified EL 2.2 support enabled (method invocations are available). I'll add similiar log MyFaces Faces EL (javax.faces.el) support disabled as part of disabling old technologies WDYT ? Kočičák -- There are two kinds of people in the world, those who believe there are two kinds of people and those who don't. — Robert Benchley
