Comments on: Castle demo app: ActiveRecord basics and unit testing

By: Phil Penn

Phil Penn — Fri, 29 Jan 2010 01:01:56 +0000

In case anyone else had the following problem, add NHibernate.ByteCode.Castle dll to your test project references and then the factoryclass value:

Error:
NHibernate.Bytecode.ProxyFactoryFactoryNotConfiguredException : The ProxyFactoryFactory was not configured

Amended Config:

By: Brian Mavity

Brian Mavity — Mon, 11 Aug 2008 03:33:22 +0000

Just in case anyone else has this problem. If you are using the latest castle bits, you’ll need to update your config section by removing all the “hibernate.”

So you’ll have these properties
key=”connection.driver_class”
key=”dialect”
key=”connection.provider”
key=”connection.connection_string”

Wasted 2 hours on that lol

By: Stew

Stew — Tue, 05 Aug 2008 23:09:07 +0000

I upgraded to the latest Npgsql and that seems to have broken the ice. I think I’m OK now.

Thanks again for the help.

By: Stew

Stew — Tue, 05 Aug 2008 00:12:59 +0000

Thanks for taking the time to respond.

I’m still stuck here. There is no client schema in the database right now. Here’s what the error looks like right now:

Scrumpy.Database.Test.Tests.ClientTests.TestNonUniqueUsername:
Castle.ActiveRecord.Framework.ActiveRecordException : Could not perform Save for Client
—-> NHibernate.ADOException : cannot close connection
—-> NHibernate.ADOException : Could not close Npgsql.NpgsqlConnection connection
—-> System.NotSupportedException : This stream does not support seek operations.
TearDown : System.Reflection.TargetInvocationException : Exception has been thrown by the target of an invocation.
—-> NHibernate.ADOException : cannot close connection
—-> NHibernate.ADOException : Could not close Npgsql.NpgsqlConnection connection
—-> System.NotSupportedException : This stream does not support seek operations.

All suggestions appreciated. I’m very stuck.

By: gojko

gojko — Sat, 28 Jun 2008 19:03:36 +0000

Hi Stew,

This error message suggests that your schema cannot be dropped as part of the unit test fixture set-up. Maybe some data consistency constraints are preventing you from dropping the client table (eg you have more tables in the schema, but you only loaded the Client table into AR during unit testing). Try to drop all tables in the schema manually before running the test.