Search:

On spring-data-neo4j-2.1.0.M1.jar


Iterable<SomeClass> findByIndexedFieldAndNotIndexedField(String inIdxField, Float inNoIdxField) ;


will generate a Cypher query where the non-indexed field...

org.springframework.data.neo4j.support.typerepresentation.AbstractIndexingTypeRepresentationStrategy

@Override
public Object readAliasFrom(S propertyContainer) {
if...

I kept my first option to use UUID stored as String, the need of Binary was just for evaluation purpose, not a requirement…

http://www.springframework.org/schema/data/mongo/spring-mongo-1.0.xsd
is still referencing http://www.springframework.org/schema/beans/spring-beans-2.5.xsd.

Is that really coherent when we know...

Registering Converter and not respecting the "contract" to return the correct type is definitively not a solution for me.

We can register converter to/from String like this:


public class...

Also facing this problem,

looking in source code I have found that MongoSimpleTypes has a SUPPORTED_ID_CLASSES collection containing only: ObjectId.class, String.class, BigInteger.class

may be...

Yes that's what I discovered while reading the doc after posting the message,
but still if it solves more or less point 2 - except that writeConcern policy will affect all operations and thus the...

1. if you annotated a non @Id field with @Indexed(unique=true), then - in an NEW EMPTY collection - you insert twice the exactly same record (except the @Id) : you don't have any exception
stop your...

I repeat my previous question in another way:

You have written



not(MyAnnotation on any CarService method)


Are you sure you don't mean

just an idea:

are you sure the ! (NOT) doesn't affect the whole "@MyAnnotation * CarService.*(..)" expression and that you misinterpret it as affecting only the @MyAnnotation part ?

I would say that -Xset:weaveJavaxPackages=true looks like a JVM parameter…
and specifying a JVM parameter in a XML file that would be read after the code was loaded by the JVM, has no way to affect...

FYI:

I have tested with javassist to weave the classes afterwards and it works…



try {
BufferedInputStream fin = new BufferedInputStream(new FileInputStream("full path name the to .class...

… not sure you will be able to modify the "name" attribute of the @JoinTable annotation from your aspect…

I have tried on @Table to change the "schema" this way and it didn't worked…
but it was...

If you write a second aspect:



public aspect StaticEntityInitAspect pertypewithin(YOUR_ENTITIES_PACKAGE.*) {

pointcut atentity() : staticinitialization(*) ;

after() returning :...

There is no solution yet…
Just thinking in different paths that could lead to a solution…

currently I don't find a way to make "TO_BE_PARAMETRIZED" a dynamic expression…

So


declare @field: @ManyToMany * * : @JoinTable(
name=TO_BE_PARAMETRIZED,
inverseJoinColumns=@JoinColumn(name="user_id") ) ;

could be a "kind of of" solution…
if there was a way to...

@ManyToMany needs a join table of which name can be specified in following
@JoinTable using "name" attribute… with no "name" attribute… the name is generated according to enclosing class name and...

"AspectJ provides a construct—declare precedence—for controlling aspect prece- dence. The declare precedence construct must be specified inside an aspect. The construct takes the following form:...

Why going thru getClass().getMethod() while the JP signature should be a CodeSignature and thus has the getParameterTypes() method ?

CodeSignature cs = (CodeSignature)jp.getSignature();...

Strange but here it doesn't work as expected…

I had to make 2 changes in the Java code:



public Object nullSafeGet( ResultSet resultSet, String[] names, Object owner ) throws...

If you don't mind mixing .aj aspect and @Aspect in your project :



package __SET_YOURS__;

import javax.annotation.Resource;
import java.lang.reflect.Field ;

import...

Indeed a often seen problem in various situations… (like web services…)

a quick and easy way to detect this kind of problem is to log the execution of the constructors…
once you see the same bean...

By using a PropertyPlaceholderConfigurer


<bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property...

the user on the DB side will be the one used to connect (== the JDBC login…)
not the application user as used for Acegi or the like…

With Hibernate, I do this with a


<property...

prior to version 3.0, you have also to include the spring-security-core-tiger.jar