maXXXeE
asked on
EJB evivalent in .NET
Wat is the EJB equivalent in .NET
can it only be done by using a dll with a Transaction Server or is there any other way.
can it only be done by using a dll with a Transaction Server or is there any other way.
ASKER
umm, but webservice dont work like ejb, by ejb i mean TRANSACTION SUPPORT also
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hey rdivilbiss,
thanx for the link. i m going thru the article.
meanwhile one more question.
Is there anything comparable to Entity beans in .Net
thanx for the link. i m going thru the article.
meanwhile one more question.
Is there anything comparable to Entity beans in .Net
Actually the net framework handles entity persitance for you...although you have more control than with Entity Beans.
Creat a .NET object and it will be compiled, optimized and cached (persisted) on the server. You have a lot of control over this, although a Windows 2003 IIS 6.0 server probably will do a better job of managing this than you would.
This article points out some of the problems with EB, all of which are missing in the .NET environment.
http://theserverside.com/discussions/thread.tss?thread_id=771
Much like the author makes the case for Java Data Objects as a better solution, so did the .NET team implement a more robust environment for persiting tranactional aware objects. You'll just need to learn new terminology.
Creat a .NET object and it will be compiled, optimized and cached (persisted) on the server. You have a lot of control over this, although a Windows 2003 IIS 6.0 server probably will do a better job of managing this than you would.
This article points out some of the problems with EB, all of which are missing in the .NET environment.
http://theserverside.com/discussions/thread.tss?thread_id=771
Much like the author makes the case for Java Data Objects as a better solution, so did the .NET team implement a more robust environment for persiting tranactional aware objects. You'll just need to learn new terminology.
BTW, the CLR environment means you don't have to create DLL's and register those on the server. All my projects involve creating server side objects which slows the front end of the development but reduces the code for the application and vastly increases speed of maintenance. (Plus, you can hide complexity, transactions and persistance) from the junior developers who only can interface to the objects.
ASKER
hi rdivilbiss
thanx for helping.
the link that u provided (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/psent.asp) cleared many of my doubts.
thanx again
thanx for helping.
the link that u provided (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/psent.asp) cleared many of my doubts.
thanx again
Have fun...
Nothing like learning a new envoronment.
Nothing like learning a new envoronment.
Yes, End of the day, the code has to be a .NET DLL.
There are a few ways to communciate with a server side .NET DLL such as via a web service or an ASPX page.