<defaults>
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>Hypersonic SQL</datasource-mapping>
</defaults>
which I believe is a wart.
So if you have set your DefaultDS to be postgres, then jetty is still trying to use
hsqldb mappings with it.
Steve
On Wednesday, November 20, 2002, at 02:31 PM, Rick LaBanca wrote:
I thought along the same lines as you. I'm not doing anything myself,
whatever the jetty cmp is doing triggers this, and the site isn't running
yet, this is initialization. I am pretty sure it's using the postgres map,
but it sure seems likely that I have something wrong in this area if it
works for others. All I changed was the jboss-servicecmp (or whatever it is
in conf, not at work to look right now) to point to postgres at the top, and
put in my postgres.xml (and remove hsqldb).
Postgres actually isn't necessary, I may just punt and try to figure out how
to get an hsqldb running and just go with the flow!
Are you by any chance mixing up the JDBC type mappings with the SQL
type mappings?
VARBINARY is a JDBC type, and BYTEA is an SQL type. JBoss needs the SQL
type so
that it can create the table. After that is uses the JDBC type as far
as I know.
The message suggests that you're trying to use VARBINARY as an SQL type.
Coincidentally, VARBINARY is an hsqldb SQL type. Maybe you're somehow
using a postgres
datasource with hsqldb mappings (which are the default)?
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
