 Documentation
» Signsoft intelliBO user guide
-
Signsoft
intelliBO and Spring 2.0
An architecture sample for using Signsoft intelliBO with Spring 2 was added.
-
intelliBO
first steps
This chapter is intended for new users of Signsoft intelliBO. On the basis of a simple
application it describes the essential steps from the creation of the business class up to saving
and loading persistent objects from a database.
-
Mappings
and relations
This chapter describes how to express mapping declarations for field mappings, relationship
mappings and inheritance mappings with Signsoft intelliBO.
-
Queries
This chapter comprehensively describes how to formulate queries with Signsoft intelliBO.
-
System
Configuration
There are three ways to configure Signsoft intelliBO
- programmatically,
- by a properties-file according the JDO2-specification and
- by a
ibo-config.xml file.
This chapter provides you with all details.
-
Database
support drivers
This chapter describes all database support drivers shipped with Signsoft intelliBO.
-
Application server support (coming soon)
In the meanwhile, please refer to our architecture samples for details of how to configure
the Signsoft intelliBO resource adapter.
Please subscribe to our
newsletters to
receive latest news when this chapter will be available.
Application Programming Interface
Migration to Signsoft intelliBO 4.1
-
»
Migration guide to Signsoft intelliBO 4.0
Signsoft intelliBO version 3.x reached end of life in 2006. This migration guide will
facilitate the transition to version 4.0.
-
» Migration guide to Signsoft intelliBO 4.1
The following behaviour changes should be taken into consideration when migrating from
Signsoft intelliBO 4.0.x to version 4.1:
-
Optional relations between data objects
If an association is optional, i.e. a null reference is allowed, the JDO mapping file must
explicitly state an "allow-null" for this relation.
-
PersistenceManager#getObjectById
Calling getObjectById() on a PersistenceManager does not cause a refresh of an already
fetched object any more.
-
Query#declareImports
Parameter and variable declarations have to be full-qualified or are to be imported according
to the JDO specification.
-
Fetching on demand
To improve JDO 2.0 conformance, an access to a not-yet-loaded field leads to a fetch of the
whole default fetch group or the currently active fetch group.
-
Datastore identities
In the course of memory optimizations, the internal representation of datastore identities
was changed. For further details please contact the Signsoft intelliBO support team.
We will support you in the transition to Signsoft intelliBO 4.1. Please read also the version
4.0 migration guide in case you update from an earlier version of Signsoft intelliBO.
Whitepapers
|
|EN 
