|
[
Permlink
| « Hide
]
Shay Banon added a comment - 29/Jul/09 10:16 AM
In that same thread it was suggested that the new GAE version does support it. Maybe it makes sense to verify that this issue still applies to the latest GAE.
I'm afraid the issue at least partly still applies. It may be that the fully qualified path name is no longer a requirement but the trailing 'x' still appears to be. I updated the thread with my tests on this, will feedback any more info I find.
I have just committed a fix to add the trailing x in the DatanucleusJpaEntitiesLocator. I will kick a nightly build, can you give it a go?
Good news! That seems to have done the trick
![]() For the record this is the device configuration I'm using. {{ compass = new CompassConfiguration() compassGps = new SingleCompassGps(compass); CompassGpsDevice device = new JpaGpsDevice("appengine", emfInstance); ((JpaGpsDevice) device) compassGps.addGpsDevice(device); if(compass.getSearchEngineIndexManager().isLocked()){ compass.getSearchEngineIndexManager().releaseLocks(); } compassGps.start(); //compassGps.index(); }} Great stuff!. Can you post your Key converter (I think you posted it in the forum somewhere)? I will add it as a built in feature in Compass...
Sure, happy to be of help.
— import org.compass.core.converter.ConversionException; import com.google.appengine.api.datastore.Key; /**
@Override @Override } (sorry about the formatting, got a bit messed up posting through jira)
|