Removed unused files.

This commit is contained in:
David Montag
2011-04-13 14:22:07 -07:00
parent 83c8805f77
commit 2bbd9132b8
4 changed files with 0 additions and 164 deletions

View File

@@ -1,93 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
<chapter id="get-started">
<title>Getting Started</title>
<para>NOSQL databases have only recently come to prominence, even though some of them have existed for a few years now.
That's why this document will not only guide you through the relevant parts of the Spring Data Graph
API, but also explain some key concepts of graph databases.
</para>
<para>
After reading this document, you should be able to integrate Spring Data Graph into your applications.
If there are any inaccuracies, issues or if you just think the explanations are too complicated, please feed that back to us. Your input will also benefit future readers of this documentation. For details on how to get help
and provide feedback, see <xref linkend="get-started:help"/>.
</para>
<section id="get-started:first-steps">
<title>First Steps</title>
<para>As explained in <xref linkend="why-sd-graph"/>, Spring Data Graph provides integration
between the Spring framework and graph databases. As we said in the introduction <xref linkend="introduction"/>, familiarity with the Spring framework is assumed to get the most out of this book.
But we will explain graph databases and Neo4j in particular in a little more detail.
The main focus of this document is to explain the steps needed to get an interesting Spring Data Graph application up and running.
</para>
<section id="get-started:first-steps:spring">
<title>Knowing Spring</title>
<para>Spring Data Graph makes heavy use of Spring Framework's <ulink url="http://static.springframework.org/spring/docs/3.0.x/reference/spring-core.html">core</ulink> functionality,
such as the <ulink url="http://static.springframework.org/spring/docs/3.0.x/reference/beans.html">IoC</ulink> container,
<ulink url="http://static.springsource.org/spring/docs/3.0.x/reference/validation.html#core-convert">converter</ulink> API and the
<ulink url="http://static.springframework.org/spring/docs/3.0.x/reference/aop.html">AOP</ulink> infrastructure. While it is less important
to know the Spring APIs, understanding the concepts behind them is essential.
The Spring Framework documentation
<ulink url="http://www.springsource.org/documentation">home page</ulink> is a good starting point for
developers who want to become more familiar with the Spring Framework.</para>
</section>
<section id="get-started:first-steps:nosql">
<title>Knowing NOSQL and graph databases</title>
<para>The recent interest in NOSQL databases has been driven by the need to find the better storage solutions for different kinds of data and access patterns. The NOSQL mantra is that databases should fit the data, not the other way round.
The NOSQL space is overflowing with interesting and useful technology. But as a consequence, each store tends to implement its own data access API, leading to a steep learning curve for developers intent on using polyglot persistence. Spring Data aims to ease this burden by
providing consistent abstractions over those underlying data access APIs.
</para>
<para>
Graph databases are a particularly good fit for large networks of connected information (objects). They map objects to nodes and connections to
relationships. Examples of such datasets are social networks, geospatial information, network layouts, and hardware or dependency graphs.
Neo4j is the first graph database that is tightly integrated with the Spring Data Graph project.
</para>
</section>
<section id="get-started:first-steps:samples">
<title>Trying Out The Samples</title>
<para>Spring Data Graph comes with a number of <ulink url="http://github.com/SpringSource/spring-data-graph-examples">samples</ulink>
and unit test cases (if you accessed the sources via
<ulink url="http://github.com/SpringSource/spring-data-graph">github</ulink> or Maven).
</para>
<para>For more information on the samples, see <xref linkend="samples"/>.</para>
</section>
</section>
<section id="get-started:help">
<title>Need Help?</title>
<para>If you encounter issues or you are just looking for advice, feel free to use one of the links below:</para>
<section id="get-started:help:community">
<title>Spring Data homepage</title>
<para>The Spring Data <ulink url="http://www.springsource.org/spring-data">homepage</ulink> provides all the necessary links for information, community forums and code repositories.
</para>
</section>
<section id="get-started:help:professional">
<title>Professional Support</title>
<para>Professional, from-the-source support, with guaranteed response time, is available from <ulink url="http://www.springsource.com">SpringSource</ulink>,
the company behind Spring Data and the Spring Framework.
</para>
</section>
</section>
<section id="get-started:up-to-date">
<title>Follow the Development</title>
<para>For information on the Spring Data source code repository, nightly builds and snapshot artifacts please see the Spring Data home
<ulink url="http://www.springsource.org/spring-data">page</ulink>.
</para>
<para>You can help make Spring Data better serve the needs of the Spring community by interacting with developers through the
<ulink url="http://forum.springsource.org/forumdisplay.php?f=27">community forums</ulink>.</para>
<para>If you find a bug or want to suggest an improvement,
please create a ticket on the <ulink url="https://jira.springframework.org/browse/Spring Data Graph">Spring Data Graph issue tracker</ulink>.</para>
<para>To stay up to date with the latest news and announcements in the Spring eco system, subscribe to the
<ulink url="http://www.springframework.org/">Spring Community Portal</ulink>.</para>
<para>Lastly, you can follow the <ulink url="http://blog.springsource.com/category/data-access/">SpringSource Data blog</ulink> or the project team on Twitter
(@<ulink url="http://twitter.com/SpringData">SpringData</ulink>)</para>
</section>
</chapter>

