I had a go at knocking this up but ran into a bit of an issue. I was surprised to find a lack of shared code between the jaxb databindings for the tooling and the runtime components for the dynamic client. I got going by moving all the needed components from the tooling projects into the runtime/shared areas and then added a dependency on the runtime components from the tooling (which seemed a lot better than the other way around). Is this the correct way to solve this?
I would have though that going forwards (post 2.1.x sometime i guess) it would be better to have a single set of jaxb databinding classes, based on my quick look it would be best based on the tooling support as that is more versatile and have the dynamic clients access a subset of the functionality. Discuss.... Dave dkulp wrote: > > > On Jul 3, 2008, at 6:11 PM, Benjamin Coiffe wrote: > >> is there a way to enable -autoNameResolution for the dynamic client? >> thanks, > > That should probably be the default for the dynamic client. Can you > file a JIRA? It should be just taking the ClassNameAllocatorImpl > from the tools module and setting it into the schemaCompiler. A > patch would be nice. :-) > > Dan > > -- View this message in context: http://www.nabble.com/can-not-generate-stubs-for-salesforce-partner-wsdl-tp18267939p18686530.html Sent from the cxf-user mailing list archive at Nabble.com.
