From f084e6d5c6e20a08394679e05e9f44bd9c4dc508 Mon Sep 17 00:00:00 2001 From: tle Date: Tue, 27 Dec 2011 21:53:10 +0000 Subject: 350615 - [EclipseLink] Point to latest XSD's in shipped EL bundles in XML Catalog --- .../schemas/eclipselink_sessions_2.1.xsd | 1598 -------------------- 1 file changed, 1598 deletions(-) delete mode 100644 common/plugins/org.eclipse.jpt.common.eclipselink.core/schemas/eclipselink_sessions_2.1.xsd (limited to 'common/plugins/org.eclipse.jpt.common.eclipselink.core/schemas/eclipselink_sessions_2.1.xsd') diff --git a/common/plugins/org.eclipse.jpt.common.eclipselink.core/schemas/eclipselink_sessions_2.1.xsd b/common/plugins/org.eclipse.jpt.common.eclipselink.core/schemas/eclipselink_sessions_2.1.xsd deleted file mode 100644 index 61697113d8..0000000000 --- a/common/plugins/org.eclipse.jpt.common.eclipselink.core/schemas/eclipselink_sessions_2.1.xsd +++ /dev/null @@ -1,1598 +0,0 @@ - - - - - - - - - This is the root element and exists only for XML - structure - - - - - - - - - - - - - This is the node element that describes a particular session - - - - - - - Generic element used to describe a string that - represents the name of an item - - - - - - - - - This element is an optional element of - session element that define the Remote - Command Module that can also be used for - cache synchronization - - - - - - - - This element is an optional - element of remote-command - element." - - - - - - - This element is an optional - element of remote-command - element. It determine what - command features, the RCM - supports - - - - - - - - This element is an - optional element of - command element. It - turns on cache - synchronization to - allow sending and - receiving cache sync - commands - - - - - - - - - - This element is an optional - element of remote-command - element. It defines the - transport mechanism of the RCM. - The default transport mechanism - is RMI - - - - - - - - - - - - - - - - This element represents if the profiler will be - used by the session - - - - - - - - - - - - - This is the class that the session will use to - handle exceptions generated from within the - session - - - - - - - This element used to specify the logging options - - - - - - - This element specifies the session customizer - class to run on a loaded session. - - - - - - - - - This is the node element that describes which server - platform to use, JTA settings and runtime services - settings - - - - - - - This element is an optional element. This - specifies whether or not the JMX MBean for - providing runtime services is deployed. - - - - - - - This element is an optional element. This - specifies whether or not this session will - integrate with the JTA (i.e. whether the session - will be populated with a transaction controller - class. The choice of server-class will - automatically be chosen based on the transaction - controller - - - - - - - - - - - - - This is the subclass of - org.eclipse.persistence.platform.server.PlatformBase - to specify which server platform to use - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Provides a single view to a session that - transparently accesses multple databases. - - - - - - - - - This is the element that represents the - session name - - - - - - - - - - - - - - - - - - - - The session is the primary interface into EclipseLink, the - application should do all of its reading and writing of - objects through the session. The session also manages - transactions and units of work. The database session is - intended for usage in two-tier client-server - applications. Although it could be used in a server - situation, it is limitted to only having a single - database connection and only allows a single open - database transaction. - - - - - - - - - This project (class or xml) will be - loaded as the primary project for the - session. - - - - - - - Additional projects will have their - descriptors appended to the primary - project. - - - - - - - - - - - - Is an extension of a DatabaseSession - - - - - - - - - Connection pools are only for usage with - internal connection pooling and should - not be used if using external connection - pooling - - - - - - - - - - Set this tag to use the - sequence connection pool - - - - - - - - - - - - - - - - Used to specify how default client sessions are acquired - - - - - - - Specifies if an exclusive connection should be - used for reads, required for VPD, or user based - read security. - - - - - - - Specifies if a connection should be acquired and - held upfront in the client session, or only - acquired when needed and then released. - - - - - - - - - Defines common fields for database-login and eis-login - - - - - - - This is the element that represents the platform - class name - - - - - - - This element is used in the login as well as the - Cache Synchronization feature - - - - - - - This element is used in the login as well as the - Cache Synchronization feature - - - - - - - This element is used in the login as well as the - Cache Synchronization feature - - - - - - - Set the default qualifier for all tables. This - can be the creator of the table or database name - the table exists on. This is required by some - databases such as Oracle and DB2. - - - - - - - Set to true if the connection should use an - external connection pool - - - - - - - Set to true if the session will be using an - external transaction controller - - - - - - - Sequencing information. - - - - - - - - Default sequence. The name is - optional. If no name provided an - empty string will be used as a name. - - - - - - - Non default sequences. Make sure - each sequence has unique name. - - - - - - - - - - - - - - - This element is an optional element of a login. - It is used to define extra properties on the - login - - - - - - - - - - - - - Holds the configuration information necessary to connect - to a JDBC driver. - - - - - - - - - - - The driver class is the Java - class for the JDBC driver to be - used (e.g. - sun.jdbc.odbc.JdbcOdbcDriver.class) - - - - - - - This is the URL that will be - used to connect to the database. - - - - - - - - This is the URL of a datasource that - may be used by the session to - connect to the database. - - - - - - - - - - - - - - - Set whether to bind all arguments to any - SQL statement. - - - - - - - Set whether prepared statements should - be cached. - - - - - - - EclipseLink can be configured to use - parameter binding for large binary data. - By default EclipseLink will print this data - as hex through the JDBC binary excape - clause. Both binding and printing have - various limits on all databases (e.g. 5k - - 32k). - - - - - - - Set to true if strings should be bound. - Used to help bean introspection. - - - - - - - EclipseLink can be configured to use streams - to store large binary data. This can - improve the max size for reading/writing - on some JDBC drivers. - - - - - - - This setting can be used if the - application expects upper case but the - database does not return consistent case - (e.g. different databases). - - - - - - - Set whether driver level data conversion - optimization is enabled. This can be - disabled as some drivers perform data - conversion themselves incorrectly. - - - - - - - By default CHAR field values have - trailing blanks trimmed, this can be - configured. - - - - - - - EclipseLink can be configured to use batch - writing. This facility allows multiple - write operations to be submitted to a - database for processing at once. - Submitting multiple updates together, - instead of individually, can greatly - improve performance in some situations. - - - - - - - Setting this tag with true indicates to - EclipseLink that the JDBC driver supports - batch writing. EclipseLink's internal batch - writing is disabled. Setting this tag - with false indicates to EclipseLink that the - JDBC driver does not support batch - writing. This will revert to the default - behaviour which is to delegate to - EclipseLink's internal batch writing. - - - - - - - Allow for the max batch writing size to - be set. This allows for the batch size - to be limited as most database have - strict limits. The size is in - characters, the default is 32000 but the - real value depends on the database - configuration. - - - - - - - EclipseLink can be configured to use - database specific sql grammar not JDBC - specific. This is because unfortunately - some bridges to not support the full - JDBC standard. By default EclipseLink uses - the JDBC sql grammar. - - - - - - - - - - - If true will cause EclipseLink to ping database to determine if an SQLException was cause by a communication failure - - - - - Configure the number of attempts EclipseLink will make if EclipseLink is attempting to retry a query. - - - - - Configure the time in miliseconds that EclipseLink will wait between attempts to reconnect if EclipseLink is attempting to retry a query. - - - - - Override the platform specific SQL that EclipseLink will issue to a connection to determine if the connection is still live. - - - - - - - - - - - - - - - - - Defines connection information and datasource - properties. There are three ways to connect through EIS, - - Provide a JNDI name to the ConnectionFactory and use - the default getConnection - Provide a JNDI name to the - ConnectionFactory, and a driver specific ConnectionSpec - to pass to the getConnection - Connect in a non-managed - way directly to the driver specific ConnectionFactory An - EISConnectionSpec must be provided to define how to - connect to the EIS adapter. The EIS platform can be used - to provide datasource/driver specific behavoir such as - InteractionSpec and Record conversion. - - - - - - - - - - - - - - - Defines login and platform type to be used - - - - - - - - - - - - - - - - - - Used to specify how connections should be pooled in a - server session. - - - - - - - - The max number of connections that will be - created in the pool - - - - - - - The min number of connections that will aways be - in the pool - - - - - - - - - - The read connection pool is used for read access through - the server session. Any of the connection pools can be - used for the read pool however this is the default. This - pool allows for concurrent reads against the same JDBC - connection and requires that the JDBC connection support - concurrent read access. - - - - - - - - - This tag is used to specify if the - connections from the read connection - pool are exclusive or not - - - - - - - - - - - Defines the common logging options - - - - - - - Defines the options of the Java log - - - - - - - - - - - - - - Defines the options of the EclipseLink log - - - - - - - - - This element specifies the log level for logging - - - - - - - - - - - - - - - - - - - - Name of the file to write the logging to - - - - - - - - - - - - Defines the options of the Server log - - - - - - - - - - - - Set whether to log exception stacktrace. Without - this element, the stacktrace is logged for FINER - or less (FINEST) - - - - - - - Set whether to log thread. Without this element, - the thread is logged for FINE or less (FINER or - FINEST) - - - - - - - Set whether to log session. Without this - element, the session is always printed - - - - - - - Set whether to log connection. Without this - element, the connection is always printed - - - - - - - Set whether to log date. Without this element, - the date is always printed - - - - - - - - - This element defines the transport mechanism of the RCM. - The default transport mechanism is RMI - - - - - - - This element is an optional element of transport - element and has value of "DiscardConnection" or - "KeepConnection". It determines whether - connection to a RCM service should be dropped if - there is a communication error with that RCM - service. The default value for this element is - "DiscardConnection". - - - - - - - - - - - - - - - This element is an optional element of transport - element. It defines the RMI transport mechanism. The - default naming service is JNDI - - - - - - - - - This element is an optional element of - rmi element and has value of - "Asynchronous" or "Synchronous". It - determines whether the RCM propagates - command and does not wait for command to - finish its execution in asynchronous - mode or wait for command to finish its - execution in synchronous mode. The - default value of this element is - "Asynchronous". - - - - - - - - - - - - - This element is an optional element of - rmi element. It determines whether the - Discovery settings should be changed. - Note that a default Discovery with its - default settings is created when the rmi - element is specified. - - - - - - - - - - This element is an optional - element of discovery - elemenent. It determines - whether the multicast group - address should be changed. - The default value of this - element is "1000" - - - - - - - This element is an optional - element of discovery - elemenent. It determines - whether the time-to-live of - the packets that are sent - from the Discovery's - mulsticast socket should be - changed. The default value - of this element is "2" - - - - - - - - - - - - This element is an optional element - of rmi elemenent. It determines - whether RMI registry should be used - for naming service - - - - - - - - - - - - - - - - - This element defines the RMI-IIOP transport mechanism of - the RCM. The default naming service is JNDI - - - - - - - - - - This element defines the JMS topic transport mechanism - of the RCM - - - - - - - - - - - - - - - - - This element defines the OC4J JGroups transport - mechanism of the RCM - - - - - - - - - - - - - - - This element defines the Sun CORBA transport mechanism - of the RCM - - - - - - - - - - This element is an optional element of transport - element. It determines whether a user implemented - transport mechanism that should be used. - - - - - - - - - - - - - - - - This element is an optional element of - jndi-naming-service. It determines whether the - URL for naming service should be changed. - - - - - - - - - - - This element is an optional element of - jndi-naming-service. It determines whether the - initial context factory class for naming service - should be changed. - - - - - - - This element is an optional element of - jndi-naming-service. It determines whether - naming service requires extra property that is - not defined by EclipseLink but it is required by the - user application - - - - - - - - - - - - - - - - - - - - - - Sequence object. - - - - - - Sequence name. - - - - - - - Sequence preallocation size. - - - - - - - - - References default sequence object, overriding its name - and (optionally) preallocation size. - - - To use preallocation size of default sequence object, - set preallocation size to 0 - - - - - - - - - - Database sequence mechanism used. - - - - - - - - - Table sequence - - - - - - - - Define the name of the sequence table. - - - - - - - Define the name of the sequence name - field in the sequence table. - - - - - - - Define the name of the sequence counter - field in the sequence table. - - - - - - - - - - - Unary table sequence - sequence name is a table name, - table has a single field and a single row - - - - - - - - - Define the name of the sequence counter - field in the sequence table. - - - - - - - - - - Xmlfile sequence. - - - - - - - - Xml sequence - - - - - - - - Define the name of the sequence table. - - - - - - - Define the name of the sequence name - field in the sequence table. - - - - - - - Define the name of the sequence counter - field in the sequence table. - - - - - - - - - - - - - - This element specifies which document preservation - strategy will be used. - - - - - - - - - - - - This element specifies which node ordering strategy will - be used. - - - - - - - An implementation of DocumentPreservation Policy that - accesses the session cache to store Objects and their - associated nodes. - - - - - - - - - - - A DocumentPreservationPolicy to indicate that no - document preservation work should be done. - - - - - - - - - - - An implementation of DocumentPreservationPolicy that - maintains bidirectional relationships between Java - Objects and the XMLNodes they originated from. - - - - - - - - - - - An implementation of NodeOrderingPolicy that simply - appends the new child element to the parent. - - - - - - - - - - - An implementation of NodeOrderingPolicy that ignores any - new elements when updating a cached document. - - - - - - - - - - - An implementation of NodeOrderingPolicy that adds new - elements to an XML Document based on the last updated - sibling in their context. - - - - - - - -- cgit v1.2.3