id not being handled correctly by icefaces? //JIRA-1593
[Logo]
ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf
[Search] Search   [Recent Topics] Recent Topics   [Groups] Home Page | www.icefaces.org  [Register] Register  [Login] Login 
id not being handled correctly by icefaces? //JIRA-1593  XML
Forum Index -> JBoss Seam Integration
Author Message
tony.herstell

Joined: 01/12/2006 00:00:00
Messages: 206
Offline


Given this menuItem has an id:

Code:
             <ice:menuItem id="goHomeMenuOption" value="#{messages.menu_item_main_menu}" action="#{menu.goHome}">
                 <s:conversationPropagation type="none"/>
             </ice:menuItem>
 


Why are we getting this:
Code:
 21:23:04,375 INFO  [[/risingstars]] WARNING: Component _id53:_id54:goHomeMenuOption:_id104 just got an automatic id, because there was no id assigned yet. If this component was created dynamically (i.e. not by a JSP tag) you should assign it an explicit static id or assign it the id you get from the createUniqueId from the current UIViewRoot component right after creation!
 21:23:04,375 INFO  [[/risingstars]] WARNING: Component _id53:_id54:goHomeMenuOption:_id105 just got an automatic id, because there was no id assigned yet. If this component was created dynamically (i.e. not by a JSP tag) you should assign it an explicit static id or assign it the id you get from the createUniqueId from the current UIViewRoot component right after creation!
 21:23:04,375 INFO  [[/risingstars]] WARNING: Component _id53:_id54:goHomeMenuOption:_id106 just got an automatic id, because there was no id assigned yet. If this component was created dynamically (i.e. not by a JSP tag) you should assign it an explicit static id or assign it the id you get from the createUniqueId from the current UIViewRoot component right after creation!
 


Is this JIRA'able?
philip.breau


Joined: 08/05/2006 00:00:00
Messages: 2675
Offline


Hi Tony,

I think it's fairly harmless, but I think you can JIRA it. It's probably due to the child components that MenuItemRenderer creates and doesn't assign an id to.

Philip

.
judy.guglielmin

Joined: 20/02/2007 00:00:00
Messages: 1196
Offline


It is totally harmless in that the icefaces view handler assigns it a unique id if it doesn't already have one...In the Jira you might want to mention having some setting to suppress the warning....Not sure if you want to remove it entirely as sometimes you may want to ensure that you have supplied unique Id's???
tony.herstell

Joined: 01/12/2006 00:00:00
Messages: 206
Offline


Philip,

As its something outside the control of the person using IceFaces and it does clutter up the server log (badly when you have a large menu structure!) then I think it is worth being able to suppress it.. or perhaps IceFaces can assign ID's to the these autogenerated components automatically and not actually complain.

I will Raise a JIRA.
tony.herstell

Joined: 01/12/2006 00:00:00
Messages: 206
Offline


http://jira.icefaces.org/browse/ICE-1593
Baleyba

Joined: 16/11/2006 00:00:00
Messages: 110
Offline


Hi,

I have the same problem.
I explain it here: http://www.icefaces.org/JForum/posts/list/5113.page#22837

Did you find a solution to remove warnings ?


thanks
regards
Bal.

JBoss 4.2.3 | Java 1.6.0_16 | IceFaces 1.8.2
 
Forum Index -> JBoss Seam Integration
Go to:   
Powered by JForum 2.1.7ice © JForum Team