Java Stardog Libs

[Agustín Martínez]

Hi everyone. I need to code a simple prototype in Java but I'm a little confused with the stardog libraries I have to include in my project. Initially I've included all the libs located in stardog/client folder (excepting jena). Obviously the project runs, but I really wanna know what it's the objective of each one: 

• /client 
  
• /api
• /cli
• /empire
• /http
• /snarl (this it's what I use for the information exchange)
• /sesame
• /pack
• /server
  
• /dbms
• /http
• /pack
• /snarl

Regards,

Agustín

[Al Baker]

The API is the top level API, of which you need at least one protocol driver (snarl, or HTTP), empire is our JPA interface, Sesame and Jena are obvious, and pack is the clustering support in Stardog 2.2.1 and later.  Server side is just the server side components of all of the above.  For embedded server applications, you need all of the jars in the server folder on the class path, and my favorite way of accomplishing that is using Gradle and the fileTree dependency declaration, but anything will do.

If you’d like to see more on client dependencies, the Maven dependencies are available via the “mavenInstall” script, and then you can use any build tool you like that can pull from your local maven repository (Maven, Ivy, Gradle, Leiningen, etc).

There’s also a listing of the top level dependencies and the client type in the docs:

http://docs.stardog.com/java/#sd-Support-for-Maven

Cheers,

Al 

--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+u...@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en

[Agustín Martínez]

Excellent. Thanks for the quick response!

Agustín

Universidad Tecnológica Nacional - Facultad Regional Santa Fe

-------------

CIDISI - Centro de Investigación y Desarrollo de Ingeniería en Sistemas de Información