Try adding this to the page and email the result:
<tr:outputText value="pattern: #{entity['format']}"
inlineStyle="display:block;" />
Add one of these for every EL expression that you may question if it
is working or not.
-Andrew
On Wed, Jul 9, 2008 at 10:47 AM, Gerard Donnelly
<[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
> I've sorted the issue with the Illegal Argument. My mistake.
>
> However, the convertDateTime tag is still not working.
>
> The tag is kicking in but the evaluation of the pattern is not.
>
> If I hard code a value of 'yyyyMMdd' everything is sweet - in those
> cases where that is the actual pattern I require.
> If I rely on el (either nodeFormat or entity['format']) the pattern
> seems to be set to "".
>
> I'm guessing this is the case as the attached image shows a valid
> example being blank.
>
> Setting of shortDesc with nodeFormat is fine and the required value is
> displayed as a tool tip.
>
>
> <tr:inputDate id="dateChoice" value="#{nodeData}"
> rendered="#{nodeType['date'] and !nodeReadOnly}"
> maximumLength="#{nodePrecision}"
> shortDesc="#{nodeFormat}">
> <tr:convertDateTime pattern="#{entity['format']}"
> secondaryPattern="#{entity['format']}" />
> </tr:inputDate>
>
>
> Thanks,
> Gerry
>
>
> -----Original Message-----
> From: Andrew Robinson [mailto:[EMAIL PROTECTED]
> Sent: 08 July 2008 16:56
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate
>
> ****** This Message Originated From The Internet Please Be Aware Of
> Suspicious Attachments And Content ******
>
>> Didn't realise that that was the case. Seems to be working though.
>
> I think there may be a discrepancy between the c:set in JSTL and the
> behavior of the c:set TagHandler in facelets. Another user was saying
> that it worked as well. Facelets must implement it differently by not
> evaluating the EL immediately, but instead doing a substitution of EL.
>
>>
>> With the exception of <tr:convertDateTime>. Is this also related to
>> evaluation order?
>
> I just looked at the source code after reading your stack trace, and
> the UIXComponentBase.findComponent is dying on this line:
>
> if ("".equals(id))
> throw new IllegalArgumentException();
>
> Interpreting the stack trace:
> Caused by: java.lang.IllegalArgumentException
> at
> org.apache.myfaces.trinidad.component.UIXComponentBase.findComponent(UIX
> ComponentBase.java:491)
> at
> org.apache.myfaces.trinidad.util.ComponentUtils.findRelativeComponent(Co
> mponentUtils.java:385)
> at
> org.apache.myfaces.trinidadinternal.context.RequestContextImpl.addPartia
> lTriggerListeners(RequestContextImpl.java:550)
> at
> org.apache.myfaces.trinidad.component.UIXComponentBase.decode(UIXCompone
> ntBase.java:710)
>
> It seems that the partialTtriggers of a component is "" during decode,
> which is an invalid value (although if true, this should probably be
> handled).
>
> From the stack, it appears that the problem is a child of a column
> component. Try to see if you can determine the component and
> partialTriggers that may be blank on decode, then get back to us.
>
>
>
> P Please consider the environment before printing this email
>
>
> P Please consider the environment before printing this email
> _________________________________________________________
>
> 1. The information contained in this E-mail, including any files transmitted
> with it, is confidential and may be legally privileged. This E-mail is
> intended only for the personal attention of the stated addressee(s). Any
> access to this E-mail, including any files transmitted with it, by any other
> person is unauthorised. If you are not an addressee, you must not disclose,
> copy, circulate or in any other way use or rely on the information contained
> in this E-mail or any files transmitted with it. Such unauthorised use may be
> unlawful. If you have received this E-mail in error, please inform the sender
> immediately and delete it and all copies from your system. You may not
> forward this E-mail without the permission of the sender.
>
> 2. The views expressed in this E-mail are those of the author, and do not
> necessarily represent the views of AMT-SYBEX. Internet communications are not
> secure and AMT-SYBEX cannot, therefore, accept legal responsibility for the
> contents of this message nor for any damage caused by viruses.
>
> AMT-SYBEX Limited is a UK company, registration number GB03036807 at address
> The Spirella Building, Bridge Road, Letchworth, SG6 4ET.
> AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at
> address Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ.
> For more information on the AMT-SYBEX Group visit http://www.amt-sybex.com
> _________________________________________________________
>
