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

Define XML Namespace for spring-data-cassandra [DATACASS-54] #230

Closed
spring-projects-issues opened this issue Dec 11, 2013 · 3 comments
Closed
Labels
in: core type: enhancement

Comments

@spring-projects-issues
Copy link

spring-projects-issues commented Dec 11, 2013

David Webb opened DATACASS-54 and commented

Create the XML Namespace for spring-data-cassandra and reuse the schema from spring-cassandra where applicable


Affects: 1.0 M1 (Dijkstra)

Issue Links:

  • DATACASS-79 Complete XML support for <repositories>
    ("is duplicated by")

Referenced from: commits df990d2

@spring-projects-issues
Copy link
Author

spring-projects-issues commented Jan 22, 2014

Matthew T. Adams commented

AFAICS, there is no easy way to do this so that the user of the Spring Data Cassandra schema is completely encapsulated from the fact that it's derived from the Spring Cassandra schema.

Solution for now is to simply have two schema files, one for SC & one for SDC, and maintain them in parallel. A future build enhancement could generate the two schema documents (via an XSLT or similar) so that there is no duplication in the source

@spring-projects-issues
Copy link
Author

spring-projects-issues commented Jan 31, 2014

Matthew T. Adams commented

Solution mentioned above is working. I'm now working on adding support for cassandra:repositories

@spring-projects-issues
Copy link
Author

spring-projects-issues commented Feb 3, 2014

Matthew T. Adams commented

df990d2

@spring-projects-issues spring-projects-issues added type: enhancement in: core labels Dec 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core type: enhancement
Projects
None yet
Development

No branches or pull requests

1 participant