Can you ugrade to the current XalanJ version and see if you still get
the problem? If so, it's likely in your "bigger project" code. I think
we'll need to see that to see what the problem is since everything is
working from the command line.
Gary
Bjoern Martin wrote:
>
> Hi there.
>
> I have a problem with Xalan-J 1.2.2 (WinNT4, SP6, Xerces-J 1.3.1, JDK
> 1.2.2). I use foo.xml as input and get bar.xml as output, using
> foo2bar.xsl as stylesheet (it just copies everything). The files are
> appended.
> Now I have two different implementation areas for Xalan, one just from
> the cmdline, the other within a bigger project. If I use the cmdline
> transformer to get bar.xml, it's a perfect copy of foo.xml, but using
> the more complex vbersion causes Xalan to output something like the
> attached version of bar.xml (it's not regular). It seems there are
> element tags missing.
> Did anyone of you encounter a similar problem or knows what it might
> be caused by?
> Any help would be appreciated.
>
> Bye,
>
> --
> Bjoern Martin [EMAIL PROTECTED]
>
> ------------------------------------------------------------------------
> Name: bar.xml
> bar.xml Type: BizTalk Schema (text/xml)
> Encoding: Quoted-Printable
>
> Name: foo.xml
> foo.xml Type: BizTalk Schema (text/xml)
> Encoding: Quoted-Printable
>
> Name: foo2bar.xsl
> foo2bar.xsl Type: BizTalk Schema (text/xml)
> Encoding: Base64
