|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Feature matrix
Signsoft intelliBO Professional - Signsoft intelliBO Community Edition| Pro | CE | ||
| » Mappings | |||
|
Field mappings
:
direct mapping, code mapping, virtual mapping, multi source field mapping |
|
|
|
|
Relationship mappings:
1:1, 1:N, M:N, ordered 1:N and M:N mapping, bidirectional 1:1 mapping, inverse mapping, constraint 1:N
mapping
|
|
|
|
|
Inheritance mappings:
Subclass-Table, Superclass-Table und New-Table in almost every conceivable combination |
|
|
|
|
additional functions:
cascading delete and update, batch-delete, batch-update, untying foreign keys |
|
|
|
| » Tools | |||
|
Standard tools:
enhancer, schema-generator, mapping-verifier, version information |
|
|
|
|
Integration in third party products:
ant-tasks, eclipse3 plug-in, JBuilder plug-in |
|
|
|
|
Experimental tools:
referential-integrity analyser, class-generator |
|
|
|
|
Lizenz management:
license-tool |
|
|
|
| » Persistent data sources | |||
|
Databases:
Oracle 9i/10g, IBM DB2 UDB 8, MSSQL 2005, MySQL 5, Sybase ASE 15, PostgreSQL, H2, HSQLSB, Derby, McKoi, Ingres, Informix 10 |
|
|
|
| XML-Datastores |
|
|
|
| » Caching | |||
| First level object cache |
|
|
|
| Second level shared cache |
|
|
|
|
Distributed shared cache*:
TCP multicast |
|
|
|
| » Supported environments | |||
|
Desktop applications:
Fat-Clients, Rich-Clients |
|
|
|
|
Web applications
Tomcat 4.x/5.x |
|
|
|
|
Spring-Framework
|
|
|
|
|
Application servers**:
Bea WebLogic 8.1/9.2/10.0, IBM WebSphere 5.x/6.x, SAP WebAS 6.4/7.10, Oracle OC4J 10g, JBoss 3.x/4.x, Apache Geronimo 1.x |
|
|
|
* The distributed share cache is required when using application servers in a cluster. It is employed when several application server instances have to exchange information about cached objects.
** Support of J2EE 1.4 und JEE 5 compatible application servers is realized by using the Java Connector Architecture API (JCA). Signsoft intelliBO is here deployed as a resource adapter into the application server. With this kind of deployment the application server takes over transaction control and pooling of persistence-managers.
