You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by "Edwards, Peter" <ed...@genrad.com> on 2000/07/20 17:35:01 UTC

XML parser problem building Slide from CVS

Remy

Thanks for the work bringing Slide up to date so quickly - I have now got it
running in non-Avalon mode and have used DAVExplorer to place files on the
server. Incidentally, DAVExplorer does not show the tree of files (it has
the same problem with DAV4J) - any ideas on that one would be welcome.
Internet Explorer 5's "Web folders" works with Slide.

Now to the problem - initially Slide failed to build because of the errors
listed below. I had JAXP 1.0 on the classpath. It does not include classes
like org.xml.sax.Attributes. I put Xerces on the path and everything was
fine. The Attributes class is a SAX2.0 class - I haven't checked but I
assume JAXP is not up to that version.

main:
    [javac] Compiling 126 source files to D:\Java\CVS\build\slide\classes
    [javac]
D:\Java\CVS\jakarta-slide\src\share\org\apache\slide\util\conf\SAXConfigurat
ionBuilder.java:13: Class org.xml.sax.Attributes not found in import.
    [javac] import org.xml.sax.Attributes;
    [javac]        ^
    [javac]
D:\Java\CVS\jakarta-slide\src\share\org\apache\slide\util\conf\SAXConfigurat
ionBuilder.java:14: Class org.xml.sax.ContentHandler not found in import.
    [javac] import org.xml.sax.ContentHandler;
    [javac]        ^
    [javac]
D:\Java\CVS\jakarta-slide\src\share\org\apache\slide\util\conf\SAXConfigurat
ionBuilder.java:17: Class org.xml.sax.ext.LexicalHandler not found in
import.
    [javac] import org.xml.sax.ext.LexicalHandler;
    [javac]        ^
    [javac]
D:\Java\CVS\jakarta-slide\src\share\org\apache\slide\util\conf\SAXConfigurat
ionBuilder.java:27: Interface org.xml.sax.ContentHandler of class
org.apache.slide.util.conf.SAXConfigurationBuilder not found.
    [javac] public class SAXConfigurationBuilder implements ContentHandler {
    [javac]                                                 ^
    [javac] 4 errors

If I can add yet another question (or two) 
  - I read somewhere that you are working on a client API for this - what is
the plan?
  - Is there / will there be a relationship between Slide and DAV4J?

Regards
Pete

____________________________________________________________________________
____
Pete Edwards	: Principle Software Engineer, R&D Department, GenRad ADS
			: Orion Business Park, Bird Hall Lane, Stockport,
Cheshire, SK3 OXG, United Kingdom
Direct line		: +44 (0)161 491 9127
Fax			: +44 (0)161 491 9106

Email		: edwardsp@genrad.co.uk <ma...@genrad.co.uk>




Re: XML parser problem building Slide from CVS

Posted by Remy Maucherat <re...@apache.org>.
> Remy
>
> Thanks for the work bringing Slide up to date so quickly - I have now got
it
> running in non-Avalon mode and have used DAVExplorer to place files on the
> server. Incidentally, DAVExplorer does not show the tree of files (it has
> the same problem with DAV4J) - any ideas on that one would be welcome.

I reproduced the problem with DAVExplorer 0.62. 0.60 was working just fine
:-(
I tried hacking my code to make it generate simpler XML, with or without
namespaces, etc ... to no effect.
The only rational explation I see is that it looks at the status text (which
it shouldn't). It's something I have no control on, unfortunately. Now that
the void setStatus(int sc, String st) has been deprecated, I can't specify
the status text (which should be Multistatus, here), so the webserver puts a
default status text, which is usually something completely unrelated ...
If DAV4J fails too, I think the latest DAV Explorer is a bit broken.

> Internet Explorer 5's "Web folders" works with Slide.

That has been tested a lot, so it should work.

> Now to the problem - initially Slide failed to build because of the errors
> listed below. I had JAXP 1.0 on the classpath. It does not include classes
> like org.xml.sax.Attributes. I put Xerces on the path and everything was
> fine. The Attributes class is a SAX2.0 class - I haven't checked but I
> assume JAXP is not up to that version.

That's correct. It's SAX 1 and DOM 1.

> main:
>     [javac] Compiling 126 source files to D:\Java\CVS\build\slide\classes
>     [javac]
>
D:\Java\CVS\jakarta-slide\src\share\org\apache\slide\util\conf\SAXConfigurat
> ionBuilder.java:13: Class org.xml.sax.Attributes not found in import.
>     [javac] import org.xml.sax.Attributes;
>     [javac]        ^
>     [javac]
>
D:\Java\CVS\jakarta-slide\src\share\org\apache\slide\util\conf\SAXConfigurat
> ionBuilder.java:14: Class org.xml.sax.ContentHandler not found in import.
>     [javac] import org.xml.sax.ContentHandler;
>     [javac]        ^
>     [javac]
>
D:\Java\CVS\jakarta-slide\src\share\org\apache\slide\util\conf\SAXConfigurat
> ionBuilder.java:17: Class org.xml.sax.ext.LexicalHandler not found in
> import.
>     [javac] import org.xml.sax.ext.LexicalHandler;
>     [javac]        ^
>     [javac]
>
D:\Java\CVS\jakarta-slide\src\share\org\apache\slide\util\conf\SAXConfigurat
> ionBuilder.java:27: Interface org.xml.sax.ContentHandler of class
> org.apache.slide.util.conf.SAXConfigurationBuilder not found.
>     [javac] public class SAXConfigurationBuilder implements ContentHandler
{
>     [javac]                                                 ^
>     [javac] 4 errors

Ooops.
Thanks a lot for reporting the problem (since Xerces is sitting in my
classpath I didn't get the errors). I shouldn't have added that class in the
first place, since it's actually not used.

> If I can add yet another question (or two)
>   - I read somewhere that you are working on a client API for this - what
is
> the plan?

To make a low level HTTP client library with all the DAV extensions I could
dream of. It will be used for :
- testing of new DAV functionality
- administration tools
- perhaps later build a DAV4J-like client library on top of it

>   - Is there / will there be a relationship between Slide and DAV4J?

Right now, nothing. In the future, I don't know what IBM wants to do with
DAV4J. I guess they should have open-sourced it a while ago, and there
haven't been a lot of updates to it in the past year either.
A lot of design ideas are the same, though. DAV4J's client API is different,
but way too high level IMO for what I want to do with it.

Remy