-
1. Re: Problem updating from 3.0.1 to 3.1RC6
budoray Sep 13, 2007 2:29 PM (in response to budoray)Did I miss something? Is 3.1 not available for JBoss 4.0.5 yet? I see distributions for Tomcat and assumed this applied to JBoss. Would someone clarify this for me so that I can try to make the move to JBoss 4.2?
Many thanks. -
2. Re: Problem updating from 3.0.1 to 3.1RC6
alexsmirnov Sep 13, 2007 2:38 PM (in response to budoray)Please, provide your page code.
By a jsf specification, view tree can't have more then one components with a same clientId ( refresh in your case ). -
3. Re: Problem updating from 3.0.1 to 3.1RC6
budoray Sep 13, 2007 3:10 PM (in response to budoray)Hmm. I don't have duplicate ids in the my tags are most are assigned by JSF. I double checked that my taglibs do not include duplicate tags and I made sure to change the a4j and rich taglib uri to the updated ones listed in the sample war. I removed the old a4j jar and the old richfaces jar and now include the 3 richfaces jars with the distribution.
With that said, are you hinting that there's a component with an id of 'refresh' on one of the pages that's causing this? I'll dig through the code and look again, but please correct me if I'm chasing this problem incorrectly. -
4. Re: Problem updating from 3.0.1 to 3.1RC6
alexsmirnov Sep 13, 2007 3:43 PM (in response to budoray)duplicate Id for a component refresh
- this message mean about second component with clientId 'refresh' found in view tree.