You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/extending-neo4j/project-setup.adoc
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,7 +138,7 @@ Once the procedure has been deployed to the _plugins_ directory of each Neo4j in
138
138
139
139
The _Seed from URI_ feature provides the ability to dynamically discover additional seed provider implementations from the class path.
140
140
141
-
Seed providers should be implemented in Java and this guide provides instructions on how to do this using Maven as the build tool.
141
+
Seed providers should be implemented in Java; and this guide provides instructions on how to do this using Maven as the build tool.
142
142
143
143
=== Set up a Maven project
144
144
@@ -203,24 +203,27 @@ To implement the custom database seed provider, you must define three methods on
203
203
Additionally, you must implement a method on the nested `Dependencies` interface to resolve any dependencies required by your seed provider implementation.
204
204
205
205
Typically, the match method uses the URI scheme (the part specified before the first colon) to determine whether it can support the given URI or not.
206
-
For example, `file`, `http`, `https` etc.
206
+
For example, `file`, `http`, `https`, etc.
207
207
208
208
The stream method should implement a scheme-specific way to obtain an input stream for the backup or dump.
209
209
210
-
Implementation-specific seed configuration can be passed through from options specified in the `CREATE DATABASE` command using `seedConfig`.
210
+
Implementation-specific seed configuration can be passed through from options specified in the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/standard-databases/create-databases[`CREATE DATABASE` command using `seedConfig`].
211
+
212
+
Keep in mind that the `CREATE DATABASE` command is Enterprise Edition feature.
213
+
211
214
212
215
=== Deploy
213
216
214
-
Build a jar file from Maven and place this onto the Neo4j classpath.
217
+
Build a JAR file from Maven and place this onto the Neo4j classpath.
215
218
216
-
The jar must include a META-INF file to enable discovery of the providers with the path:
219
+
The JAR file must include a META-INF file to enable discovery of the providers with the path:
It should be a plain text file with one line for each provider contained within the jar, the line should contain the fully qualified name of the provider class.
226
+
It should be a plain text file with one line for each provider contained within the JAR file, the line should contain the fully qualified name of the provider class.
If you are using the Enterprise Edition of Neo4j in embedded mode, you have to create your database with the link:{com-neo4j-dbms-api-EnterpriseDatabaseManagementServiceBuilder}[`com.neo4j.dbms.api.EnterpriseDatabaseManagementServiceBuilder`^] to enable the Enterprise Edition features.
129
-
If you intend to operate embedded clusters, you need to provide the appropriate configuration to the instances you create (for example ports and discovery endpoints).
129
+
If you intend to operate embedded clusters, you need to provide the appropriate configuration to the instances you create (for example, ports and discovery endpoints).
130
130
For maintainability purposes, you can define your embedded DBMS configuration in the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/configuration/neo4j-conf[_neo4j.conf_] file as follows:
0 commit comments