Hi Berin,
At one point, I think I took a step back and tried to keep the transform()
overloads from exploding into every possible combination. We could add
another one for this case, but the one you mention ought to handle work.
So, Colin, have you tried it, and does it work? If so, we could just
document that this is the way to do it if you want to use a stylesheet PI.
If it doesn't work, we can either fix it, or add the overload.
Berin, do you want to do a patch for the overload? I think it's fine to
add a few targetted ones, but we should do them sparingly.
Dave
|---------+--------------------------->
| | Berin Lautenbach|
| | <[EMAIL PROTECTED]|
| | om.au> |
| | |
| | 02/01/2003 01:09|
| | PM |
|---------+--------------------------->
>--------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [email protected]
|
| cc: (bcc: David N Bertoni/Cambridge/IBM)
|
| Subject: Re: XalanParsedSource and xml-stylesheet processing
instruction |
>--------------------------------------------------------------------------------------------------------------------------------|
Colin,
[As an aside - meant to say last night - just put the bugzilla report in
as against the latest version and mark in the text that it actually
applies to CVS.]
Had a look - probably should be added to the API (David?) but in the
interim, you _should_ be able to do this using an empty XSLTInputSource
- ie.
transform(theParsedSource, XSLTInputSource(), theResultTarget);
Cheers,
Berin
Colin Paul Adams wrote:
>Looking through the documentation , and the header file, I cannot see
>a version of XalanTransformer::transform that takes a
>XalanParsedSource as input, and allows you to miss out the
>stylesheet. Does this mean that a XalanParsedSource does not store any
>xml-stylesheet instruction?
>
>
