Announcement Announcement Module
Collapse
No announcement yet.
SAXParseException: src-import.0 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • SAXParseException: src-import.0

    When I start my spring 2.0 application, that works fine under tomcat, on my Websphere 5.0.2 server I get :

    org.xml.sax.SAXParseException
    : src-import.0: Failed to read imported schema document

    A Sax errors occurs when readingg the WEB-INF/applicationContext.xml. This seems to come from Spring 2.0 namespaces.
    It there anything to configure to make this work ?

  • #2
    Seems to be a problem with the XML parsers used by WS 5.0.2 - can you find out what version/implementation are you using?

    Comment


    • #3
      In Spring PDF doc, some config samples use xmlns:xsd="http://www.w3.org/2001/XMLSchema" and other ones xmlns:xsd="http://www.w3.org/2001/XMLSchema-Instance"

      In code, DefaultDocumentLoader seems to regsiter XSD_SCHEMA_LANGUAGE = "http://www.w3.org/2001/XMLSchema".

      What schema URI should I use ? Can someone explain me why there is two URI for schema namespace ? If both are valid, could Spring register both ?

      Comment


      • #4
        My application includes xerces 2.4.0, but AFAIK websphere itself includes xerces. There is no version info in MANIFEST.

        Comment


        • #5
          With WebSphere it is sometimes necessary (but risky) to set the classloader to "parent last". This can be set up in the WAS console. Jar conflicts between the app and WAS can sometimes be resolved that way. With such an old version of WAS, this might be the only sensible option.

          Comment


          • #6
            I've made some test with server configured in "PARENT_LAST" with no change. I cannot set the web-application classloader in parent_last due to some (stupid) deployment constraint (console is write protected and only limited config can be set by a script...)

            Comment


            • #7
              As I see the latest stable release is 2.8.0. Try removing the parser from WS with this one and see how it goes.
              If that is not a possible I'm not sure what other solutions are there (the XSD has no relevance - on my parser both variations works).

              Comment


              • #8
                I'll include xerces 2.8 in my EAR as dependency, so it can be loaded prior to websphere one using PARENT_LAST in the server config. I've no more acces to server today.

                Thanks a lots for your quick and usefull replies !

                Comment

                Working...
                X