Is "USER_DEFINED_HTML_PROP" fixed in JATO 1.1 ?

Hi Srikanth--

(I guess you must be working for Wipro in India, because I'm always up too

late when I first see messages from you. <g>)

> - values defined in "DisplayFieldDescriptor.USER_DEFINED_HTML_PROP" are

> still not reflected on final html.

> Is this problem fixed in JATO 1.1 ?

This is not a problem per se. Unfortunately, we have not made it clear

enough that information in the descriptor is entirely irrelevant to a JATO

application at runtime (with one exception for Buttons and HREFs). The

intent of the descriptor is to cache information statically so that it can

be used efficiently by display field instances which are created per

request.

When migrating an application, the iMT populates the descriptor with all the

declarative information that was present for the display field in the

original app. The reason for this is to allow developers migrating an

application to take advantage of information that wasn't translated directly

to a JATO construct, though this is rare. Thus, the information in the

descriptor is only an archive of information from the original application,

and is largely irrelevant in JATO; therefore, changing that information has

no effect. (Generally, the relevant information is translated by the iMT and

there are other ways to manipulate it.)

In your case, the user-defined HTML property is no longer necessary because

of the way JATO applications generate HTML output. Instead, you should just

modify your JSP to use whatever HTML you desire for a field. You can use

the <jato:getDisplayFieldValue> tag to get a display field's value without

any HTML. You can then wrap this "naked" value in whatever HTML you want in

the JSP. Also, most of the JATO tags have attributes that reflect the most

common usage of the user-defined HTML property, such as JavaScript event

specification. See the taglib documentation for for examples.

> Also, I observed that I need to append "fireDisplayEvents="true" for all

> my JATO tags, if the events have to invoked.

> However, if my requirements is such a way that, events have to be

> invoked on all my pages and their displayFiels, then is their

> way I change DisplayFieldTagBase.java and make the default behaviour to

> be true. (I always want events to be invoked for all

> Jato display objects)

> Is there way to do this, without affecting the framework?

Unfortunately, the only way to change the default behavior without a lot of

trouble would be to modify the tag handler base class. Instead, the easiest

way to do what you want is to specify "fireChildDisplayEvents=true" on the

<jato:useViewBean> tag. This attribute on the view bean or any other

container view will cause events for all the children in that container to

fire, and is inherited by child containers.

Todd

Guest at 2007-7-1 16:30:41 >