database audit capabilities in iBatis?

[Jesus Mirabal <jm...@investran.com>]

Hello,

 

I have posted a couple of emails to this list since we began to evaluate
and prototype iBatis. I work for a considerable large software company
that provides solutions for renowned financial institutions. We are in
the verge of embarking in a big project that includes the architecture
renovation of one of our product suites.

Obviously, we are taking iBatis, as well as NHibernate in consideration
to be the foundation of our Data Access Layer.

 

For various reasons we have been more inclined towards the iBatis
implementation. However, we are facing a couple of problems we have to
resolve before taking a definitive decision.

 

One of the requirements we have is to collect audit information at the
field level in the database. We have our own implementation to provide
such behavior. Our implementation is based on the Castle Project Windsor
Container, taking advantage of IoC, interceptors, etc. The more
restricted nature of iBatis, compared with the extensibility of
NHibernate creates some problems for us to intercept the properties Set
accessor. In the middle of this, I was wondering if adding database
audit capabilities to a framework like iBatis would make sense. This
could be a really nice feature I'm almost sure a lot of DAL developers
could take advantage from. But in any case, my intention is to try and
brainstorm with you guys about the different possibilities we have to
accomplish such audit capabilities with iBatis.

 

I hope we get some ideas from this community. If necessary we could
share more details of our specific implementation so far.

 

Thanks in advance for your cooperation,

 

J. Mirabal

 


CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you.

Re: database audit capabilities in iBatis?

[Gilles Bayon <ib...@gmail.com>]

I see 3 solutions :

1/ third party tool
2/ use your own ISetAccessorFactory (set the property SetAccessorFactory
on DomSqlMapBuilder before launch Configure)
3/ Once the DaTaMapper is build, decorate the IProvider (CreateCommand) of
the DataMapper.DataSource so that it give you a decorate IDDbCommand which
log parameters on the Excute* method

Cheers
Gilles

On 8/7/06, Jesus Mirabal <jm...@investran.com> wrote:
>
>   Hello,
>
>
>
> I have posted a couple of emails to this list since we began to evaluate
> and prototype iBatis. I work for a considerable large software company that
> provides solutions for renowned financial institutions. We are in the verge
> of embarking in a big project that includes the architecture renovation of
> one of our product suites.
>
> Obviously, we are taking iBatis, as well as NHibernate in consideration to
> be the foundation of our Data Access Layer.
>
>
>
> For various reasons we have been more inclined towards the iBatis
> implementation. However, we are facing a couple of problems we have to
> resolve before taking a definitive decision.
>
>
>
> One of the requirements we have is to collect audit information at the
> field level in the database. We have our own implementation to provide such
> behavior. Our implementation is based on the Castle Project Windsor
> Container, taking advantage of IoC, interceptors, etc. The more restricted
> nature of iBatis, compared with the extensibility of NHibernate creates some
> problems for us to intercept the properties Set accessor. In the middle of
> this, I was wondering if adding database audit capabilities to a framework
> like iBatis would make sense. This could be a really nice feature I'm almost
> sure a lot of DAL developers could take advantage from. But in any case, my
> intention is to try and brainstorm with you guys about the different
> possibilities we have to accomplish such audit capabilities with iBatis.
>
>
>
> I hope we get some ideas from this community. If necessary we could share
> more details of our specific implementation so far.
>
>
>
> Thanks in advance for your cooperation,
>
>
>
> J. Mirabal
>
>
> CONFIDENTIALITY: This email (including any attachments) may contain
> confidential, proprietary and privileged information, and unauthorized
> disclosure or use is prohibited. If you received this email in error, please
> notify the sender and delete this email from your system. Thank you.
>



-- 
Cheers,
Gilles

<a href="http://www.amazon.com/gp/registry/6JCP7AORB0L">Wish List</a>