Uploaded onthe ftp source in a zip Eclipse project and the bundle already built
Thanks Torsten for looking into it.
Doing a bit of guessing here since I cannot recompile your testcase (due to dependencies on some internal packages of yours).
The problem might be that the schema files cannot be loaded at runtime for doing the validation. On the file system you have the wsdl file in wsdl/ importing the schema files from ../schemas/ which obviously works ok.
However I believe the OSGI classloading will try to load the schema files based on the configured Bundle-ClassPath (as defined in MANIFEST.MF). In your case the Bundle-ClassPath contains ./, which is the root level OSGI bundle directory. So when trying to load ../schemas/... this will then fail as it tries to load it from ./ the bundles root directory.
I suggest a quick test. Place all schema and wsdl files into one directory and import them using "./" in your wsdl and xsd files. This might work around the problem.
As I said, I am only guessing here as I cannot recompile the testcase myself.
Btw, I ran the CXF 2.2 wsdlvalidator against your schema and wsdl files and it succeeded without problems. So these files should be okay.
Thanks for looking into it. The errors are the same.
I have another service with the same configuration (but different schemas) with schemas in the schemas/ directory and the wsdl in the wsdl/ directory and the schemas are included/imported using ../schemas/... and the validation works great. But I'll do the test anyway and I'll let you know.
Well I did the test moving schemas into the wsdl dir and using ./ and that made it work. So something weird is going on since ../schemas is working for my other service.