Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I am looking for a OGM for OrientDb - something that will allow me to persist my domain model (POJO) as vertices and edges declaratively (using annotations perhaps). I stumbled upon Ferma which seems to have the annotations support but I can't find many examples to go on. Specifically, how do I create/initialise a Ferma FramedGraph from an OrientGraphFactory?
This lack of enough samples/documentation also makes me doubt the support for Ferma. I am new to graph databases. Am I on the right track? Are OGM/ORM not the right way to go for graph databases or am I just looking at the wrong OGM? Coming from the RDBM world I am looking for a stack like: OrientDb -> TinkerPop3 Frames -> anOGM where anOGM is an actively maintained fast(preferably compile time code generation) OGM/ORM with wide community support. Something like neo4j-ogm.
Yes, JPA has spoiled me!!.
Currently, the most active OGM for TinkerPop 3.x that I know of for Java is the recently announced gremlin-ogm. You also have the option of building a Gremlin DSL which has a similar goal of mapping the domain of the graph to the query language. You can read more about that here in this blog post as well.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I am using MireDot for generating documentation for my REST service.
While it is awesome for generating the models and general information on the resources, I don't believe it currently has a way of "nicely" adding concrete example input/output.
That said, I am resorting to pure JavaDoc for writing the Json examples. And it's painful.
Does anybody know of any tool out there that helps write JavaDoc... and in particular makes it easy to insert formatted JSON/etc into it?
This is an old question I posted when I was just experimenting with ways to document an API.
Eventually I switched to Apiary over MireDot, which makes this task trivial. The reason for this transition was mostly to decouple the JavaDoc from the actual API documentation, as I found coupling those two can create a very messy code-base for a sophisticated API that requires a lot of documentation.
Ideally would have built documentation using an all-encompassing API management platform like Mashery or the like, but at the time that was not an option.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I am looking for JAXB classes (XML binding for Java) to represent the JIRA REST API - preferably for the current version (6.1.4, though our atlassian.net site says JIRA v6.2-OD-03), although I can update an older version as needed.
Background:
I'm working on a simple Java service that searches JIRA for issue details and compiles custom reports for our team. We have a quick 'n dirty set of JAXB classes, but they're both cluttered and incomplete. The full set of things returned is heavily nested JSON and not trivial to represent with JAXB. I'd love to have an existing implementation (official or otherwise) to help minimize my effort.
Searching for info on this is overly cluttered with info on using JAXB in a JIRA plugin, which is entirely unrelated my issue but apparently much more commonly done.
While searching for something else entirely, I came across the JIRA REST Java Client page. It has almost exactly the classes I'm looking for, though I'll have to modify them to work with JAXB and not require some of their project dependencies.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I'm looking for an open source, Java-based database that ...
can be easily extended, e.g. by implementing various forms of trees (R-tree, etc.), various indexing techniques (BitMatrix, etc.), new operations and fields
does a good (fast) job at reading data, e.g. for reading time series
is well documented
I looked at (in other threads suggested) Apache Derby and BerkleyDB already; at the moment I'm in favor of BerkleyDB since it seems to be faster than Derby. Do you have any further preferences or any arguments for or against a database.
I never tried to extend it but H2 database seems to be one of the most flexible and vibrant projects at this time.
It uses interfaces in many places which makes it simple to drop in your own implementation, for example for custom tables.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I'm about to implement a state machine based workflow in my app and I've encountered an interesting framework that could make this task easier - http://code.google.com/p/stateless/
Sadly, it's for C# only.
Does anyone know about a similar workflow framework for Java? I'm afraid integrating Drools would take a lot more time than I can afford, I need something lightweight like the Stateless framework.
You can try
http://unimod.sourceforge.net/fsm-framework.html
http://today.java.net/pub/a/today/2006/01/04/business-processes-with-osworkflow.html
http://jakarta.apache.org/site/downloads/downloads_commons-scxml.cgi
http://springframework.org/webflow
http://www.jboss.org/jbpm
http://www.complang.org/ragel/
http://today.java.net/article/2009/09/06/finite-state-machine-supporting-concurrent-states
Or instead of using a framework, you can use an enum to do it (which is what I do)
http://vanillajava.blogspot.com/2011/06/java-secret-using-enum-as-state-machine.html
We have been using Stateless in our .NET which now needs to go Java for prod servers. This is what we are going with (note W3 and apache commons):
http://www.w3.org/TR/scxml/
http://commons.apache.org/proper/commons-scxml/
http://www.javacodegeeks.com/2012/06/apache-commons-scxml-finite-state.html
Have you checked the Java Finite State Machine Framework? looks simple enough. And agreed, Drools would be overkill -. and besides, it's more of an inference engine (although it can be used as a workflow component).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
Has anyone used, implemented, knows or just have heard of any graph (especially RDF) to object mapping frameworks for java.
We are evaluating frameworks at the moment.
So far we have:
KMS
JenaBean
Alibaba
Elmo
Tinkerpop Stack - Especially Blueprints and Frames
Empire
Spring Data Graph
jo4neo
Callimachus Project
There is also RDF2Go, which has has RDFReactor.
I remember that Elmo is very nicely done, using only interfaces for class definitions, and java-proxy objects for the implementations allow quite clean multiple inheritance...
In general though I wonder if these frameworks really are worth it. The theory is that they hide the "complexity" of RDF and allow normal java programmers to work with RDF - but in the process they also hide one of the main benefits of RDF, being able to deal with data-structured not known at compile time.
The "schemalessness" of RDF is great for small projects, or for extending normal schemas, and of course RDFS offers a way to formalise and standardise your new properties/classes when you need to. As Kendall Clark says "Correctness when it matters; sloppiness when it doesn’t". If you pre-generate all your object interfaces from a schema you lose all this - of course you could have a generic bean interface at the top (i.e. DynaBean) which would let you query for properties not in your scheam, but then you could just as well just use the Jena OntResource.