[
https://issues.apache.org/jira/browse/PROVISIONR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686521#comment-13686521
]
Rahul Sharma commented on PROVISIONR-9:
---------------------------------------
I am still working on it. I have changed the driver but I keep getting
Serialization exception while creating/using pool. Postgres drivers are not
osgi friendly so I have taken progres(8.3.604) bundle from springsource. After
using this Activti is able to connect/use postgres but while using
provisinior;pools command I get :
Caused by: java.io.StreamCorruptedException: invalid stream header: BB656430
at
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801)[:1.7.0_13]
at
java.io.ObjectInputStream.<init>(ObjectInputStream.java:298)[:1.7.0_13]
at
org.activiti.engine.impl.variable.SerializableType.getValue(SerializableType.java:48)[89:org.activiti.engine:5.10.0]
This works fine in activiti test cases like ListActivitiCommandTest etc. I
still need to figure out what is causing this.
Also I was thinking of exposing the setting in form of JDBC parameters and
using them via Spring-jdbc. This would allow us switching between different
databases using the same set of parms with different values. But unfortunately
spring jdbc bundle does not have an import-package for postgres, so got stuck
there.
Any thoughts ?
> Test with PostgreSQL as a database
> ----------------------------------
>
> Key: PROVISIONR-9
> URL: https://issues.apache.org/jira/browse/PROVISIONR-9
> Project: Provisionr
> Issue Type: Test
> Components: Activiti, Core
> Affects Versions: 0.5.0-incubating
> Reporter: Andrei Savu
> Assignee: Rahul Sharma
>
> Right now we are only supporting & testing H2 as a database for state
> persistence. Activiti supports a large number of database and we should test
> that we have the right configuration mechanisms in place and the right .jar
> files on the classpath to make it easy to use a different one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira