Couple thoughts:
1) Is ASM on the classpath?
2) What does the soap message look like if validation is turned off? Does it
actually match the schema?
3) I notice you aren't using the WSDL at runtime. Thus, it ends up using a
generated schema and not the real schema from the wsdl. You
Hi Dan:
ASM is on the classpth.. Does this have an impact?
Dumb question - how do I use the wsdl at runtime?
Do you mean that I should use the wsdl in my service definition? ie.
jaxws:endpoint id=userDataService
implementor=#userManager
On Tue October 27 2009 1:17:40 pm Suneet Shah wrote:
Hi Dan:
ASM is on the classpth.. Does this have an impact?
It can for cases where the SEI and stuff was not generated from wsdl. If asm
isn't there, that can be a problem.If ASM is there, then you should be all
set.
Dumb question -
Hello:
I get the exception below when I call the add() operation on my service
with schema validation turned on. Its goes through fine, if the schema
validation is set to false. I suspect that something is wrong in my wsdl
that is causing this error to come up. However, I am at a loss as
