0.92 changed xmlbeans sts from foo to dynamic. Why was this change required?

I have a common schema catalog and a bunch of wsdl files that use the schemas defined in the schema catalog. We use tibco on server, which generates client wsdls with schema definitions embedded instead of as import statements. This cause problems when we try to generate Axis client stubs. Because xmlbeans is invoked for every wsdl it generates a new sts name (instead of using "foo" eveytime). That makes my xmlbeans classes, between two wsdls stubs generation, runs imcomptible. They now have two different sts names in it. Also, the package schema_org_apache is shared by code generated from two different wsdls, overwriting files generated by first one.

It is problem to work with more than one wsdl files that work off of same schema type definitions.

XFire is attempting for a way to generate stubs from multiple wslds at the same time. Is something on those lines planned for Axis?

Also, xmlbeans has a sfactor tool ( http://xmlbeans.apache.org/docs/2.0.0/guide/tools.html#sfactor) that "Factors redundant definitions out of a set of schemas and uses imports instead." wouldn't something like that which works on wsdls be great? I have 25+ wsdls that include the same schema definitions instead of just importing them. It would be nice to have a tool that refactors and uses import statements.

Is there a way in Axis2 to specify a xmlbeans schema package that is pregenerated based on schema files (xsd) directly, instead of having it generated per wsdl file while using wsd2code?

Thanks,
Prashant Rane

Reply via email to