> > > Has there been interest in creating a J2EE style architecture for > > > C#/.NET? We can make it "better" because we can make the beans self > > > describing using attributes. No need for XML descriptors :D. > > > > > > > This is what System.EnterpriseServices does. > > Not really. System.EnterpriseServices is basically a band-aid on top of > COM+. The only reason it exists is that MS ran out of time and chose to > ship .NET without a new distributed Tx architecture. Of all the things > in .NET System.EnterpriseServices probably has the shortest future ahead > of it - I can't see Mono really meaningfully implementing it as > ServicedComponent and friends are conceptually tied so closely to > COM+/Windows.
This is a good point for discussion. System.EnterpriseServices is just an API through you can use the services that COM+ offers, I Agree. But this API and those services are very generic: distributed transactions, role-based security, object pooling, etc., more or less what J2EE has (ok, it doesn't have anything like BMP or CMP). So, if we need an API for a J2EE style app server, why not use System.EnterpriseServices? I see many benefints: it is already defined, it is known by many developers, and it will ease portability of server applications between Windows and Linux. - Lluis _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
