MARTIN Franck wrote:
That's right, but sometimes in order to get even more flexible (and probably
more complicated) system that static content could be moved further into
another xml file, dynamically loaded by xslt during transformation. This way
the only stuff in xsl would be a logic and data + p
That's right, but sometimes in order to get even more flexible (and probably
more complicated) system that static content could be moved further into
another xml file, dynamically loaded by xslt during transformation. This way
the only stuff in xsl would be a logic and data + presentation would be
MARTIN Franck wrote:
I don't think it is a good idea to insert static content in the xml file. The
xml file should only contain dynamic data (in your case client information). The
static stuff should be placed in the xsl file.
That's right, but sometimes in order to get even more flexible (and prob
I don't think it is a good idea to insert static content in the xml file. The
xml file should only contain dynamic data (in your case client information). The
static stuff should be placed in the xsl file. The xslt process will output a fo
file which will contain the merging of static and dynamic d
Hi,
You can visit this link,where I have asked the
similiar
question.http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=31&t=002274
I hope I'm not redirecting you to another forum.
Regards
Balaji
--- Roland Neilands <[EMAIL PROTECTED]>
wrote: > >My web application needs to
>My web application needs to generate a variety of client forms. These are
>typical boilerplate forms, but are customized by having the client
>information printed in it. From what I gather from reading the various
>literature it sounds like the following steps need to be performed:
>
>1. create