Castle's NHibernate Bytecode Provider

[G. Richard Bellamy]

I’m curious what the status is of the NH bytecode provider from the Castle perspective (if there is one). From what I’ve read, the NH team is no longer supporting the various Bytecode providers, and is going with a default of using LinFu for their ProxyFactoryFactory (I guess this really means they’re no longer supporting the Spring and Castle bytecode providers).

 

http://groups.google.com/group/nhusers/browse_thread/thread/d22172aec62a2ddd/d6a8898a1204fc8f?lnk=gst&q=bytecode#d6a8898a1204fc8f

http://stackoverflow.com/questions/5728622/nhibernate-bytecode-providers-source

 

-rb

[Mauricio Scheffer]

Is there any real advantage in using and maintaining the Castle bytecode provider (over the new default one, that is)? If it's worth maintaining, it could be moved to NHibernate.Contrib or as a Castle contrib project.

--

Mauricio

--
You received this message because you are subscribed to the Google Groups "Castle Project Users" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.

[G. Richard Bellamy]

The ProxyFactoryFactory is configurable in NH. This allows the developer to choose whether or not all proxies are generated by the same provider.

 

I’m not sure that’s a convincing argument, but there you go.

 

-rb

[Mauricio Scheffer]

Yes, I'm well aware of that, but just because it can be done doesn't mean it provides any real value. IMHO it's not worth maintaining it...

--

Mauricio

[G. Richard Bellamy]

“IMHO it’s not worth maintaining it…” is what I was interested in.

 

Thanks,