Re: ext-bv addon: Required Initialization for labels required change

Hello Ben, I made a few checks and within my examples everything works (they don't use Richfaces however). Can it be that you are mixing some environments ?? The line of code * ExtValUtils.**configureComponentWithMetaData**(facesContext, targetComponent,

RE: ext-bv addon: Required Initialization for labels required change

Hi Rudy, I am using both property and bean validation. The labels of concern, though, are annotated using @Column(...nullable=false). So perhaps we've discovered my issue. Thanks! I will drop in the non-bean validation version and see how that works. Is there any reason why I can't/shouldn't

RE: ext-bv addon: Required Initialization for labels required change

Rudy, I haven't tried the non-bean version yet but was just wondering if this is the only difference between the two versions? If so, why not just make one version that applies the correct component init/config method based on the annotation type (bean vs property)? Ben -Original

Re: ext-bv addon: Required Initialization for labels required change

Ben, There exists 2 version because the handling of Bean Validation annotations is completely different then the 'standard' ones (you are using JPA annotations but there exists also ExtVal annotations like @Required that do more or less the same as the Bean Validation annotations) The issue that

RE: ext-bv addon: Required Initialization for labels required change

Rudy, --But commenting out the super.initComponent as you proposed will result in not recognizing the Bean validation annoations anymore.-- Thanks for the info. I'm sure I'll need both property and bean annotations on some properties. I'll try using both versions together. Ben

[jira] Created: (TRINIDAD-1947) Supported browsers page is out of date

Supported browsers page is out of date -- Key: TRINIDAD-1947 URL: https://issues.apache.org/jira/browse/TRINIDAD-1947 Project: MyFaces Trinidad Issue Type: Bug Components: Documentation

[jira] Resolved: (TRINIDAD-1947) Supported browsers page is out of date

[ https://issues.apache.org/jira/browse/TRINIDAD-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Robinson resolved TRINIDAD-1947. --- Resolution: Fixed Fix Version/s: 2.0.0.4-core

[Trinidad] I updated the Trinidad site (browsers.xml), any one know how to get it updated on the web?

Looks like the trinidad pom file is wrong and still lists continuum as the continuous integration piece in the pom.xml. I do not see where on hudson that the Trinidad site is listed as a project. Anyone know how to get the site re-deployed? Also anyone know the correct URL for hudson in the

Re: NPE in Required Initialization for labels addon (property version)

thx ben - i've committed it. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/10/27 neum...@ijet.com This null-check was also needed in the Bean Validation version.

[jira] Updated: (TRINIDAD-1858) Fix fail-over bugs where session state is mutated without dirtying the Session objects

[ https://issues.apache.org/jira/browse/TRINIDAD-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Sullivan updated TRINIDAD-1858: - Status: Patch Available (was: Open) Fix fail-over bugs where session state is

[jira] Updated: (TRINIDAD-1858) Fix fail-over bugs where session state is mutated without dirtying the Session objects

[ https://issues.apache.org/jira/browse/TRINIDAD-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Sullivan updated TRINIDAD-1858: - Resolution: Fixed Fix Version/s: 2.0.0.4-core 1.2.14-core