[WEB400] Re: Webfacing JSP Custom Tags - Automatic Generation?

[Colm_Byrne@xxxxxxxx]

To Web 400 group:

Has anyone done auto JSP tag creation for Webfacing?

We manually modified webfacing JSPs to include our own corporate JSP custom
tag library.
This transforms screens to our own corporate standard and is an easier way
to maintain code.
What we would like to do is to automate this procedure so that our JSP tags
are included at conversion time.

What normally is generated:
                  <TD NOWRAP ><INPUT <% if (isProtected) { %>
                        readonly tabindex=-1 <% } %> 
id="l<%=zOrder%>_FWXX00001$MENOPT2"
                        
previousValue="<%=FWXX00001.getFieldValueWithTransform("MENOPT2", 
QUOTED_TRANSFORM)%>"
                        class="<%=isProtected?"wf_pr":""%> wf_rightJustify 
wf_default wf_field"
                        
VALUE="<%=FWXX00001.getFieldValueWithTransform("MENOPT2", QUOTED_TRANSFORM)%>"
                        SIZE=2 MAXLENGTH=2 STYLE="width: "></TD>

To this automatically:
       <ff:inputField  id="l1_FWXX00001$MENOPT2" name ="l1_FWXX00001$MENOPT2"
      value="<%=FWXX00001.getFieldValueWithTransform(\"MENOPT2\", 
QUOTED_TRANSFORM)%>"/>

This would be a big time saver.

Our friend Mister Hockings at IBM generously  included a set of methods (WSAD 
5.0)  to automatically influence JSP custom tag creation.  But alas, I
am not
at Doctorate level with Java and WSAD.

The documentation follows:
The interaction with the conversion process is done by coding a "generator" 
class that will be called by the conversion when a particular field or
WebSetting type is encountered. The generator class (or classes) are contained 
in and declared by a plugin. The purpose of the generator is to emit
the JSP Tag source for the field. There are three flavours of generator 
classes, each have their own interface to implement. The three interfaces are
as follows:
IFieldTagGenerator: This is the generator that is used for basic field types. 
Implementing a generator like this would handle all fields types that
are directed to it.

IWSTagGenerator: This generator will key off of WebSettings values on the 
field. If a generator of this type is selected then it will be used in
preference over the generator for the basic field type.

IWSSubTagGenerator: define the main HTML construct that is emitted.

 I can't figure out how to correctly implement this. Has anyone implemented 
these methods? Is there any complete examples from how to insert the xml
plugin to
converting the field elements etc?

Regards

Colm Byrne