[jira] Commented: (TOMAHAWK-922) JSF-1.2: JspTilesViewHandlerImpl

[ https://issues.apache.org/jira/browse/TOMAHAWK-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499498 ] Jesper Pedersen commented on TOMAHAWK-922: -- The JspTilesViewHandlerImpl should be based on Tiles-2.0 from

[jira] Created: (MYFACES-1651) Default converters and validators not correctly registered

Default converters and validators not correctly registered -- Key: MYFACES-1651 URL: https://issues.apache.org/jira/browse/MYFACES-1651 Project: MyFaces Core Issue Type: Bug

[jira] Created: (TOMAHAWK-1010) Allow the sandbox examples to be build with the different configurations (1.1 and 1.2 for both myfaces and ri)

Allow the sandbox examples to be build with the different configurations (1.1 and 1.2 for both myfaces and ri) -- Key: TOMAHAWK-1010 URL:

[jira] Resolved: (TOMAHAWK-1010) Allow the sandbox examples to be build with the different configurations (1.1 and 1.2 for both myfaces and ri)

[ https://issues.apache.org/jira/browse/TOMAHAWK-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Aranda resolved TOMAHAWK-1010. Resolution: Fixed Allow the sandbox examples to be build with the different

[jira] Resolved: (TRINIDAD-41) Create more specific packageContains configuration attributes for the maven-faces-plugin, for validators and converters

[ https://issues.apache.org/jira/browse/TRINIDAD-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Aranda resolved TRINIDAD-41. -- Resolution: Fixed Implemented in the branch of may Create more specific packageContains

[jira] Resolved: (MYFACES-1650) convertDateTime tag not implemented correctly in myfaces 1.2

[ https://issues.apache.org/jira/browse/MYFACES-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Aranda resolved MYFACES-1650. --- Resolution: Fixed I submitted a fix for this yesterday convertDateTime tag not

[jira] Resolved: (MYFACES-1643) f:convertDateTime has wrong signatures of all setters (does not accept javax.el.ValueExpression)

[ https://issues.apache.org/jira/browse/MYFACES-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Aranda resolved MYFACES-1643. --- Resolution: Fixed Fix Version/s: 1.2.0-SNAPSHOT Assignee: Bruno Aranda

MyFaces 1.2 backwards compatibility

Hi, For backwards compatibility, when restoring the view we need to know if older (1.2) ViewHandler and StateManager are used in order to fall into 1.1 behaviour if they are older. The RI checks the faces-config file of the artifact [1], inferring the version from the XML grammar (name of the

Re: MyFaces 1.2 backwards compatibility

Well, you could use reflection if from the tomahawk you check the version of JSF being used. But we are talking here about the opposite, in order to restore the view correctly the JSF implementation needs to know the version used by the artifact to know which behaviour to follow... tomahawk is

Branching tomahawk 2.0

Hi, I would like to create a branch for tomahawk to start playing with the autogeneration of tomahawk components. So this is meant to be the branch for the future Tomahawk 2.0, that will work with jsf 1.2+. Any objections? Bruno

Re: maven-faces-plugin

Yes, I am afraid there is not much documentation (always necessary) for that plugin and I still have to look often into the code to understand what it does. The plugin has too many goals and many configuration attributes. For MyFaces 1.2 I took most of the trinidad configuration, with only some

Re: Branching tomahawk 2.0

On 5/28/07, Bruno Aranda [EMAIL PROTECTED] wrote: I would like to create a branch for tomahawk to start playing with the autogeneration of tomahawk components. So this is meant to be the branch for the future Tomahawk 2.0, that will work with jsf 1.2+. Any objections? Let's not choose a

Re: Branching tomahawk 2.0

Ok, well, as any version of tomahawk will be compatible with 1.2, I will just call it tomahawk_next_20070528. Cheers, Bruno On 28/05/07, Wendy Smoak [EMAIL PROTECTED] wrote: On 5/28/07, Bruno Aranda [EMAIL PROTECTED] wrote: I would like to create a branch for tomahawk to start playing with

Re: maven-faces-plugin

Hi, I badly needed for such a plugin last week but because of issues like documentation and java5 stuff, I couldn't use it. Instead I had to create my own plugin at sourceforge that generates, tld, faces-config, tag files, facelets taglibs and components. Anyway it'd be great to see the trinidad

[jira] Created: (MYFACES-1652) Current shared 2.0 and 3.0 should be compatible

Current shared 2.0 and 3.0 should be compatible --- Key: MYFACES-1652 URL: https://issues.apache.org/jira/browse/MYFACES-1652 Project: MyFaces Core Issue Type: Task Components: JSR-252

Re: maven-faces-plugin

I agree, we should have a lot more documentation, and also be deploying a plugins site in general. Also, yes, the code is written to target Java 5. All of the current consumers (MyFaces 1.2 and Trinidad) require Java 5, so that hasn't been a problem up to this point. -- Adam On 5/28/07,

Re: MyFaces 1.2 backwards compatibility

On 5/28/07, Bruno Aranda [EMAIL PROTECTED] wrote: Hi, For backwards compatibility, when restoring the view we need to know if older (1.2) ViewHandler and StateManager are used in order to fall into 1.1 behaviour if they are older. The RI checks the faces-config file of the artifact [1],

Re: 1.2 API signature problem with UIComponentTagBase

The sad news is that this field should never have been added to UIComponentTagBase in the RI either - there's no other logger instances exposed like this (others are private static, as they should be), and this API was never discussed on the EG. But since it's there, MyFaces has to add it too.