AW: [Trinidad] Backing Bean Caching issue

Günther, Rene - Innflow AG rene.guent...@innflow.com Sorry, I am always using OpenSessionInViewFilter but I dont know that error and I never used Trinidad. Cheers Rene -Ursprüngliche Nachricht- Von: baeschtu baeschtu [mailto:baesc...@gmail.com] Gesendet: Mittwoch, 17. Februar 2010 21:21

AW: [Trinidad] Backing Bean Caching issue

Like Jakob asked already: Are you sure your entity is saved in your database? After adding the object from your add object - page can you look into the table directly. Eg. if you use MySQL you could check in the MySQL query browser. Also what session pattern do you use?

AW: JSF Combo Box for MyFaces 1.1 - one humble developer's solution

Hi Jakob, If you use an UISelect component, then you have to be aware of the fact that this component matches the submitted values against the possible values. So it has to be a hardcoded validation. I once recognized that too. Is that related to assure data consistency and provide some

AW: pop up for delete confirmation

Probably it is the port 8080, which is blocked for some companies. You could just download the jar and see their documentation. As long as you are using JSF 1.2+ it is very easy to use. Cheers Reen -Ursprüngliche Nachricht- Von: pbr...@johnson.ca [mailto:pbr...@johnson.ca] Gesendet:

AW: Antwort: duplicate component ids after mirgration to JSF 1.2

Another cause could be the use of %...@include file Tags . I dont know whether that falls in the dirty tag category :) -Ursprüngliche Nachricht- Von: andreas.schm...@hella.com [mailto:andreas.schm...@hella.com] Gesendet: Donnerstag, 10. Dezember 2009 15:47 An: MyFaces Discussion Cc:

AW: Any way to customize this validate number message?

Hi Dave, If I remember correctly, if you use a label and use t:inputText instead of h:inputText together with forceId=true in the message tourType:domeTourNumber_of_Adults: will be replaced with the name of the label. There is also a key relating to MyFaces applicationResources.properties file

AW: AW: Any way to customize this validate number message?

Hi Dave, I just looked it up, it is h:outputLabel ... Eg.: h:outputLabel for=status value=#{text['entity.gos.status']}/ t:inputText forceId=true value=#{documentData.documentStatus} id=status required=true/ That way the ... is required message included

AW: AW: Any way to customize this validate number message?

Btw. the file where are the messages are located is myfaces-impl-x.x.x.jar!/javax.faces/MessagesXXX.properties -Ursprüngliche Nachricht- Von: laredotornado [mailto:laredotorn...@gmail.com] Gesendet: Mittwoch, 2. Dezember 2009 19:10 An: users@myfaces.apache.org Betreff: Re: AW: Any

AW: Possible to force bean to load into session at session start up?

Hi Dave, I guess it is possible. I just wanted to point out though that on a first glance it looks like a design flaw. In my opinion a managed bean should always be related to a JSF page. If it is not related, it should not be declared as a bean of the presentation layer. Eg. a bean responsible

Render commanButton as button

Hi, just wanted to ask whether it could cause issues to overwrite the renderer of command button to write button/button tags instead of input type=submit/image? I tried it and it seem to work but I am worried that this might cause issues in certain scenarios which I don't know of. I did that

AW: Render commanButton as button

will submit the text between the button and /button tags, while other browsers will submit the content of the value attribute. Use the inputhttp://www.w3schools.com/tags/tag_input.aspelement to create buttons in an HTML form. On Tue, Nov 17, 2009 at 10:16 AM, Günther, Rene - Innflow AG rene.guent

AW: Problem with duplicated ID in FacesTree in MyFaces 1.2

Hi Jürgen, if I remember correctly (we also had duplicated id issue), in 1.1 something like: h:form id=form h:panelGroupd id=outer h:inputText id=input Renders the id as form:outer:input. In 1.2 it renders the id as form:input. That causes duplicated ids: h:form id=form h:panelGroupd

AW: Render commanButton as button

at 11:06 AM, Günther, Rene - Innflow AG rene.guent...@innflow.com wrote: Hi Cagatay, thanks for that. The question is now whether that different behavior is a problem if I extend tomahawk's command button renderer. The output of my renderer is: button id=documentList_1 name=documentList_1

FYI: Tomahawk Popup + IE 6/7: can not open site issue

On IE 6/7 we encountered a problem with the tomahawk popup component. That issue is probably related to http://support.microsoft.com/default.aspx/kb/927917 I found 2 posts related to that problem in the mailing list: http://www.mail-archive.com/users@myfaces.apache.org/msg37411.html