View File

@@ -1,14 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE partintro PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
<partintro>
<para>
This document is the reference guide for Spring Data Graph.
It explains the underlying concepts, usage, infrastructure of the framework and the behaviour of the underlying graph database.
</para>
<para>For an introduction to graph databases, Spring, or Spring Data examples, please refer to
<xref linkend="get-started"/>. This documentation refers only to Spring Data Graph and
assumes that the reader is familiar with Spring concepts.</para>
</partintro>

View File

@@ -1,18 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
<chapter id="requirements">
<title>Requirements</title>
<para>Spring Data Graph 1.x requires JDK level 6.0 or higher,
and <ulink url="http://www.springsource.org/documentation">Spring Framework</ulink>
3.0.x or higher.</para>
<para>
For the graph database, <ulink url="http://neo4j.org/">Neo4j</ulink> 1.2 or higher is required.
Neo4j has a dependency on Apache Lucene for indexing. Users are encouraged to use the latest version of Neo4j
available.
</para>
<para>
For building the project, Apache Maven (version 2.10 and above) is recommended.
</para>
</chapter>

View File

@@ -1,39 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
<chapter id="why-sd-graph">
<title>Why Spring Data Graph?</title>
<para><ulink url="http://en.wikipedia.org/wiki/NOSQL">NOSQL</ulink>
stores provide novel storage solutions to suit the
data storage requirements of modern applications.
</para>
<para>
Graph databases provide excellent support for connected data - that is data that easily can
be structured as connected nodes in a network.
Property graph databases like Neo4j support an arbitrary number of named properties on
nodes and relationships. Neo4j is highly performant when traversing large, highly-connected datasets with
millions of nodes and relationships, even on commodity hardware.
</para>
<para>
Neo4j is an open source graph database written in Java. It has excellent performance characteristics while providing ACID
semantics and full transactional support (both JTA and XA transactions). Neo4j can run as a lightweight embedded database as well as a standalone
server that exposes the API via a rich REST interface.
</para>
<para>The Spring Data Graph framework makes it easy to
integrate graph databases in existing or new Spring applications. It provides
infrastructure that reduces boilerplate data access code and uses
common patterns and idioms that are well-known in the Spring community, such as declarative transaction management.
Those practices are based on a simple POJO programming model that leverages
annotations to add metadata. It can be integrated in any part of a Spring application,
including the Web or service layers.
</para>
<para>
A special use case of Spring Data Graph is the cross-store functionality that can extend
existing JPA data models with new, graph database backed parts (properties, entities, relationships).
These parts are stored exclusively in the graph database while being transparently
integrated with the JPA entities. This enables easy and seamless addition of new features
that have not been available to JPA-based applications previously.
</para>
</chapter>