Have you guys heard about Jboss Seam framework?
I've worked with that framework for 2 years and I think its very good to work with web development. It has a lot off interesting features like, dependency injection, management session beans and an extended EL for the JSF pages. And most of the configuration is done with java annotations reducing the XML files.
I've also worked with struts and struts2 but I prefer Jboss seam.
I've heard a lot of good recommendations about the srping framwework but i never tryied yet, i hope to find more time to study Spring.
| |
|
Welcome to KnowledgeSutra - Dear Guest 
, Please Register here to get Your own website. - Ask a Question / Express Opinion / Reply
w/o Sign-Up!
| |
2
11 replies to this topic
#12
-
- Kontributors
-
- 1,114 posts
Grand Imperial Poobah
- Gender:Male
- Location:Dubai
- myCENT:50.55
Posted 03 May 2010 - 12:16 PM
Hi!
@chetdek
The use of the term Framework is not strict enough to clearly identify what one is speaking of. For example, one can refer to the Java framework, which includes all of the classes provided as a part of the Java Standard Edition (J?SE) or we could refer to the Abstract Windowing Toolkit (AWT) as a framework. AWT is included within Java, which makes the concept of a framework indistinguishable from a collection of frameworks. The Microsoft .NET 'framework' is simply a collection of frameworks such as the Windows Presentation Foundation, the Windows Communication Foundation, the Windows Workflow Foundation, the ASP.NET MVC framework, and many others.
Although Microsoft has provided us with the .NET framework, there are open-source frameworks such as Log4Net, Spring.NET and others that are available to .NET developers. Log4Net is a pretty light weight logging framework for .NET that rivals Microsoft Enterprise Library logging framework (the MSEL, Microsoft Enterprise Library, is not a part of the .NET framework). For developing Windows Forms applications, we use the WinForm framework, which is part of the .NET Framework. Spring.NET provides many of the features of the Microsoft Enterprise Library such as data validation and inversion of control, and is an attempt at porting Spring for Java onto the .NET platform.
Microsoft has been building in the functionality that 3rd party frameworks have been providing and as it is a commercial effort, they have been quite successful at replicating the efforts of the open-source movement and keeping up with open-source frameworks for the .NET platform. Language Integrated Query, Linq, along with the Entity Framework is a pretty good alternative that Microsoft has provided to match NHibernate. Language Integrated Query is simply a way for the programming language to be able to specify the data that is required and a provider hooks up the request with the actual database access code. The SQL statements are automatically generated by the Entity framework. If the application you are developing specifically targets the Microsoft SQL Server database, you could use Linq2Sql instead of the Microsoft Entity Framework. The Entity framework enables your application to achieve database independence in that you can connect to a variety of other databases. Linq itself, however, is not specific to the Entity framework or to Linq2Sql and can be extended to NHibernate too by adding in a provider.
Generally, developments that become a part of the Microsoft .NET framework start off as separate frameworks. You might have heard of the ASP.NET MVC framework that has recently gained popularity among ASP.NET developers. The MVC framework started off as a separate library that ASP.NET developers had to add in to their projects and include with their deployments until recently that MVC has become a part of the ASP.NET framework, as is the case with ASP.NET-AJAX. However, the Microsoft Enterprise Library has always remained separate from the core .NET framework.
An advantage of Microsoft's model of putting together all of its frameworks under the ".NET" badge is that installation of .NET ensures that all of the built-in libraries are present. However, if you do want to install your application on a machine that does not include the .NET framework, that would be one huge download as it is a bundle of a lot of different fraeworks, including those that you do not need. In addition, if a framework has been included with the .NET framework, it would not be possible for Microsoft to remove it from the framework because it would break backward compatibility. For example, the Linq2Sql framework included within the .NET framework will remain available although the entity framework has superseded it for all projects that have begun after the entity framework has been released.
@chetdek
The use of the term Framework is not strict enough to clearly identify what one is speaking of. For example, one can refer to the Java framework, which includes all of the classes provided as a part of the Java Standard Edition (J?SE) or we could refer to the Abstract Windowing Toolkit (AWT) as a framework. AWT is included within Java, which makes the concept of a framework indistinguishable from a collection of frameworks. The Microsoft .NET 'framework' is simply a collection of frameworks such as the Windows Presentation Foundation, the Windows Communication Foundation, the Windows Workflow Foundation, the ASP.NET MVC framework, and many others.
Although Microsoft has provided us with the .NET framework, there are open-source frameworks such as Log4Net, Spring.NET and others that are available to .NET developers. Log4Net is a pretty light weight logging framework for .NET that rivals Microsoft Enterprise Library logging framework (the MSEL, Microsoft Enterprise Library, is not a part of the .NET framework). For developing Windows Forms applications, we use the WinForm framework, which is part of the .NET Framework. Spring.NET provides many of the features of the Microsoft Enterprise Library such as data validation and inversion of control, and is an attempt at porting Spring for Java onto the .NET platform.
Microsoft has been building in the functionality that 3rd party frameworks have been providing and as it is a commercial effort, they have been quite successful at replicating the efforts of the open-source movement and keeping up with open-source frameworks for the .NET platform. Language Integrated Query, Linq, along with the Entity Framework is a pretty good alternative that Microsoft has provided to match NHibernate. Language Integrated Query is simply a way for the programming language to be able to specify the data that is required and a provider hooks up the request with the actual database access code. The SQL statements are automatically generated by the Entity framework. If the application you are developing specifically targets the Microsoft SQL Server database, you could use Linq2Sql instead of the Microsoft Entity Framework. The Entity framework enables your application to achieve database independence in that you can connect to a variety of other databases. Linq itself, however, is not specific to the Entity framework or to Linq2Sql and can be extended to NHibernate too by adding in a provider.
Generally, developments that become a part of the Microsoft .NET framework start off as separate frameworks. You might have heard of the ASP.NET MVC framework that has recently gained popularity among ASP.NET developers. The MVC framework started off as a separate library that ASP.NET developers had to add in to their projects and include with their deployments until recently that MVC has become a part of the ASP.NET framework, as is the case with ASP.NET-AJAX. However, the Microsoft Enterprise Library has always remained separate from the core .NET framework.
An advantage of Microsoft's model of putting together all of its frameworks under the ".NET" badge is that installation of .NET ensures that all of the built-in libraries are present. However, if you do want to install your application on a machine that does not include the .NET framework, that would be one huge download as it is a bundle of a lot of different fraeworks, including those that you do not need. In addition, if a framework has been included with the .NET framework, it would not be possible for Microsoft to remove it from the framework because it would break backward compatibility. For example, the Linq2Sql framework included within the .NET framework will remain available although the entity framework has superseded it for all projects that have begun after the entity framework has been released.
Reply to this topic
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
