I have created a small database using HSQLDB and Hibernate (db.script
is about 1Mb) that I wish to include into my AppEngine webapp for
consultation purpose only, that is the database will be read from but
never written into.

While exploring and understanding the use of the "res" protocol [1] I
made a standalone program to test it and it worked as advertised.

I then proceeded to make use of that in my servlet running on
AppEngine and I hit a wall whose core is this exception:

Caused by: java.sql.SQLException: General error:
java.security.AccessControlException: access denied
(java.io.FilePermission \db.properties read)
        at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
        at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
        at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
        at org.hsqldb.jdbcDriver.connect(Unknown Source)
        at java.sql.DriverManager.getConnection(DriverManager.java:582)
        at java.sql.DriverManager.getConnection(DriverManager.java:154)
        at
org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:
133)
        at
org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:
446)
        ... 51 more

That is HSQLDB does not have access to the properties file of its
database.

My suspicion is that the server that comes with the Google Eclipse
Plugin for AppEngine and GWT is blocking access to the properties file
somehow.

1) Should this pattern (read-only HSQLDB accessed with Hibernate) be
viable on AppEngine?

2) Should it be viable, what is causing this AccessControlException?

Regards

[1] http://www.google.ca/search?q=jdbc%3Ahsqldb%3Ares%3A%3Cpath+in+jar%3E

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to