Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 29

Thread: SAAJ0511 problem with spring-ws

  1. #11

    Default

    Arjen, I noticed you set the issues's fix version to 1.0.1.

    Did you reproduce the problem? If so, could you let me know what the underlying problem is so I can start thinking about a workaround?

    Thanks,
    -Ralph.

  2. #12
    Join Date
    Jul 2005
    Location
    Rotterdam, the Netherlands
    Posts
    1,562

    Default

    I haven't had time to reproduce it yet. I only set the fix version to 1.0.1 because I intend to look at it before that version in released. A date for 1.0.1 has not been set yet, but I expect it to be somewhere at the end of September. Of course, the issue might be fixed beforehand, but in snapshot releases.
    Arjen Poutsma

    Spring Web Services Dev Lead
    Please read the FAQ

  3. #13

    Default

    OK, thanks. Let me know if I can help somehow.

  4. #14

    Default same problem

    Hi,

    I am experiencing the same problem.

    "28-Aug-2007 10:45:05 com.sun.xml.messaging.saaj.soap.EnvelopeFactory createEnvelope
    SEVERE: SAAJ0511: Unable to create envelope from given source"

    The versions of xalan (2.6.0) and xerces (2.6.2) war in my war file generated by mvn install. Deploying to tomcat 5.5.17 on jdk 1.5. Maven insists on downloading these versions of the file. I followed the tutorial and then ran into this problem.

    Any pointers?

  5. #15

    Default resolved

    I got around this problem by changing versions of the xalan and xerces files in the war file created by maven to the following: xercesImpl-2.8.1.jar and xalan-2.7.0.jar.

    My question is how do I get maven to include the right version of these files in the war file?

    This seems to be a bit of a dark art in Maven2 in Maven1 it would have been easy...

  6. #16

    Default

    To change the version of a transitive dependency in Maven2, just add the dependency as a top level dependency to your project, using the desired version.

    Maven2 will then find the dependency in 2 different versions and pick the one that's closest to your project (closest in terms of transitions). A dependency of a dependency is always preferred to a dependency of a dependency's dependency. By making something a top level dependency of your project, you can make sure the version matches your expectations.

    Cheers,
    -Ralph.

  7. #17

    Default yes indeed

    Yes,

    That's exactly what I ended up doing...

    It might be helpfull to add the following 2 dependencies to the pom.xml of the Spring-WS tutorial.

    <dependency>
    <groupId>xerces</groupId>
    <artifactId>xercesImpl</artifactId>
    <version>2.8.1</version>
    </dependency>
    <dependency>
    <groupId>xalan</groupId>
    <artifactId>xalan</artifactId>
    <version>2.7.0</version>
    </dependency>

  8. #18
    Join Date
    Mar 2007
    Posts
    15

    Smile

    I have the last couple of days experienced the problem of:
    "28-Aug-2007 10:45:05 com.sun.xml.messaging.saaj.soap.EnvelopeFactory createEnvelope
    SEVERE: SAAJ0511: Unable to create envelope from given source"
    I could not find any simple answer to this on google, so I thought I should share with you the solution in my case which was very simple, but nonetheless extremely hard to find.

    I had forgotten to include
    Code:
    <xs:schema ... elementFormDefault="qualified">
    in my XML Schema.

    Sincerely,
    Paul

  9. #19
    Join Date
    Oct 2008
    Posts
    1

    Default

    Quote Originally Posted by andre.vermeulen View Post
    Yes,

    That's exactly what I ended up doing...

    It might be helpfull to add the following 2 dependencies to the pom.xml of the Spring-WS tutorial.

    <dependency>
    <groupId>xerces</groupId>
    <artifactId>xercesImpl</artifactId>
    <version>2.8.1</version>
    </dependency>
    <dependency>
    <groupId>xalan</groupId>
    <artifactId>xalan</artifactId>
    <version>2.7.0</version>
    </dependency>
    Thanks Andre - that worked a treat after a few hours of frustration!

  10. #20
    Join Date
    Jan 2009
    Posts
    3

    Default

    Hello,

    I'm using Grails with the Grails-metro-plugin 1.0.2 which comes with jaxws-spring 1.8. I deployed a service and the WSDL can be requested, but the following error occur, when I call the service:

    SCHWERWIEGEND: Couldn't create SOAP message due to exception: XML reader error: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
    Message: Premature end of file.

    The recent xalan and xerces builds are in my Grails/lib directory. Does anyone knows what's on here?

    -thanks
    Last edited by creme-fresh; Jan 12th, 2009 at 04:37 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •