<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic my next tasks in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/my-next-tasks/m-p/22559#M10835</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;these are the tasks that i plan to do next:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;* adding conditions to transitions.&amp;nbsp; adding a test that shows how it's possible to implement an exclusive gateway based on transition condition expressions&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;* queries.&amp;nbsp; see to what extend we still can convert the current api towards a query based objects.&amp;nbsp; our current strategy is to go for fluent query apis.&amp;nbsp; the idea would be that the Page class would be removed.&amp;nbsp; all finder methods would be replaced with createXxxxQuery methods.&amp;nbsp; when we get to implement cloud based persistence, we'll have to see to what extend these queries can be supported on the cloud.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;probably by the time that's done it'll be friday &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 25 May 2010 20:12:41 GMT</pubDate>
    <dc:creator>tombaeyens</dc:creator>
    <dc:date>2010-05-25T20:12:41Z</dc:date>
    <item>
      <title>my next tasks</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/my-next-tasks/m-p/22559#M10835</link>
      <description>these are the tasks that i plan to do next:* adding conditions to transitions.&amp;nbsp; adding a test that shows how it's possible to implement an exclusive gateway based on transition condition expressions* queries.&amp;nbsp; see to what extend we still can convert the current api towards a query based objects.&amp;nbsp; ou</description>
      <pubDate>Tue, 25 May 2010 20:12:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/my-next-tasks/m-p/22559#M10835</guid>
      <dc:creator>tombaeyens</dc:creator>
      <dc:date>2010-05-25T20:12:41Z</dc:date>
    </item>
    <item>
      <title>Re: my next tasks</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/my-next-tasks/m-p/22560#M10836</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Agreed with first task.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For the second task, I have some remarks. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;My problem is not with removing the findXXX operations, there are not so many anyway.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The issue is with the testing which is inherently complexer when using the queries - since there are multiple permutatioms of usage that&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;could lead to unforseen bugs. Testing the findXXX operations is easier. Otoh, the queries should be tested in depth anyway…&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;OK for removing the Page class. I introduced it, but never liked it and it existed ever since &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 May 2010 20:30:47 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/my-next-tasks/m-p/22560#M10836</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2010-05-25T20:30:47Z</dc:date>
    </item>
  </channel>
</rss>

