Anybody knows if there is an exisiting "free" AsP.NET 2.0 Membership provider that I can use implemented using NHibernate?

I guess I can use the default provider, but just thought it will be cool to make it a "pure" nhibernate application.

Thanks.

There is one here,

http://www.codeplex.com/nhibernateprovider

I checked the source out a ways back and ultimately decided it wasnt the proper approach for me, but you may think differently.

Awesome. Thanks a lot man. I just want to use pure nhibernate solution..

Although I do want to test out if transaction is possible with the provider because it will be great to have.

I have also created an open source NHibernate providers (Membership, Roles, Profiles, Forum, News...).

You can download it from:
http://www.devage.com/Wiki/ViewArticle. ... &version=0
or
http://www.codeproject.com/useritems/eucalypto.asp

Davide

Have you ever considered Spring.Net integration? I mean an integration with respect to the spring way of data dealing - abstract DAO objects, where particular case uses NH (Spring.NHibernate12 inegration project).

This introduces two benefits:
1. We can have allternative DAO implementations (we could even drop NH for other technology).
2. We can use DI for Eucalypto and DI of Eucalypto to the client code.


I've investigated your code and see that interfaces would have to be introduced + NH implementations of XXXDataStore classes in the spring way (using HibernateDaoSupport class). Also the managers would potentially require interfaces additionally. No static members would be allowed there then. There's quite a lot to do... but IMO it's worth that effort, isn't it?

I must admit that I'm not an expert of Spring.
Sometime ago I have studied the best way to implement Eucalypto (I have looked at Spring and CastleProject) but at the end I have decided to just use the ASP.NET provider pattern.

I known that Spring is more powerful (and has many more features: transactions, configuration, ...) but I think that the provider pattern is quite similar to the IoC pattern of Spring (correct me if I'm wrong).
I think that the provider pattern can be already used to implement different data access strategies and it is quite easy to use.

Consider also that I have used the provider pattern to replace the default Membership, Roles and Profiles ASP.NET classes.

What do you think?

Anyway I will look again at Spring, can be useful also for other projects ...

Davide

Ioc or dependency injection is a way to inject different providers. Provider pattern is not the same thing. They work together.

Yes I known that is not the same, but I think that both try to solve the same problem: a more flexible way to create classes and to connect the classes together.

I think that IoC is more powerful but I think that these 2 patterns are similar.
Right?


Davide

This diagram demonstrates how easy it is to integrate membership providers with spring:

http://zerek.pl/roland/Spring-Membership.emf



I have provided rough design with respect to the forum subsystem. Bellow you can see current state of Eucalypto:

http://zerek.pl/roland/Eucalypto-Current.emf

And my integration design:

http://zerek.pl/roland/Eucalypto-Spring.emf

There are potentially few changes. The use of forum (by the client code) remains unchanged. However I would be able to have several different architectures of the underlying layers of Eucalypto. And of course DI benefits.

Personally I will need this kind of the integration because I would like to have other domains in the database (that are not currently handled by Eucalypto and I want them to be handled in the spring way so the use of eucalypto is not enough for me). That's exactly why I'm asking for this integration.

Anyway - I possibly will do this integration... Any opinions and suggestions are welcome.

Cheerz :)

Great question:

Is the nhibernate provider here using the latest NHibernate 1.2 ?

I'm very interested in using this on a current solution.

Seems to be an interesting idea.

In these weeks I'm a little busy with another project and probably I need some days to be productive with Spring so I think that is better that you work on this integration. But if you want I can help you on some aspects and of course I will really appreciate if we can share the results.

In this case my only suggestion is to create a new provider so we can select the provider to use at any moment without breaking changes.
Maybe you can call it SpringForumProvider, like in this image:
http://www.devage.com/temp/EucalyptoSpringDiagram.png
If you prefer you can also work on a separate assembly.

Consider that you can access the subversion repository for the latest version of Eucalypto at this link:
https://svn.quanticosoft.com/devage/

Thanks for your suggestions and write me if you need help or you need some changes on the Eucalypto classes.
My email is: davide AT devage DOT com

Davide

Eucalypto 1.3 (currently available only on subversion but soon I will release an official version) uses NHibernate 1.2.0.4000.
Eucalypto 1.2 uses NHibernate 1.2.0.3001.

Davide