Moving this back to user since it's not dealing with the MyFaces
project development, but is instead dealing with using MyFaces and
JSF...


I'm not completely sure I understand your description of the situation
with 1), but you can certainly display messages both with no
associated component as well as with an associated component.

See this link for examples of both.  You can combine and arrange them
on the same page however you like.

http://wiki.apache.org/myfaces/Create_and_Display_Messages

As for 2), I've never tried assigning multiple message tags to the
same component, but I would expect it works fine.   Assigning multiple
dataScrollers to the same dataTable component works fine, and I'd be
surprised if it didn't use the same code.

On 9/14/05, Michael Jenik <[EMAIL PROTECTED]> wrote:
> hello,
> 
> 1)
> I have the need to show a lists of messages (like
> Messages tag does) but in diferent points of my page.
> 
> So I would need to put different Messages tags and I
> would have to be abel to discern between them wen I do
> Context.addMessage(....); in my beans.
> 
> There's  discapacity right now. Messages tag only can
> be adjusted to show all messages (not related with any
> Message's for tag attribute) or to show only messages
> with it's clientID param == null .
> 
> It would be cool to have a for attribute in the
> Messages tags. So that I could send multyple messages
> to taht tag from my bean:
> addMessage("MessagesForAttribute",new
> FacesMessage(...));
> 
> ------------
> 2)
> Another problem I have is : If I use two Message tag
> with the same for, then the first addMessage in my
> bean  which point's to that for is asociated with
> boths message tags. So the second addMessage I hoped
> it would be asociated with the second message tag has
> no efect.
> 
> Hopeing your opinions and comments
> 
> Thanks
> 
> Michael
> 
> 
> 
> 
> 
> ______________________________________________________
> Yahoo! for Good
> Donate to the Hurricane Katrina relief effort.
> http://store.yahoo.com/redcross-donate3/
> 
>

Reply via email to