[jboss-user] [jBPM Users] - Re: JBPM 4.x using Sybase ASE 11/12 on Jboss 5.1.0GA

[HelloW]

kukeltje: hehehe. yep i think so as well
jbarrez: That's what i thought. do you mean this file -> {jboss.home}\server\default\deploy\jbpm\jbpm-service.sar\jbpm.hibernate.cfg.xml

my file currently looks like this: 


  | <?xml version="1.0" encoding="utf-8"?>
  | 
  | <!DOCTYPE hibernate-configuration PUBLIC
  |           "-//Hibernate/Hibernate Configuration DTD 3.0//EN"
  |           "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
  | 
  | <hibernate-configuration>
  | 	<session-factory>
  | 
  |         <property name="hibernate.dialect">org.hibernate.dialect.SybaseDialect</property>
  | 		<property name="hibernate.connection.datasource">java:JbpmDS</property>
  | 		<property name="hibernate.connection.username">jbpmtest</property>
  | 		<property name="hibernate.connection.password">jbpmtest</property>
  | 		<property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
  | 		<property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property>
  | 		<property name="jta.UserTransaction">UserTransaction</property>
  | 
  | 		<mapping resource="jbpm.repository.hbm.xml" />
  | 		<mapping resource="jbpm.execution.hbm.xml" />
  | 		<mapping resource="jbpm.history.hbm.xml" />
  | 		<mapping resource="jbpm.task.hbm.xml" />
  | 		<mapping resource="jbpm.identity.hbm.xml" />
  | 
  | 	</session-factory>
  | </hibernate-configuration>
  | 

i added these two lines to try force the user but still no luck:

  | <property name="hibernate.connection.username">jbpmtest</property>
  | 		<property name="hibernate.connection.password">jbpmtest</property>
  | 

Funny thing is that if I use mySQL (instead of sybase) then it appears to work save for a similar error. It complains of a user called 'sa'@localhost not existing. If I add the two lines to the hbm file then it either works with that user or I have to manually create a user 'sa' with no password and the error disappears.

I suspect the reporting engine is being a weird with the user/pass it uses for the db. Any clue how to force it to use a specific user/pass (apart from adding those two lines - assuming that is not the right solution)?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255542#4255542

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255542