-
1. Re: faces-config.xml error notification
akazakov May 16, 2010 12:34 PM (in response to vblagojevic)Looks like a bug. Could you attach your faces-config.xml?
-
2. Re: faces-config.xml error notification
vblagojevic May 16, 2010 2:21 PM (in response to akazakov)I just created an empty faces-config.xml using JBT. First, it JBT regarded as valid and then about 5 minutes later (and I did not change the file) it started to become regarded as invalid. Maybe the error message is going to give you some clues....
-
3. Re: faces-config.xml error notification
akazakov May 17, 2010 4:48 AM (in response to vblagojevic)Ok, I've created an issue in JIRA. https://jira.jboss.org/browse/JBIDE-6295
Thanks.
-
4. Re: faces-config.xml error notification
jenskreidler Jun 9, 2010 5:25 PM (in response to vblagojevic)Hi,
I recently encountered this faces-config validation issue as well.
Using e3.5.2, I saw that the issue has been resolved for next Tools 3.2 version.
As I'd like to get that bug away, I went on the development release page to get a 3.2-Snapshot version of that bundle. But unfortunately there are no snapshot releases where that issue'd be resolved, so what can I do so far?
Thx in advance
-
5. Re: faces-config.xml error notification
akazakov Jun 9, 2010 6:36 PM (in response to jenskreidler)You can get the latest 3.2 nightly build here: http://download.jboss.org/jbosstools/builds/nightly/trunk/201006071537/
-
6. Re: faces-config.xml error notification
ova Jul 5, 2010 5:18 AM (in response to akazakov)Hello,
I've tried the latest 3.2 nightly build and the latest 3.1.2 nightly build. Nothing works. I still have a red point and see the message "Value cannot be empty". Any idea?
I have Eclipse 3.5.x for J2EE developers. My faces-config.xml is valid and placed under META-INF directory. The strange thing is that my other faces-config.xml under WEB-INF directory doesn't cause this message and red points in Eclipse.
Thanks in advance for any workarounds.
-
7. Re: faces-config.xml error notification
maxandersen Jul 5, 2010 8:26 AM (in response to ova)It should be fixed - if it still isn't please report jira on it.
btw. workaround is to set name attribute (required in jsf 1.2 but not in 2.x)