- This topic has 35 replies, 15 voices, and was last updated 12 years, 10 months ago by
.
-
Posts
-
MWThomson,
I could not replicate this issue with the Version and Build id you specified.
Can you answer some questions for me?1. When you invoke the autocomplete does it prompt for ‘RequireMessage’ or ‘RequiredMessage’ ?
2. Do you see it for < h:selectOneMenu> or <h:inputText> ?
3. Does the validator highlight ‘RequireMessage’ as unknown attribute?
4. Do you get suggestions when you delete the ‘RequireMessage’ and invoke the autocomplete?Note that it does work correctly at runtime.
1) auto complete does not show it
2) it does show up for <h:selectOneMenu /> and <h:inputText />
3) Problems view:
Unknown attribute (requiredMessage) userInformation.xhtml /<appname>/web/secure/administration L/<appname>/web/secure/administration/userInformation.xhtml Facelets Problem (JSF)4) I do get suggestions, including “required”, but not “requiredMessage” or even “requireMessage”
Our namespace:
<ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:c="http://java.sun.com/jstl/core" xmlns:f="http://java.sun.com/jsf/core" xmlns:ice="http://www.icesoft.com/icefaces/component" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:ice-cc="http://www.icesoft.com/icefaces-composite-comps">Thanks for the detailed explanation with screenshots; as you can see, we did fix this issue with for the regular HTML prefix but not for the ICEfaces prefix which escaped us. I’ll try to get this fixed in the upcoming 9.0 GA release, thanks again for the report.
@Support-Brian wrote:
Thanks for the detailed explanation with screenshots; as you can see, we did fix this issue with for the regular HTML prefix but not for the ICEfaces prefix which escaped us. I’ll try to get this fixed in the upcoming 9.0 GA release, thanks again for the report.
Any word on when this will be fixed? It is still a problem in 9.0 (Build id:9.0-20110318).
MWThomson,
Thanks for reminding us. I’ve put this out as a high priority item for 9.0.1 due in a couple of weeks. My team is looking at the problem right now and may have a few questions for you shortly.
MWThomson,
We took this up with the ICEfaces team and the issue will be fixed in the upcoming 1.8.3 and 2.1 releases of ICEfaces. Once these versions of ICEfaces are publicly available, updating your libraries to use that version will fix the problem.
See here for more details: http://jira.icefaces.org/browse/ICE-6930
Appreciate your support.
