Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XSD should work independently of hazelcast-spring.jar #11577

Closed
crazyguyonabike opened this issue Oct 12, 2017 · 2 comments
Closed

XSD should work independently of hazelcast-spring.jar #11577

crazyguyonabike opened this issue Oct 12, 2017 · 2 comments

Comments

@crazyguyonabike
Copy link

@crazyguyonabike crazyguyonabike commented Oct 12, 2017

Since the hazelcast-spring.xsd is at https://hazelcast.com/schema/spring/hazelcast-spring-3.9.xsd but the namespace is http://www.hazelcast.com/schema/spring you can't get it to load.

If you try to load it all with http you get:

org.xml.sax.SAXParseException; systemId: http://hazelcast.com/schema/spring/hazelcast-spring-3.9.xsd; lineNumber: 2; columnNumber: 35; s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw '301 Moved Permanently'.

If you try to load it all with https you get:

org.xml.sax.SAXParseException; systemId: https://hazelcast.com/schema/spring/hazelcast-spring-3.9.xsd; lineNumber: 23; columnNumber: 47; TargetNamespace.1: Expecting namespace 'https://www.hazelcast.com/schema/spring', but the target namespace of the schema document is 'http://www.hazelcast.com/schema/spring'.

If you try and mix them i.e.
xmlns:hz="http://www.hazelcast.com/schema/spring"
and
http://www.hazelcast.com/schema/spring https://hazelcast.com/schema/spring/hazelcast-spring-3.9.xsd

Then you get:

org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace [http://www.hazelcast.com/schema/spring]
@mesutcelik
Copy link
Contributor

@mesutcelik mesutcelik commented Oct 12, 2017

Hi @crazyguyonabike ,

The same question is already answered by @googlielmo in Google Groups.

Can you please follow-up in this link ?

@mesutcelik mesutcelik closed this Oct 12, 2017
@crazyguyonabike
Copy link
Author

@crazyguyonabike crazyguyonabike commented Oct 12, 2017

I created the issue because I think the errors with XSD are separate from the workaround. If the .jar is not present, the errors should be more related to classes not found. Since you are serving the XSD over HTTPS, the namespaces in the both the XSD on the web and the XSD in the .jar are incorrect. So this issue is to fix the namespaces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants