Hi Anuj,
Could you please try using <tr:messages> to display any error message in
the FacesContext? If you refer to Trinidad issue (Trinidad-607) that
resolved this problem, the last comment states that the error message is
stored in the FacesContext.
Thanks
Mamallan
Anuj Patel wrote:
Hi All,
I am using Trinidad-api and trinidad-impl version 1.2.10. When using
tr:inputFile with in tr:panelGroupLayout, if the file size is too
large then the message that should be displayed for informing the user
is not getting displayed. Following is the generated source;
<br><br><span id="uploadPhoto:j_id141"
class="af_panelGroupLayout"><script type="text/javascript">var
_locale='en';var _tLocale='en';</script><script type="text/javascript"
src="/adf/jsLibs/resources/LocaleElements_en1_2_10.js?loc=en"></script><table
id="uploadPhoto:inputFileImg__xc_" class="af_inputFile"
cellpadding="0" cellspacing="0" border="0" summary=""><tr><td
class="af_inputFile_label" nowrap><span
id="uploadPhoto:inputFileImg::icon" style="display:none;"><a
name="_msgAnc_uploadPhoto:inputFileImg" title="Error"
class="AFErrorIconStyle">X</a></span></td><td valign="top" nowrap
class="AFContentCell"><input id="uploadPhoto:inputFileImg"
name="uploadPhoto:inputFileImg" onchange="checkImageExtension(this);"
class="af_inputFile_content" type="file"></td></tr><tr><td></td><td
class="AFComponentMessageCell"><span
id="uploadPhoto:inputFileImg::msg"
class="OraInlineErrorText"></span></td></tr></table>
As one may see in the above generated text, the span that should
display the message is turning out to have no value in it. Also, the
icon "X" does not show up on the screen for some reason.
Following is my code snippet that is generating the above mentioned
view source when trying to upload a file bigger than allowable size;
/<tr:panelGroupLayout partialTriggers="uploadImgBtn deleteBtn">
<tr:inputFile
id="inputFileImg" onchange="validateFile(this);"
partialTriggers="uploadImgBtn deleteBtn"
value="#{backingBean.imageFile}"
rendered="#{backingBean.imageFile==null}"/>
/
Is this a bug or am I missing something? FYI, I get the same
behaviour even with version 1.2.9. Although, in version 1.2.9 there
is an exception reported in the server log where as in 1.2.10 the
exception does not get logged in server log.
-Anuj
