|
From: bruce <br...@mc...> - 2003-03-28 14:34:30
|
On Friday 28 March 2003 09:28 am, ek...@ba... wrote: > << > We add another configuration parameter to the XslTransform that provides > the > XSL document inline. This will be in addition to the file configuration > parameter. So the logic is: > > 1. If the file/url parameter is not null, load from the url > 2. if the inline parameter is not null, use the XSL in the parameter > > > I'm not sure of the method signature that would take this, but is it > possible to have an overloaded implementation that has one method that > takes a URL and another that takes a String? No, we have another configuration parameter for the XslTransform pipeline stage called, say transformationScript. This contains the script inline > Also, how would this information be stored in the Properties Files / > CONFIG table? An additional key/value pair or column? Or are you > thinking of using the existing key / cfg_value field to store EITHER the > URL or the actual script? If this is your choice, the db schema has to > change to support more than 255 chars. Bingo - we will have to increase the storage area. The script will get stored in the cfg_value column. > Otherwise, it sounds great!!! > > Erik > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |