I'm trying to upgrade a project to Spring Data Neo4j 4.0.0 and I'm facing two problems :
The "spring-data-neo4j-rest" package is missing at MvnRepository (spring-data-neo4j-rest-4.0.0.jar returns 404 error). Does the package still exist and should be there, or should I just delete the dependency from my pom.xml?
I've got the following error : The method fetch(Set<...>) is undefined for the type Neo4jOperations in all my DAOs. The method was used to initialize collections of lazily loaded nodes. How can I initialize a node's collections?
Thanks!
Did you read the migration guide that's provided for SDN 4?
http://docs.spring.io/spring-data/neo4j/docs/current/reference/html/#migration
fetch is gone and replaced by fetch-depth
SDN-rest is gone too any not needed anymore (as SDN-4 is all about remote connections).
Related
My project recently upgraded grails from 2.0.0 to 2.4.3. In a domain object I am using the email validation constraint. I've noticed in testing that emails with fake tlds eg 'fake#fakedomain.tld' are now considered invalid. Grails documentation says it is using Apache Commons EmailValidation class to do the validating. That documentation explicitly states that it doesn't check for valid tlds.
Has anyone else seen this issue, and if so was there a simple work around? I am on the fence between a custom validator that allows invalid tlds or removing the constraint all together.
It would appear that the new Commons Vaidator v1.4.0 which is used by Grails v2.4.3 has an open bug VALIDATOR-338 where unknown TLDs in e-mail addresses are invalid. This only effects 1.4 and not 1.3.1 which Grails 2.0.0 used.
The quickest route would be to implement a custom validator for now. You might even get away with using a custom regular expression (of which there are many examples of).
I recently updated my grails project from 2.0.4 to 2.3.6, which is giving some errors while saving a form which contains multipart data (file attachments),
Its giving me the error for the file attachment fields like rejected value: grails.validation.ValidationException: Validation Error(s) occurred during save():
And its giving me the error in Requestmap.groovy as well, below is the error
Requestmap.url.unique.error
In version 2.0.4, its working fine without any errors.
How to resolve these issues?
Grails documentation contains tips on updating from one version to another. In your case you are making a large jump so you may have to refer to the following:
Upgrade from versions previous to 2.2
Upgrade from 2.2 to 2.3
Both issues you have are validation errors. You can see the validation errors in detail by executing:
Requestmap requestmap = new Requestmap([...])
requestmap.validate()
println requestmap.errors
You can find additional details about validation errors in the docs.
I have something weird going on when I'm trying to setup the Doctrine Extensions and the Stof Doctrine Extensions bundle. After I followed the tutorial by Stof, I get an error that he doesn't know stof_doctrine_extensions in the config.yml. Also in the list of namespaces he doesn't exist (that the terminal shows on that kind of error).
Does somebody got the same problem? Do I need a specific branch... I'm using Symfony 2.0.x with Doctrine 2.1.6.
Thanks!
You need to upgrade to Symfony 2.1.* for this bundle to work.
https://github.com/stof/StofDoctrineExtensionsBundle/blob/master/Resources/doc/index.rst#bring-in-the-vendor-libraries
I'm moving my application from Structure Map 2.5.3 to 2.6.2 and I'm having some scoping problems.
In 2.5.3 version I used CacheBy(InstanceScope.HttpContext) to have instances disposed at the end of Http request. Now in 2.6.2 I tried both HybridHttpOrThreadLocalScoped and HttpContextScoped but my injected instances do not get disposed.
Any solutions?
Those classes which were not disposed were in another project still referencing 2.5.3. It works fine now after fixing the references :)
I have AS (as a plugin) working in another app just fine (I dont remember this
issue...) - its also using Rails 2.3.9, on same dev box.
Now trying to add it to a new app and getting this error when running
the webrick, script/server:
/Users/kimptoc/.rvm/gems/ruby-1.8.7-p302/gems/activesupport-2.3.9/lib/
active_support/core_ext/module/aliasing.rb:33:in `alias_method':
undefined method `number_of_pages' for class `Paginator' (NameError)
from /Users/kimptoc/.rvm/gems/ruby-1.8.7-p302/gems/
activesupport-2.3.9/lib/active_support/core_ext/module/aliasing.rb:
33:in `alias_method_chain'
from /Users/kimptoc/Documents/ruby/borisbikestats/vendor/plugins/
active_scaffold/lib/extensions/paginator_extensions.rb:9
I couldn't find any previous references to this error.
Embarassingly I dont know which version of AS I am using successfully... it says 1.2RC1 in the CHANGELOG file, but I seem to remember trying a few of the forks...(is there somewhere I can see which fork is in use...). I have tried using the the 'main' activescaffold in the new project, but it fails as above, but so does using the same plugin that is in the working project :(
Thanks in advance for any pointers as to what I am doing wrong.
Thanks,
Chris
PS Just realised that new Rails was using Rails 3 and old/working one was 2.3.9. It seems you need to use an alternate branch of AS for Rails 3, like this : https://github.com/vhochstein/active_scaffold/wiki
This is just a guess, but built in pagination was removed in Rails 2 as I recall, and you needed to install the classic_pagination plugin to get that functionality back.
I only used ActiveScaffold once, but the error there says paginator_extensions.rb ... it's probably monkey patching the old Rails paginator? Therefore the class exists but the number_of_pages method doesn't.