Re: [jira] [Created] (ZEST-131) OSGi doesn't work anymore

One thought I suspect this is broken due to a lack of tests. This made me think is there any standard way of handling more complex test environments in apache-land? Such as using docker/vagrant to manage a container, where we launch an application server, deploy a test application insi

Re: Inconsistency between indexers and stores?

Den 14-12-2015 kl. 03:55 skrev Niclas Hedhman: > I think that the key to solving this problem is creation of testcases that > highlights the many problems. And I don't think I am capable of making > those on my own, we need a collaborative effort here... > > S, I have pushed a new branch ZEST-1

[jira] [Commented] (ZEST-132) Improve Indexing/Query Semantics

[ https://issues.apache.org/jira/browse/ZEST-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055451#comment-15055451 ] Kent Sølvsten commented on ZEST-132: There are 2 motivations for this: * More consisten

Re: Inconsistency between indexers and stores?

I think that the key to solving this problem is creation of testcases that highlights the many problems. And I don't think I am capable of making those on my own, we need a collaborative effort here... S, I have pushed a new branch ZEST-132, which currently is 'develop', but I want this branch

[jira] [Commented] (ZEST-132) Improve Indexing/Query Semantics

[ https://issues.apache.org/jira/browse/ZEST-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055339#comment-15055339 ] Niclas Hedhman commented on ZEST-132: - Further, the whole Indexing/Query subsystem seems

[jira] [Resolved] (ZEST-123) Remove Zest Base64Encoder in favor of the Java 8 one.

[ https://issues.apache.org/jira/browse/ZEST-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman resolved ZEST-123. - Resolution: Fixed Simple fix. > Remove Zest Base64Encoder in favor of the Java 8 one. > ---

[jira] [Closed] (ZEST-123) Remove Zest Base64Encoder in favor of the Java 8 one.

[ https://issues.apache.org/jira/browse/ZEST-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed ZEST-123. --- > Remove Zest Base64Encoder in favor of the Java 8 one. > --

[jira] [Created] (ZEST-132) Improve Indexing/Query Semantics

Niclas Hedhman created ZEST-132: --- Summary: Improve Indexing/Query Semantics Key: ZEST-132 URL: https://issues.apache.org/jira/browse/ZEST-132 Project: Zest Issue Type: Bug Reporter:

Re: Inconsistency between indexers and stores?

On Mon, Dec 14, 2015 at 5:29 AM, Kent Sølvsten wrote: > For querying the current status is much more complex. > > (3a) I can query for an existing entity, if i can see it's model, *and* > i can see an indexer, *and* the entitystore in which the entity is > persisted can see the same indexer. >

[jira] [Updated] (ZEST-120) Figure out the semantics for Default Methods in interfaces

[ https://issues.apache.org/jira/browse/ZEST-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman updated ZEST-120: Description: The introduction of default methods in Java 8 has impact on Zest. * What semantics sh

[jira] [Updated] (ZEST-94) Support for Pluggable Types

[ https://issues.apache.org/jira/browse/ZEST-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman updated ZEST-94: --- Summary: Support for Pluggable Types (was: Better support for custom basic types) > Support for Pluggab

[jira] [Updated] (ZEST-43) Solr Indexing has dependency on RDF library

[ https://issues.apache.org/jira/browse/ZEST-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman updated ZEST-43: --- Summary: Solr Indexing has dependency on RDF library (was: Solr Indexing has dependency in RDF library)

[jira] [Assigned] (ZEST-123) Remove Zest Base64Encoder in favor of the Java 8 one.

[ https://issues.apache.org/jira/browse/ZEST-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned ZEST-123: --- Assignee: Niclas Hedhman > Remove Zest Base64Encoder in favor of the Java 8 one. >

[jira] [Updated] (ZEST-124) Replace Joda Time with Java 8 Time API

[ https://issues.apache.org/jira/browse/ZEST-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman updated ZEST-124: Description: If we are going with Java 8, AND support pluggable types, then I think we should drop the

Jenkins build is back to normal : Zest(JavaEdition)-develop-java8-check #125

See

Re: Inconsistency between indexers and stores?

I see, I need to be more precise :-) I have (currently) no intention to change the flow for saving/updating/get'ing/finding entities. What i would like to change is the algorithm for selecting *which* indexer is used for querying (in a setup with multiple indexers). The "Closest Entity Store" is

Re: Inconsistency between indexers and stores?

I think this is a topic that needs a few brains and a whiteboard. The "Closest Entity Store" is not a concept that makes sense to me right now, as we have only worked with Visibility rules. That said, the query process should in my opinion be very straight forward; The returned values are ONLY Id

Inconsistency between indexers and stores?

Hi We seem to have som inconsistencies between indexers and entitystores. When we get() an entity, it is fetched from the EntityStore that is "closest" to the corresponding EntityModel. When we save an entity, it is persisted in the EntityStore that is "closest" to the corresponding EntityModel.