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.
Printable View
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.
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.
OK, thanks. Let me know if I can help somehow.
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?
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...
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.
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>
I have the last couple of days experienced the problem of:
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. :)Quote:
"28-Aug-2007 10:45:05 com.sun.xml.messaging.saaj.soap.EnvelopeFactory createEnvelope
SEVERE: SAAJ0511: Unable to create envelope from given source"
I had forgotten to include
in my XML Schema.Code:<xs:schema ... elementFormDefault="qualified">
Sincerely,
Paul
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