# 2840 Spring Portfolio resources classified in several categories...
# Over 400 unique visitors per day to SpringHub.com...
# Thanks to all subscribers to SpringHub.com from all over the world...
The "Clustered Remoting For Spring Framework" (or Cluster4Spring) is alternative implementation of remoting subsystem included into Spring framework.
Clustered remoting scheme
While implementation of remoting in Spring is great, it has several limitations that are quite important and must be taken into consideration when building large enterprise-level distributed system.
Briefly, these limitations relate to the point-to-point model of remoting supported by Spring - generally speaking, the client may use only one instance of remote service. It is obvious that having only such a scheme of remoting, it is hard to develop fault-tolerant systems and implement some kinds of load balancing.
Another feature, which is currently missing in remoting subsystem offered by Spring framework, is lack of the ability to dynamically discover remote services.
The main purpose of Cluster4Spring is to extend remoting system of Spring framework and overcome limitations mentioned above.
Welcome to the home of Skyway Visual Perspectives, a set of Eclipse-based modeling tools for rapidly producing highly-scalable JEE web applications and services using the Spring Framework. Using a model-centric approach to development, testing and deployment, Skyway Visual Perspectives increases developer productivity and application quality.
This article demonstrates a brand new open source library for unit testing, called Unitils. Unitils helps you in writing simple and maintainable unit tests with JUnit or TestNG . It glues together some widely used test libraries like DbUnit and EasyMock and offers integration with Spring and Hibernate . Unitils encourages applying good practices and unit testing guidelines. The ideas behind the code are based on the authors' concrete experience on enterprise projects.
Unitils offers following features
* Equality assertion through reflection, with options like ignoring Java default/null values and ignoring order of collections
* Support for database testing involving test data management with DbUnit, automatic maintenance of unit test databases and automatic constraints disabling
* Hibernate integration features such as session management and testing the mapping with the database
* Integration with Spring, involving ApplicationContext management and injection of spring managed beans
* Integration with EasyMock and injection of mocks into other objects
Chariot Solutions is a software development and consulting firm focused on helping clients achieve greater success through the intelligent application of established and emerging technologies. Emphasizing the use of agile architectures based upon open standards, we deliver solutions that allow clients to react more quickly to competitive pressures and market opportunities.
SpringSource Application Platform is a completely module-based Java application server that is designed to run enterprise Java applications and Spring-powered applications with a new degree of flexibility and reliability. The SpringSource Application Platform is based on the new SpringSource Dynamic Module Kernel™ (dm-Kernel). The dm-Kernel provides a module-based backbone for the server, which also harnesses the power of Spring, Apache Tomcat and OSGi-based technologies
The traditional way to integrate JSF and Spring was to define JSF beans in faces-config as managed beans and refer to the spring beans using the managed-property configuration. With the help of the spring’s delegatingvariableresolver the managed property is resolved from spring application context and JSF’s IOC injects the bean to the JSF Managed bean instance. I’ve written an article it about this way before.First approach is modelled as follows
JSF-Spring-JPA is the popular stack of choice these days, mostly to be used in my consulting and training purposes I’ve created a base project called MovieStore demonstrating the annotation-driven integration of JSF-Spring-JPA. JSF backing beans, spring service level beans and DAO’s are configured and integrated with annotations. Only the core infrastructure like datasource, entityManagerFactory or transactionManager are configured with xml.
Get the @Configurable stuff working within Eclipse...
"Some weeks ago I wrote a custom JSP tag for a Spring project I am currently working on. Inside the tag I wanted to use a Spring bean. Soon I realized that this case had to be handled a bit different because the tag is instantiated by the application server and not from the Spring context. Therefore the simple standard injection mechanism did not work."
This is a very simple integration of Spring and FitNesse. FitnNesse is a Wiki-based framework to implement integration tests. Fit as well. This framework uses HTML files as input and output for the integration tests. Therefore the tests can be written using Word or Excel instead of a Wiki. This makes usage much easier and can be critical for success or failure.
This framework offers new classes that you can inherit from to implement or Fit FitNesse Fixtures. These Fixtures are then autowired to Spring Beans. So the Fixtures just need to implement set-methods. These are automatically called by Spring with a Spring Bean of the right type. This way Dependency Injection also covers the Fitnesse tests.
The XAware project provides real time data integration with a service-oriented flavor. XAware makes other tools and frameworks much more productive by hiding data complexity behind "XML views". XML views span any number of data sources, and can read data, write data, or transfer data between sets of sources, all within a distributed transaction.
As also described in the Hibernate book from King and Bauer: "With the adoption of Java™ 5 generics, the idea of a generic typesafe Data Access Object (DAO) implementation has become feasible. In this article, system architect Per Mellqvist presents a generic DAO implementation class based on Hibernate. He then shows you how to use Spring AOP introductions to add a typesafe interface to the class for query execution."
GASwerk - Geronimo Application Server Assemblies
GASwerk provides production ready solutions based on proven OpenSource components.
Three server assemblies based on Apache Geronimo Application Server are available. Each of them solving a particular problem.
GASwerk SOA Stack is a powerful feature-rich SOA assembly for agile businesses that want to bring their IT department closer to their business processes. GASwerk SOA provides an Enterprise Service Bus for connectivity and an business process engine to model all the processes.
GASwerk Spring is focused on developer needs. It provides a Spring framework deployment feature. Equipped with GASwerk Spring, your Geronimo Application Server is able to directly deploy Spring Applications to your server.
GASwerk JMS is a Messaging Cluster based on Javas Messaging Service (JMS). It is a powerful, scalable solution for companies where message throughput and reliability is critical.
And of course you could use all the GASwerk pieces together or only parts of the whole stack.
Geb GAS!
this module makes the integration of spring-annotation and JSF really easy.
* It registers automatically a VariableResolver in the JSF stack to enable the use of the spring beans as managed beans
* it adds 2 (two) more scopes to spring framework: flash and conversation
* it registers a navigation handler in the JSF stack to enable you to write less code
* it adds some annotations to make it easier to write JSF code
The Security Annotation Framework (SAF) is an instance-level access control framework driven by Java 5 annotations. It can be easily integrated into Spring applications which primarily use the SAF to control access to their domain object instances. SAF security annotations define locations in the source code where the SAF shall perform permission checks at runtime. An annotation-driven approach to instance-level access control promotes the separation of an application’s security logic from its business logic. This significantly increases the testability and reusability of application components. It further allows the implementation of instance-level access control features into existing applications without modifying existing business logic.