Changed the configuration:

# If you need a full JDBC configuration use the following :
db.url=jdbc:oracle:thin@//localhost:1521:mybd
db.url=jdbc:oracle:thin@localhost:1521:mybd
db.driver=oracle.jdbc.driver.OracleDriver
db.user=myusername
db.pass=mypassword

# Specify the custom JPA dialect to use here (default to guess):
jpa.dialect=org.hibernate.dialect.OracleDialect

Let me know if you solve it.
Thanks.

# If you need a full JDBC configuration use the following :
db.url=jdbc:oracle:thin@//localhost:1521:mybd
db.driver=oracle.jdbc.driver.OracleDriver
db.user=myusername
db.pass=mypassword

# Specify the custom JPA dialect to use here (default to guess):
jpa.dialect=org.hibernate.dialect.OracleDialect

But, show me this error:

Database error
A database error occured : Cannot connected to the database, La dirección URL de Oracle especificada no es válida

Well putted.. Thanks Hugo!

I have never used Hibernate-Spatial, there are a few posts in play! google groups: about it. Just give it a quick read

You have to take into account that play! uses a forked version of hibernate.

Good luck and thanks!

Thanks for the fast reply! Immediately after I submitted my doubt to you, I had a second look at my app conf and I spotted the bottom of the file the in-memory db declared for testing purposes.. I forgot to mention that I was testing the connection to the oracle db through the app’s Test Runner.. so the use of the in-memory db made sense!

I can know connect successfully to my oracle db!

Thanks for the tips anyway and it would be really nice that you continue to post here your experiences with Play! Framework! _filipera (Filipe Oliveira) explained once why he was in love with Play!… I understand know!

Well, I must continue my “fight” with Play! + Hibernate + Oracle, but now adding a variation to it: Hibernate Spatial… The HBSpatial’s ConnectionFinder needs the OracleConnection from the current Connection but it’s not getting it… Already tried several versions of the Oracle JDBC driver, but with no luck.

Any thoughts about this? =)

Stay fit & well!

By the way

Let’s try to create another configuration. On my projects, I use in-memory database when my framework id is dev.
This is good for testing experimental features where the structure of the database is changed.
Let’s create a configuration “test”:

# Database configuration
%test.db.url=jdbc:oracle:thin:@:1521:
%test.db.driver=oracle.jdbc.driver.OracleDriver
%test.db.user=cadrede
db.pass=admdev

# JPA Configuration (Hibernate)
%test.jpa.dialect=org.hibernate.dialect.Oracle10gDialect

I just added “%test” in all of your configurations

Now, when you start the play server just do the command: “play run snet –%test”
My goal with creating another id is to create a clean configuration of another environment to see if everything is well configured.

If you want to more about the framework ids, just visit: http://www.playframework.org/documentation/1.2/ids

Thanks for this useful post!

I’m facing some problems connecting my oracle db using this configuration. It seems the default H2 db is always used even the “db=mem” is comment out.

I’m getting the following output when accessing my Play!’s app

0:43:12,923 INFO ~ Listening for HTTP on port 9000 (Waiting a first request to start) …
10:43:33,368 INFO ~ Connected to jdbc:h2:mem:play;MODE=MYSQL;LOCK_MODE=0
10:43:35,589 INFO ~ Application ‘snet’ is now started !

I think I should be seen some like “Connected tojdbc:oracle:thin:@:1521:”, right?

In my application.conf, in the lines regarding the Database and JPA configuration, I havee:

# Database configuration

# JPA Configuration (Hibernate)
jpa.dialect=org.hibernate.dialect.Oracle10gDialect

What am I missing out?

Thanks, in advance!