Reasons To Use Shipka JDF.

1. Leverage the comprehensive application architecture.
Shipka JDF architecture provides solutions for all aspects of web application development - access to data, transaction management, access to programming logic, access to presentation functionality, participation in SOA, security, etc.
Problem solved: It eliminates the need of building custom architecture for every application by integrating popular packages like Struts, Spring, Hibernate, XML parsing, and Web Services.

2. Leverage the abstract data manipulation interface.
Why would you want to do that? For the same reason developers favor JDBC over individual database APIs. Shipka JDF just goes a level up to provide single object model and object manipulation interface for data objects of all types (memory, XML, database, remote applications, etc.). Data objects are linked to the underlying data storage through XML configuration. It does not require additional code.
Problem solved: It eliminates the need to use separate interface for each data type - like Hibernate, XML parsing tool, Web Services, REST tools, etc.

3. Leverage the abstract search, query and sorting capabilities.
Shipka JDF let you work from the notion of single Object Repository and gives you consistent way to search, query and sort the objects at that repository. Those capabilities are part of the universal data manipulation interface and operate on objects (not SQL-based).
Problem solved: It eliminates the need of using separate search and query capabilities for each data type - like SQL, HQL or OQL for databases, XPATH to search XML data, and custom code to search and query memory objects, WebServices interface for remote data objects, etc.

4. Leverage the change tracking, transaction support and entity expression features available to every data object.
Those features are part of the abstract data object model. Change tracking enables developers to commit object changes to the ObjectRepository immediately or in a batch mode. They can also rollback object changes when the user cancels current workflow. Entity expressions allow direct access to all data that are part of the object graph.
Problem solved: Developers do not need to write custom code to implement those features.

5. Leverage the automated transaction management.
Shipka JDF makes all data objects transactional. It means that the framework manages transactions at two levels: a) underlying data storage (like DB) and b) data objects involved in the transactions. In case of rollback it ensures that data objects are restored to their state prior to running the transaction.
Problem solved: Developers do not need to implement transaction management at DB and object level.

6. Leverage the abstract interface for business logic invocation.
Abstract interface makes every unit of programming logic (operation) accessible by providing operation identifier and operation parameters. More complex expressions may be created by passing operations as parameters to another operation. Shipka JDF operation expression syntax enables developers to invoke operations from within configuration files.
Problem solved: Operations become independent of any class or interface. They can be implemented anywhere - locally or remotely.

7. Leverage the abstract interface for presentation components.
In the context of Shipka JDF the presentation component is self-sufficient unit of presentation functionality that is independent of any application. Presentation components are intended for deployment within the application configuration. Deployed instances may be customized with static data from resource file(s) or dynamic data from application model. Developers may implement presentation components with different presentation technologies.
Problem solved: Eliminate the complexity created by interdependent presentations and increase reusability of presentation functionality.

8. Share large units of presentation functionality between applications.
Shipka JDF allows developers to create more complex functionality involving multiple screens (like a workflow) as a standalone application and integrate it within other applications as a single presentation unit. It hides the implementation of integrated presentation component from the hosting application. The presentation unit may be either embedded with the hosted application or accessed remotely.
Problem solved: Provides a standard way of sharing large presentation units between applications.

9. Leverage an application architecture that is designed for SOA development.
Shipka JDF architecture consists of application layer, service layer and service export layer. The service layer provides access to objects, operations and presentation components. Individual service implementations (local or remote) are known only to the service layer and can be changed without affecting any other layer. The Application layer implements application functionality by consuming services from the service layer. Service export layer exports service layer services to other applications and enforces access control.
Problem solved: Makes it easy for applications to participate in SOA environment by exporting and consuming services.

10. Leverage the advanced application integration capabilities.
Shipka JDF enables developers to create composite applications integrating the functionality of many independently deployed applications through the following capabilities: a) Individual applications may export themselves or part of their functionality as single presentation unit, b) Composite application may deploy remote presentation components, c) Shipka JDF extends the user session of composite application to all collaborating applications and enables the composite application to access objects at collaborating applications. Extended user sessions do not expire automatically. They are explicitly expired by the composite application when the user session there expires.
Problem solved: Made it possible for independently deployed applications to function as a single application with single user session. It resolved the issue of independently expiring user sessions at integrated applications.

11. Protect company investments in application development.
Shipka JDF protects your investments in application development and reduces maintenance costs through the flexibility of its architecture. By programming with abstract object, operation and presentation component interfaces developers have the option of changing those implementations without affecting the application logic. If performance requirements change (for example) and the database becomes a bottleneck, developers may decide to migrate their database objects to In-Memory Data Grid (IMDG) and improve data throughput up to 10 times.
Problem solved: Increase the application life span by making it cost effective to adjust the application to ever changing enterprise landscape and application requirements.