[jira] Commented: (MYFACES-2573) NavigationHandler decoration/delegation not supported in 2.0.0-beta2

[ https://issues.apache.org/jira/browse/MYFACES-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12838283#action_12838283 ] Jakob Korherr commented on MYFACES-2573: So after thinking about this problem

[jira] Created: (MYFACES-2577) Multiple client behaviors confuse the jsf.util.chain function

Multiple client behaviors confuse the jsf.util.chain function - Key: MYFACES-2577 URL: https://issues.apache.org/jira/browse/MYFACES-2577 Project: MyFaces Core Issue Type: Bug

[jira] Resolved: (MYFACES-2573) NavigationHandler decoration/delegation not supported in 2.0.0-beta2

[ https://issues.apache.org/jira/browse/MYFACES-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2573. Resolution: Fixed Fix Version/s: 2.0.0-beta-3 NavigationHandler

[jira] Resolved: (MYFACES-2577) Multiple client behaviors confuse the jsf.util.chain function

[ https://issues.apache.org/jira/browse/MYFACES-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Bohmann resolved MYFACES-2577. Resolution: Fixed Multiple client behaviors confuse the jsf.util.chain function

[jira] Resolved: (MYFACES-2575) Replace RequestMap with FacesContext.getAttributes() where possible

[ https://issues.apache.org/jira/browse/MYFACES-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Bohmann resolved MYFACES-2575. Resolution: Fixed Fix Version/s: 2.0.0-beta-3 Replace RequestMap with

[jira] Commented: (MYFACES-2543) Facelets Taglib jars are not recognized

[ https://issues.apache.org/jira/browse/MYFACES-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12838305#action_12838305 ] Jakob Korherr commented on MYFACES-2543: OK that's a good solution, Ganesh. I

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Yeah, I understand that. Any interest in helping with the fix ? :) -Matthias On Thu, Feb 25, 2010 at 8:47 AM, Ganesh gan...@j4fry.org wrote: Also this blocks me from testing the beta with DojoFaces which might reveal other issues ... Best regards, Ganesh Matthias Wessendorf schrieb:

Re: [Facelets] deploying old Facelets templates with MyFaces 2

I'll do it! I also have a working version running locally at the moment, I just have to test it a little more. Then I'll commit it ;) Regards, Jakob 2010/2/25 Matthias Wessendorf mat...@apache.org Yeah, I understand that. Any interest in helping with the fix ? :) -Matthias On Thu, Feb

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Hi Before commit it I would like to have the description about how this should work and ask or notify the EG about this behavior (so if they decide something different we have a chance to do it right). Since ri is doing something in this field, I think we can commit a solution for that. regards,

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Hi Leo, It is a really easy fix - I just removed the version check in TagLibraryConfig to make old libraries work. If the EG changes the spec in this field we can apply this later. In the meantime, I think we clearly should support old facelets taglibs. Regards, Jakob 2010/2/25 Leonardo Uribe

[jira] Commented: (MYFACES-2543) Facelets Taglib jars are not recognized

[ https://issues.apache.org/jira/browse/MYFACES-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12838324#action_12838324 ] Jakob Korherr commented on MYFACES-2543: I committed a solution for this (I just

Re: [Facelets] deploying old Facelets templates with MyFaces 2

+1 on sooner arrival as later. Current behavior is just lame On Thu, Feb 25, 2010 at 1:33 PM, Jakob Korherr jakob.korh...@gmail.com wrote: Hi Leo, It is a really easy fix - I just removed the version check in TagLibraryConfig to make old libraries work. If the EG changes the spec in this

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Hi If we read every facelet 1.1.x tag lib xml file, it is possible to get ClassNotFoundException. The problem with this behavior is that it does not give the chance to users to fix it without change the original jar file. regards, Leonardo Uribe 2010/2/25 Jakob Korherr jakob.korh...@gmail.com

Re: [Facelets] deploying old Facelets templates with MyFaces 2

It works now ;) 2010/2/25 Matthias Wessendorf mat...@apache.org +1 on sooner arrival as later. Current behavior is just lame On Thu, Feb 25, 2010 at 1:33 PM, Jakob Korherr jakob.korh...@gmail.com wrote: Hi Leo, It is a really easy fix - I just removed the version check in

Re: [Facelets] deploying old Facelets templates with MyFaces 2

but... the spec *clearly* says that if you extend from OLD facelet classes, you have to have to ship it. On Thu, Feb 25, 2010 at 1:37 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi If we read every facelet 1.1.x tag lib xml file, it is possible to get ClassNotFoundException. The problem with

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Hi, But the users DO want to run the old facelets taglibs and, as discussed before, 95% of the old taglibs don't rely on com.sun.facelets classes, they just define tags via xhtml files. If they get a ClassCastException the just have to use the old facelets-1.1.x. This is excatly what the spec

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Hi The problem is the spec is not explicit about that. I think the way it this written those paragraph are as if it was a guideline and that's is the problem because this should be explicit. The behavior proposed (throw ClassNotFoundException or ClassCastException and kick all users to use

Re: [Facelets] deploying old Facelets templates with MyFaces 2

From the spec (10.1.2): A decision was made early in this process to strive for backwards compatibility between the latest popular version of Facelets and Facelets in JSF 2.0. The sole determinant to backwards compatibility lies in the answer to the question, === is there any Java code in the

[jira] Resolved: (MYFACES-2543) Facelets Taglib jars are not recognized

[ https://issues.apache.org/jira/browse/MYFACES-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACES-2543. Resolution: Fixed Fix Version/s: 2.0.0-beta-3 Resolved: See the discussion on the

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Hi Note that this behavior implies that all applications that are using JSP and are upgraded to JSF 2.0 needs to add javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER to work correctly, otherwise if the parser reads a bad facelet taglib file it could throw ClassXXXExceptions. I would like to prevent

[jira] Commented: (MYFACES-2573) NavigationHandler decoration/delegation not supported in 2.0.0-beta2

[ https://issues.apache.org/jira/browse/MYFACES-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12838344#action_12838344 ] Matthias Weßendorf commented on MYFACES-2573: - For the completeness, here is

[jira] Created: (MYFACES-2578) When using ui:repeat and inputText with attributes that are 'nullable' (for example date attributes) they cannot be set to null by entering an empty String ()

When using ui:repeat and inputText with attributes that are 'nullable' (for example date attributes) they cannot be set to null by entering an empty String ()

[jira] Resolved: (MYFACES-2578) When using ui:repeat and inputText with attributes that are 'nullable' (for example date attributes) they cannot be set to null by entering an empty String ()

[ https://issues.apache.org/jira/browse/MYFACES-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2578. - Resolution: Fixed Fix Version/s: 2.0.0-beta-3 When using ui:repeat and

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Hi Leo, Did you check the solution I proposed? Best regards, Ganesh Leonardo Uribe schrieb: In few words, we have to solve MYFACES-2564 too.

[jira] Created: (TRINIDAD-1740) Replace Trinidad TreeVisiting APIs with JSF 2 TreeVisiting APIs

Replace Trinidad TreeVisiting APIs with JSF 2 TreeVisiting APIs --- Key: TRINIDAD-1740 URL: https://issues.apache.org/jira/browse/TRINIDAD-1740 Project: MyFaces Trinidad Issue

[jira] Updated: (TRINIDAD-1740) Replace Trinidad TreeVisiting APIs with JSF 2 TreeVisiting APIs

[ https://issues.apache.org/jira/browse/TRINIDAD-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Sullivan updated TRINIDAD-1740: - Status: Patch Available (was: Open) Replace Trinidad TreeVisiting APIs with JSF 2

[jira] Updated: (TRINIDAD-1740) Replace Trinidad TreeVisiting APIs with JSF 2 TreeVisiting APIs

[ https://issues.apache.org/jira/browse/TRINIDAD-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Sullivan updated TRINIDAD-1740: - Resolution: Fixed Fix Version/s: 2.0.0-alpha 2.0.0-alpha-2

Re: [Facelets] deploying old Facelets templates with MyFaces 2

can you try, now ? On Thu, Feb 25, 2010 at 7:53 PM, Jakob Korherr jakob.korh...@gmail.com wrote: Hi, I implemented the lookup for the presence of the facelets-1.1.x view-handler in the faces-config.xml in the factory, so that the users don't have to explicitly set the related web.xml config

Re: [Facelets] deploying old Facelets templates with MyFaces 2

it should work, by now, just go svn up on trunk. I am interested in the results of testing your project. thx On Thu, Feb 25, 2010 at 7:08 PM, Ganesh gan...@j4fry.org wrote: Hi Matthias, Currently I'm putting my effords into dojofaces, so interest is there, but time is scarce ... sorry.

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Hi, I implemented the lookup for the presence of the facelets-1.1.x view-handler in the faces-config.xml in the factory, so that the users don't have to explicitly set the related web.xml config parameter when they already said that they want to use facelets-1.1.x in faces-config.xml (via

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Hi Ganesh I think dojofaces will not work until apply the patch on MYFACES-2564 (look on subversion commits). This change was reverted but now we need it to complete the solution. Anyway we need to change it a little and maybe remove the code that checks for facelets view handler and takes into

Re: [Facelets] deploying old Facelets templates with MyFaces 2

On Thu, Feb 25, 2010 at 7:15 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi Ganesh I think dojofaces will not work until apply the patch on MYFACES-2564 (look on subversion commits). This change was reverted but now we need it to complete the solution. Anyway we need to change it a little and

Re: [Facelets] deploying old Facelets templates with MyFaces 2

Hi Matthias, Currently I'm putting my effords into dojofaces, so interest is there, but time is scarce ... sorry. Best regards, Ganesh Matthias Wessendorf schrieb: Yeah, I understand that. Any interest in helping with the fix ? :) -Matthias

Re: UIData.setDataModel must not be used anymore?

HEy Mark, interesting found! On Thu, Feb 25, 2010 at 6:25 PM, Mark Struberg strub...@yahoo.de wrote: I found the following source in UIData of the latest from trunk (2.0.0):    protected void setDataModel(DataModel dataModel)    {        throw new UnsupportedOperationException(this method

Re: UIData.setDataModel must not be used anymore?

Hi Mark and Matthias, I am also currently investigating the problem here, but this was far before my time (somewhere in MyFaces 1.2). However I think we should do what the JavaDoc says (set the current DataModel) and apply this change not only on the trunk, but also on the JSF 1.2 branch, because

[jira] Created: (TOMAHAWK-1493) Add StyleBehavior for Tomahawk for JSF 2.0

Add StyleBehavior for Tomahawk for JSF 2.0 -- Key: TOMAHAWK-1493 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1493 Project: MyFaces Tomahawk Issue Type: Task Reporter: Leonardo

[jira] Commented: (TOMAHAWK-1493) Add StyleBehavior for Tomahawk for JSF 2.0

[ https://issues.apache.org/jira/browse/TOMAHAWK-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12838591#action_12838591 ] Jakob Korherr commented on TOMAHAWK-1493: - Sounds just great :) Add

[jira] Commented: (MYFACES-2565) BeanValidator throws Exception if external ExpressionLanguageFactory is being used

[ https://issues.apache.org/jira/browse/MYFACES-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12838612#action_12838612 ] Mark Struberg commented on MYFACES-2565: found an issue which may be related with

[jira] Issue Comment Edited: (TRINIDAD-1728) Trinidad not supporting Opera Mobile in HTC

[ https://issues.apache.org/jira/browse/TRINIDAD-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12834611#action_12834611 ] Mamallan Uthaman edited comment on TRINIDAD-1728 at 2/26/10 3:04 AM:

[jira] Updated: (TRINIDAD-1728) Trinidad not supporting Opera Mobile in HTC

[ https://issues.apache.org/jira/browse/TRINIDAD-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamallan Uthaman updated TRINIDAD-1728: --- Resolution: Fixed Fix Version/s: 1.2.14-core Status: Resolved

Re: UIData.setDataModel must not be used anymore?

from looking at the code it sounds somehow like it has something to do with cascading tables? But just a blind guess ... LieGrue, strub --- Jakob Korherr jakob.korh...@gmail.com schrieb am Fr, 26.2.2010: Von: Jakob Korherr jakob.korh...@gmail.com Betreff: Re: UIData.setDataModel must not be