Yes, I want to get the attribute when I'm processing the action. I don't understand the use of f:param. I thought it's for setting request parameters and this doesn't work well in a portal environment (probably they won't be scoped for the particular portlet). In any case, the question remains: what's wrong with my code??? I thought I was doing something very simple.
Perhaps I should mentioned that this is embedded in a <h:dataTable ... var="sRequest"> -- is that causing the problem? -----Original Message----- From: Hagen, Nicholas [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 12:54 PM To: MyFaces Discussion Subject: RE: f:attribute problem Don't you want to use f:param to set parameters on commandLinks? Or are you actually trying to store the value in the attribute map of the command link component and when you try to get the attribute out of the attribute map it is null? Nick -----Original Message----- From: Iordanov, Borislav (GIC) [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 11:33 AM To: MyFaces Discussion Subject: RE: f:attribute problem Well, thanks, but still, isn't that a bug in f:attribute? Don't want to use tomahawk tags at this time, especially when there shouldn't be a need. -----Original Message----- From: Thorbjørn Ravn Andersen [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 12:29 PM To: MyFaces Discussion Subject: Re: f:attribute problem Iordanov, Borislav (GIC) skrev den 15-09-2006 18:25: > Hi, > > Given the code: > > <h:commandLink id="cmdSelectFromSearch"> > <h:outputText value="#{sRequest.id}"/> > <f:attribute name="serviceRequestId" value="#{sRequest.id}"/> > </h:commandLink> > > The value of #{sRequest.id} in the outputText tag is correctly evaluated > (it displays), but not so for the f:attribute where the evaluation > returns null. Any idea why? I need to attach this attribute to the > command component as a parameter to my action listener (not shown here). > I use t:updateActionListener to do this. Works well. -- Thorbjørn
