This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 226717 - Add database-login metadata support to the EclipseLink-ORM.XML Schema
Summary: Add database-login metadata support to the EclipseLink-ORM.XML Schema
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 227219
  Show dependency tree
 
Reported: 2008-04-11 11:42 EDT by Guy Pelletier CLA
Modified: 2022-06-09 10:32 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Guy Pelletier CLA 2008-04-11 11:42:49 EDT 
I'm adding this since we need to deal with it. Current deployment XML allows database login metadata to be set. It provides setting points for the following:

 - platform-class
 - user-name
 - password
 - external-connection-pooling
 - external-transaction-controller
 - sequencing
   - default-sequence
   - sequences
     - sequence
 - driver-class
 - connection-url
 - bind-all-parameters                 
 - cache-all-statements
 - byte-array-binding
 - string-binding
 - string-binding-size
 - streams-for-binding
 - force-field-names-to-upper=case
 - optimize-data-conversion
 - trim-strings
 - batch-writing
 - jdbc-batch-writing

Current working of this info with regards to the EclipseLink session.xml file is, any login info specified in the deployment xml overrides any login info from the sessions.xml.

Therefore we need a way to port this metadata for those users that rely on its specification within the deployment xml.
Comment 1 Shaun Smith CLA 2008-04-11 12:37:55 EDT 
With most, if not all, of these settings already available in persistence.xml and sessions.xml it doesn't make sense to continue to propagate their use in EclipseLink.  If migrating an existing TopLink application to JPA they would move their deployment.xml settings to persistence.xml and if they were sticking with the native API they'd move the settings to sessions.xml and switch to SessionManager from XMLProjectReader.  This would be part of the documented migration instructions.

Removing yet another place to specify all this information will simplify EclipseLink usage.

--Shaun
Comment 2 Doug Clarke CLA 2008-07-07 13:32:53 EDT 
Changed version to unspecified
Comment 3 Peter Krogh CLA 2009-04-03 16:02:48 EDT 
These JPA enhancements were accidentally assigned to 1.1.1.
Comment 4 Doug Clarke CLA 2009-11-27 11:00:07 EST 
Moving to 2.1 where our goal is to have the eclipselink-orm.xsd fully support all native features currently available in the deployment XML XSD
Comment 5 Guy Pelletier CLA 2009-12-08 09:32:23 EST 
Closing this bug as it was deemed notfeasible to fix.
Comment 6 Eclipse Webmaster CLA 2022-06-09 10:32:42 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink