[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-07-31 Thread dleerob
Okay, so I commented out the datasource, but then I get java.lang.UnsupportedOperationException: The user must supply a JDBC connection. Any suggestions? I've found somewhere on the intenet that mentioned it was a JBPM bug. If this is try, is there a workaround? View the original post :

[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-07-31 Thread kukeltje
yes commment out the datasource, but UNCOMMENT the database properties then. You should use one or the other View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069113#4069113 Reply to the post :

[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-07-31 Thread dleerob
Thank you. I thought just the header/comment for the jdbc properties was commented out, and not the entire block. Didn't notice the end comment element was at the end of the block. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069128#4069128 Reply to the

[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-07-31 Thread dleerob
Thank you, all sorted out now. Didn't notice the JDBC properties were commented out. I though just the header was. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069133#4069133 Reply to the post :

[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-07-27 Thread dleerob
Aah, thanks for pointing out that the datasource is commented out. I didn't notice that, and of course that is why I was originally getting the datasource error, which is why I ended up creating the datasource in the first place. Would of been quicker/easier to just comment it out :) View the

[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-07-26 Thread dleerob
I followed the steps on the JbpmOnTomcat wiki, however there is one step that I think you left out. It had me going for a short while, till I figured it out. By the way, I am using Tomcat 5.0.28, and MySQL 5.0.27. When I finished doing everything on the Wiki, I started up tomcat, and got an

[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-07-26 Thread mputz
anonymous wrote : There was no mention of creating this datasource in the Wiki. You are absolutely right - I never thought of creating a datasource for Tomcat, but this is a very valid approach as well. If you look at the hibernate.cfg.xml snippet in the wiki, you will notice that the

[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-03-30 Thread hipchic
Thanks it's work now !!! It would be very useful for others, if i could submit all steps i did for setup jbpm on tomcat 5.5 on the wiki. Before, to deploy the application i spend half of a day for succeed to arrive to this step. View the original post :

[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-03-30 Thread mputz
This wiki entry http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmOnTomcat already describes the steps to get jBPM 3.2 working with Tomcat 6. If you find any differences there to what you have done with Tomcat 5.5 please feel free to update the wiki. Regards, Martin View the original post :

[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-03-30 Thread hipchic
here my contribution http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmOnTomcatOracle View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4033315#4033315 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4033315

[jboss-user] [JBoss jBPM] - Re: Tomcat 5.5 - Jbpm 3.2 - Starting failed couldn't get a

2007-03-28 Thread mputz
Did you set the hibernate.dialect property in hibernate.cfg.xml? Besides the changes you have already made, there should also be an entry for the dialect. Use org.hibernate.dialect.OracleDialect for Oracle 8 and earlier, org.hibernate.dialect.Oracle9Dialect for Oracle 9 and 10. !-- SQL