JWarp Core Services

If you would like to implement your application using the JWarp framework (which, of course, we would appreciate), you best start having a look at what kind of services are available. With the first release of JWarp the following services and implementations are available:

• Cache: A dynamic cache implementation with several settings that adapt to its dynamic behaviour.
• Configuration: A configuration repository service for loading and accessing several XML configurations
• ConnectionPool: A dynamic connection pool compatible with JDBC 1.0. There are some useful features, such as using the finalization APIs for detecting non-closed connections, or connecting to a database in a separate thread, thus being able to define a timeout for the connection establishment.
• Groups: A service implementation you can use whenever you need to use groups of things.
• Id: A service for generating unique identifiers.
• Localization: A service for handling / loading localization packages.
• Log: A service for managing several log implementations.
• Mail: A service for sending emails (also multipart emails are possible)
• Param: A service for defining type validators and parameter validations.
• Persistence: A service for making objects persistent. This service depends on a persistence layer implementation.
• Security: A service for handling and controlling all security checking. If no such service is present, then no security is implemented.
• System: A manager service for the current JWarp system status. This service is not yet implemented as well as not yet finally defined.
• ThreadPool: A service providing thread pools.
• Web: A service providing a small framework for web development. There are several subcomponents, such as a session- and a request initializer, different forwarders (html, jsp, xml) as an action oriented API for dispatching and handling several requests.
• Work: A service for providing software tools (implementing the org.jwarp.service.work.ITool interface. The software tools can be started through the work manager interface. In addition to a threadpool, the work manager is able to store the jobs persistently, resume their execution after restarting the service (or the whole application or JVM) and storing the execution result. This component needs the functionality of the IPersistance service and thus of a functional persistence layer implementation.

If you plan to develop a web application, you shoud have a closer look at the sample application including its configuration (mainly of the web service) and the code within the packages org.jwarp.service.web.* .