And here's a patch to the source tree for this fix.
I was wondering why these schemas are being picked up remotely instead
of locally? Seems that picking them up locally would isolate things from
changes since the published schemas can only be for a single version and
these schemas are likely to change often at the moment.
Pete
Peter Hendry wrote:
> The issue appears to be that the endpoint URLs for the schemas are now
> "https" and not "http". The http endpoint is redirected to the https
> one which seems to mess up the parser. Updating the
> applicationContext.xml to use https and also the spring.schemas file
> fixes the problem.
>
> Pete
>
> Peter Hendry wrote:
>> As happened way back (in January I think) the test-app is now causing
>> the exception
>>
>> org.springframework.beans.factory.BeanDefinitionStoreException: Line
>> 1 in XML document from ServletContext resource
>> [/WEB-INF/applicationContext.xml] is invalid; nested exception is
>> org.xml.sax.SAXParseException: White spaces are required between
>> publicId and systemId.
>>
>> I'm guessing this relates to the schemas up on
>> jax-ws.dev.java.net/spring possibly not having been updated? I'm
>> using the latest spring code and building locally.
>>
>> Pete
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
>> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>