Some suggestions for Activiti 5.0.beta1

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.

dr_pompeii

Dear Activiti's developers

I have read this link Activiti-JIRA

where appear

Versions: Due

• 5.0.beta1 Release Date: 01/Sep/10
• 5.0.beta2 Release Date: 01/Oct/10
• 5.0 Release Date: 01/Nov/10

I don't know if both links above are the unique places to know the expected or futures features or improvements for Activiti

I didn't work very deeper with Activiti yet but I want to share the follow ideas

1) Give support integration with DB PostgreSQL
2) Generalize the task/names in build.xml related with the DB, because is some confuse, I mean for example in build.properties I can do the follow.

# The db property should refer to the type of database that
# you want to use.  Currently only h2 and MySQL is supported.
db=mysql
#ORIGINAL
#db=h2

but in build.xml appear

<target name="demo.setup" depends="h2.install, h2.start,
                                     db.create,
                                     tomcat.install,
                                     deploy.activiti.engine.into.tomcat,
                               db.demo.data,
                               deploy.activiti.rest.into.tomcat,
                                     deploy.activiti.explorer.and.probe.into.tomcat,
                               tomcat.start,
                                     deploy.activiti.modeler.into.tomcat "/>

Always do reference to h2, perhaps should be
depends="db.install, db.start, to generalize the db dependencies

same appreciation for

<target name="h2.install">
     <mkdir dir="${activiti.home}/apps/h2" />
     <copy todir="${activiti.home}/apps/h2">
        <fileset dir="${activiti.home}/lib">
           <include name="h2*.jar"/>
        </fileset>
      <fileset dir="files/h2" />
     </copy>
     <chmod perm="a+x">
        <fileset dir="${activiti.home}/apps/h2">
           <include name="*.sh"/>
        </fileset>
     </chmod>
  </target>

Gives the impression that the user/developer must create a new task for mysql
like <target name="mysql.install">, thats create some confusion, of course that all works fine but I think that is fair make the build.xml totally generalized.

I know that you are in development yet, but I think important share these ideas

Let me know your thoughts

tombaeyens

for other dbs then h2, the scripts will not support install and start.  for other dbs, the scripts will assume that the db is up and running when the script runs.