Nope, I'm wrong. data, item-out, and append are literal result
elements that should appear in the redirected output, so no namespace
is needed.
The error message says: "[xalantest] line 1 column 157 - Error:
<append> is not recognized!"
Note that <append> is nowhere near line 1 and column 157 in the XSL
stylesheet, so probably something (Xerces?) is parsing the output file
and complaining that the DTD or schema does not declare the data,
item-out, and append elements. That is, it's trying to validate when
it should simply be checking for well-formedness.
On Sun, Feb 12, 2023 at 7:18 AM Elliotte Rusty Harold
<elh...@ibiblio.org> wrote:
>
> I haven't succeeded in building the code yet but I think the problem
> is here in tests/extensions/java/javaRedir2.xsl
>
> <xsl:template match="item">
> <!-- Note append is treated as avt -->
> <redirect:write select="@file" append="{@append}">
> <item-out>
> <append><xsl:value-of select="@append"/></append>
> <data><xsl:value-of select="."/></data>
> </item-out>
> </redirect:write>
> </xsl:template>
>
> This perhaps should be
>
> <xsl:template match="item">
> <!-- Note append is treated as avt -->
> <redirect:write select="@file" append="{@append}">
> <redirect:item-out>
> <redirect:append><xsl:value-of select="@append"/></redirect:append>
> <redirect:data><xsl:value-of select="."/></redirect:data>
> </redirect:item-out>
> </redirect:write>
> </xsl:template>
>
>
> That is, whoever wrote this test made a common error in namespaces.
> The XSLT processor is looking for append, data, and item-out in the
> default namespace (which isn't set) instead of the redirect namespace.
> However, there is a possibility that this error is precisely what this
> test is designed to test.
>
>
> On Sat, Feb 11, 2023 at 8:52 PM Mukul Gandhi <muk...@apache.org> wrote:
> >
> > Hi Gary,
> > The XalanJ api tests are now running fine, and don't produce sort
> > of confusing ant log statements like '[xalantest] line 1 column 147 -
> > Error: <item-out> is not recognized!'.
> >
> > The XalanJ api tests need to be run, with build command 'build
> > apitest'. This has been documented within XalanJ readme file as well.
> >
> > The only issue, that should be solved is following,
> >
> > When we run the XalanJ tests ant target as following, 'build smoketest',
> >
> > this produces certain log statements like following,
> >
> > [xalantest] line 1 column 157 - Error: <append> is not recognized!
> > // log statements like these are, the area of
> > concern for us just now
> > [xalantest] line 1 column 177 - Error: <data> is not recognized!
> > [xalantest] PASS! Redir-Append-Inner-Extension test of javaRedir2.xsl
> > [xalantest] PASS! Redir-AppendOuter-Extension test of javaRedir2.xsl
> > [xalantest] PASS! javaSample3 has been called 1 times
> > [xalantest] PASS! Extension test of javaSample3.xsl
> > [xalantest] HASHTABLE: javaSample4.postCheck() counters
> > [xalantest] index=16
> > [xalantest] PASS! javaSample4 has been called 31 times
> > [xalantest] PASS! Extension test of javaSample4.xsl
> > [xalantest] TestCaseClose(Pass) 1 Conformance test of: java
> > [xalantest] TestCaseInit 2 Conformance test of: library
> > [xalantest] PASS! ExtensionTestlet{trax} libraryDifference01.xsl
> > [xalantest] PASS! ExtensionTestlet{trax} libraryDistinct01.xsl
> >
> > The confusing log statements like '[xalantest] line 1 column 157 -
> > Error: <append> is not recognized!' as, cited within above logs
> > example, are due to the XSL test files javaRedir2.xml and
> > javaRedir2.xsl. When I run this tests XSLT transformation from command
> > like following,
> >
> > java org.apache.xalan.xslt.Process -in javaRedir2.xml -xsl javaRedir2.xsl
> >
> > I don't get any errors like 'line 1 column 157 - Error: <append> is
> > not recognized!'.
> >
> > I believe that, for example, the XalanJ test case for
> > tests\extensions\java\javaRedir2.xml &
> > tests\extensions\java\javaRedir2.xsl doesn't point to a bug within
> > XalanJ, and the log statements like 'line 1 column 157 - Error:
> > <append> is not recognized!' are coming from XalanJ tests
> > implementation (the XalanJ tests ant build implementation, is
> > producing these logs).
> >
> > I'm still unable to solve this (i.e, not producing log statements like
> > '[xalantest] line 1 column 157 - Error: <append> is not recognized!'
> > within XalanJ tests logs.
> >
> > We can either mention these facts, within XalanJ readme file and make
> > a new XalanJ 2.7.3 RC, or spend more time trying to solve these issues
> > (any help from any one, to help us solve these issues is definitely
> > welcome).
> >
> > Any thoughts, please?
> >
> > On Sat, Feb 11, 2023 at 10:23 PM Gary Gregory <garydgreg...@gmail.com>
> > wrote:
> > >
> > > Ping?
> >
> > >> I'm missing something:
> > >>
> > >> "Certain XalanJ "api" tests were causing these issues, and I've now
> > >> omitted those "api" tests from XalanJ tests configuration."
> > >>
> > >> So when are these test run?
> >
> >
> > --
> > Regards,
> > Mukul Gandhi
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
> > For additional commands, e-mail: dev-h...@xalan.apache.org
> >
>
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
--
Elliotte Rusty Harold
elh...@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
