Hello,
now i have found out that the binding attribute does not work even on an Input
component.
I was used to use this code:
|
| <t:inputText value="#{protokollErstellungname}"
binding="#{protokollErstellung.protocolNameInput}" id="protname"
styleClass="inputtext">
|
| ----------------------
| private UIInput protocolNameInput;
|
|
getFacesContext().addMessage(protocolNameInput.getClientId(getFacesContext()),
| Utils.getMessage("msgProtocolExist",
new String[] { name }, FacesMessage.SEVERITY_ERROR));
|
This code is decoupled from the concrete ClientId. I can put my component on
any place of a page without destroying functionality.
(JSF generate an assembled id of the ids of the component and its parents)
As long as i can not use the binding attribute i have to use the myfaces
attribute 'forceId'. But this does not delete the dependency from bean to
component.
With binding the page designer can choose which component he will bind to a
specific bean (provided that bean offers a corresponding getter/setter pair)
Wíthout binding the page designer must change both, the bean and the page, to
get a component message rendered at the correct place.
Will there be a solution? How can a bean determine the id for a component in
Seam?
Ciao,
Carsten
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940099#3940099
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940099
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
