my next tasks

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

tombaeyens

these are the tasks that i plan to do next:

* adding conditions to transitions.  adding a test that shows how it's possible to implement an exclusive gateway based on transition condition expressions

* queries.  see to what extend we still can convert the current api towards a query based objects.  our current strategy is to go for fluent query apis.  the idea would be that the Page class would be removed.  all finder methods would be replaced with createXxxxQuery methods.  when we get to implement cloud based persistence, we'll have to see to what extend these queries can be supported on the cloud.

probably by the time that's done it'll be friday 🙂

jbarrez

Agreed with first task.

For the second task, I have some remarks.
My problem is not with removing the findXXX operations, there are not so many anyway.
The issue is with the testing which is inherently complexer when using the queries - since there are multiple permutatioms of usage that
could lead to unforseen bugs. Testing the findXXX operations is easier. Otoh, the queries should be tested in depth anyway…

OK for removing the Page class. I introduced it, but never liked it and it existed ever since 😉