<?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 Re: pvm will be moved into engine in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/pvm-will-be-moved-into-engine/m-p/5381#M864</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Ok, I'll defer adding the OSGi metadata to the jars until the refactoring is done then.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Oct 2010 07:48:14 GMT</pubDate>
    <dc:creator>gnodet</dc:creator>
    <dc:date>2010-10-22T07:48:14Z</dc:date>
    <item>
      <title>pvm will be moved into engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/pvm-will-be-moved-into-engine/m-p/5380#M863</link>
      <description>after some reflection and seeing the disadvantages of extracting pvm as a separate module, we came to the conclusion that pvm should be merged into the engine.in the future, the interpretation algorithm should work against interfaces (instead of the impl objects).&amp;nbsp; that way we can build separate run</description>
      <pubDate>Thu, 21 Oct 2010 16:30:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/pvm-will-be-moved-into-engine/m-p/5380#M863</guid>
      <dc:creator>tombaeyens</dc:creator>
      <dc:date>2010-10-21T16:30:17Z</dc:date>
    </item>
    <item>
      <title>Re: pvm will be moved into engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/pvm-will-be-moved-into-engine/m-p/5381#M864</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Ok, I'll defer adding the OSGi metadata to the jars until the refactoring is done then.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Oct 2010 07:48:14 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/pvm-will-be-moved-into-engine/m-p/5381#M864</guid>
      <dc:creator>gnodet</dc:creator>
      <dc:date>2010-10-22T07:48:14Z</dc:date>
    </item>
    <item>
      <title>Re: pvm will be moved into engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/pvm-will-be-moved-into-engine/m-p/5382#M865</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;@tom: Could you quickly summarize the disadvantages of extracting PVM as a separate module?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Oct 2010 15:07:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/pvm-will-be-moved-into-engine/m-p/5382#M865</guid>
      <dc:creator>falko_menge</dc:creator>
      <dc:date>2010-10-25T15:07:30Z</dc:date>
    </item>
    <item>
      <title>Re: pvm will be moved into engine</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/pvm-will-be-moved-into-engine/m-p/5383#M866</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;* we had to build in many polymorphic methods in the pvm classes so that we can inject special behavior in the engine.&amp;nbsp; implementation of lazy initialization hooks in the base class is really unreadable and unmaintainable&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;* one other situation now arises where the pvm uses a classloader.&amp;nbsp; in the engine we want to make the classloader configurable.&amp;nbsp; but in the pvm, we can't access the process engine configuration.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;* variables in the pvm are stored in a Map&amp;lt;String, Object&amp;gt;.&amp;nbsp; then in the engine we provided a VariableMap implements Map&amp;lt;String, Object&amp;gt; that translates all the values into persistable VariableInstance.&amp;nbsp; Because the PVM uses the map api, we cannot introduce backpointers from VariableInstance to execution easily or do other engine specific stuff with variables.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;* we now have figured out a new strategy for dealing with different environments.&amp;nbsp; if we extract the interfaces of the model that the interpretation algorithm needs, then we can build different domain models and still have one engine to interprete those different models.&amp;nbsp; then we can build a plain pojo model, a dedicated mybatis persistence model, a cloud model etc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;those are the ones that I recall from the top of my head&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Oct 2010 15:58:53 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/pvm-will-be-moved-into-engine/m-p/5383#M866</guid>
      <dc:creator>tombaeyens</dc:creator>
      <dc:date>2010-10-25T15:58:53Z</dc:date>
    </item>
  </channel>
</rss>

