Spring Web Services 1.5.0 Release Candidate 1 released

[ray_harrison]

Not sure what you mean by pre-defined WSDLs, and how this should work in combination with them. but you can't use this approach as a substitute for the SimpleWsdl11Definition. This is more or less the successor to the Wsdl11DefinitionBuilder.

Hi Arjen,

Definitely understood. In our organization, we often receive a WSDL built by another team (what I mean by pre-defined) along with its set of imported XSDs.

Currently, we use SimpleWsdl11Definition along with the code mods provided in the included zip file for http://jira.springframework.org/browse/SWS-281. I take it from your answer above that serving up imported XSDs inside static WSDLs is not a part of this release so we'll continue with our own modifications.

I see that SWS-281 is closed but I believe part of it's original request (serving up imported XSDs inside static WSDLs) does cover a fairly common use case amongst the community. If I have time, I may try and extend your inlining work for the SimpleWsdl11Definition and submit it.

Thanks
Ray

[Arjen Poutsma]

I see. The new provider-based model is a lot more flexible than the older builder model, so I think it could work.

What you could do is create a class that implement MessagesBuilder, PortTypesBuilder, BindingsBuilder, and ServicesBuilder, and simply supply them from the pre-defined WSDL (Use the WSDL4J WSDLFactory and WSDLReader to read the predefined WSDL).

Then, use the ProviderBasedWsdl4jDefinition, plugin in your class in combination with the InlingXsdSchemaTypesProvider, which has a reference to a CommonsXsdSchemaCollection.

[sslavic]

Why haven't sources for SpringWS 1.5.0-rc1 been released in the Spring Milestone Repository? It's good to have them for debugging.

P.S. I've checked out 1.5.0-rc1 tag, and tried to install sources to my local maven repository. Before installing, Maven run tests, and two of them fail:
- testAuthenticateUserPlainTextValid(org.springframe work.ws.soap.security.xwss.callback.jaas.JaasPlain TextPasswordValidationCallbackHandlerTest)
- testValidateCertificateValid(org.springframework.w s.soap.security.xwss.callback.jaas.JaasCertificate ValidationCallbackHandlerTest)

Is this known issue? Was the rc1 released with these two tests failing?

Will there be sources released afterwards? If not, I'll install sources locally by skipping tests.

[Arjen Poutsma]

Hmm, when I go to http://s3browse.com/explore/maven.sp...ore/1.5.0-rc1/, I see the source jars...

With regard to the build failures: not sure what happened there. It works fine on my box , but also the continuous integration machine...

By the way: I will release an 1.5 RC2 tomorrow, with some minor bug fixes and some new documentation.

[sslavic]

I didn't look in each module dir, because I've set whole spring-ws as dependency which has no sources attached/released ( http://s3browse.com/explore/maven.sp...-ws/1.5.0-rc1/ )

Will configure dependency to modules. Thanks for reply! Looking forward to new RC!

[Arjen Poutsma]

Yeah, that all-in-one jar has no source jars, I am afraid. Not sure how to do that in Maven.

[neokiki2000]

I have to conform to naming conventions incompatible with the defaults providers in DefaultWsdl11Definition.

Why don't we have a way to customize those providers?
(They are private with no accessors and no constructor related to those providers is present)

I suggest to add a constructor with the providers.
My need is some kind of regexp compliant portProvider.
I can contribute to that if requested.

[Arjen Poutsma]

The DefaultWsdl11Definition is a wrapper around ProviderBasedWsdl4jDefinition, and a bunch of providers. If you want to customize the providers, simply use the ProviderBasedWsdl4jDefinition, and plug in any provider you want.