Hi Liliana,

Good question, I was about to update it and write the TX-Manager but had other 
things that distracted me.
Perhaps I find time this week to finish it up.
I can't think of any other issues that should come up. 

If you use it remotely it should actually work, only not 100% as fast as 
embedded but should work without changes with the latest SDN milestone.

You can also try the super new stuff that is to be SDN 4.x, see 
http://github.com/neo4j-contrib/neo4j-ogm, You'll have to build it locally 
though.

HTH,

Cheers,

Michael

> Am 02.02.2015 um 22:14 schrieb Liliana Ziolek <[email protected]>:
> 
> Hi Michael
> 
> Are you aware of any other incompatibilities with Neo4j 2.2 except for the 
> lack of JTA? Since I only need it for some prototyping at the moment I might 
> give it a go to implement something VERY simple just to get it going. But if 
> there are 10 other issues then I think I'll either downgrade or cut out SDN 
> for now :)
> 
> I have heard that there is some new exciting stuff coming in SDN, including 
> better handling of REST-based access - definitely looking forward to it. I 
> can totally understand that there is only so much you guys can do and things 
> are moving quickly - just wanted to know where we stand.
> 
> Cheers
> Lili
> 
> On Monday, February 2, 2015 at 9:57:24 AM UTC, Michael Hunger wrote:
> Hi Liliana,
> 
> thanks for your question.
> 
> So far SDN is incompatible with Neo 2.2 as the latter removed JTA, so we will 
> have to implement a SDN side transaction manager, which I haven't gotten 
> around to but hope to get done soon.
> 
> Also there are efforts underway for a complete rewrite of SDN built on a new  
> Java OGM from scratch by our friends at GraphAware sponsored by Neo 
> Technology. We will announce publicly when the first milestone is available 
> for testing.
> That new implementation will (first) solely focus on high performance 
> interactions with Neo4j server.
> 
> Cheers, Michael
> 
>> Am 02.02.2015 um 00:05 schrieb Liliana Ziolek <[email protected] 
>> <javascript:>>:
>> 
>> Hi
>> Does anybody know what is the current state / progress of making SDN 
>> compatible with Neo4j 2.2.0 - in other words of what is the ETA of at least 
>> runnable version (can be snapshot/nightly build or whatever)?
>> 
>> I recently downloaded 2.2.0-M03 and tried running it with snapshot of SDN 
>> 3.3.0 but it crashes with:
>> 
>> java.lang.IllegalStateException: Failed to load ApplicationContext
>> [...]
>> Caused by: java.lang.NoClassDefFoundError: 
>> org/neo4j/kernel/impl/transaction/SpringTransactionManager
>>      at 
>> org.springframework.data.neo4j.config.JtaTransactionManagerFactoryBean.createTransactionManagerForOnePointEight(JtaTransactionManagerFactoryBean.java:123)
>>      at 
>> org.springframework.data.neo4j.config.JtaTransactionManagerFactoryBean.createJtaTransactionManager(JtaTransactionManagerFactoryBean.java:104)
>> [...]
>> 
>> From what I can see, SpringTransactionManager class doesn't exist in 2.2.0 
>> at all (it was there up until 2.1.6) which makes me think that SDN 3.3.0 is 
>> only meant to work with Neo4j 2.1.x.
>> Does anybody know anything about current progress (or lack of it) with 
>> porting SDN to Neo 2.2 ? I had a quick look at Github but couldn't find an 
>> obvious branch or anything.
>> 
>> Also, as a more general question. What is the official SDN status - i.e. is 
>> it considered part of Neo4j suite, supported and maintained by Neo 
>> Technology, or is it more of open source/community effort and no 
>> expectations should ever be placed on its availability? In other words, can 
>> paying Enterprise customers expect similar kind of support for it as for the 
>> main Neo4j (including that once Neo4j database goes out of milestones, there 
>> will be SDN available that actually works with it), or is it a separate 
>> product and it just happens that some people closely connected to Neo work 
>> on it as well?
>> I don't mean this question in any negative way - I just need to set up my 
>> expectations and decide if using SDN is worth the potential delays in being 
>> able to upgrade Neo4j when new versions come out.
>> 
>> Oh, and perhaps it is worth considering some more obvious versioning scheme, 
>> or at least providing a compatibility matrix on the page so that it's clear 
>> which version of SDN goes with which version(s) of Neo4j :)
>> 
>> Thanks
>> Liliana
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Neo4j" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Neo4j" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to