Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368373

Summary:	Support JNDI data sources on the test server
Product:	z_Archived	Reporter:	Justin Spadea <jspadea>
Component:	EDT	Assignee:	Justin Spadea <jspadea>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	jndi

Description Justin Spadea

2012-01-11 12:28:02 EST

Copied from bug 361030:

The test server should make use of JNDI so that test is as similar to the
production environment as possible. One example of runtime difference if the
test server does not support JNDI is that "if (myDS isa SQLJNDIDataSource)"
would evaluate differently than production code. Jetty has built-in JNDI
support, we just need to configure it so that data sources are available. Work
involved:

a) For each SQL resource binding of each DD on the test server, if it has the
new check box for defining data sources selected, use the information to
automatically define such a data source.

b) For the condition in 5a, OR the condition that the user selected "Use an
existing JNDI data source", a resource ref needs to be configured.

c) Update IDEResourceLocator to create SQLJNDIDataSource objects as necessary.

d) The code that determines the server needs to be updated as changes are made
to DD files will need to handle any JNDI-related changes (new/changed data
sources, or new/changed resource refs).

e) To support the "Use an existing JNDI data source" option in test mode, we
can add a preference page for the test server that lets users define data
sources that get added to all test servers (they would need to enter the JNDI
name, the data source class, and pick a connection profile that provides the
rest of the information).

Comment 1 Justin Spadea

2012-01-11 12:33:39 EST

Some of this work might get bumped to I2. Ideally I'd like to get 'a', 'b', and 'c' done, then switch over to the IDE work, then come back to 'd' and 'e'. I'll split those parts out into a new bugzilla if that's what ends up happening. 'e' is a candidate for not supporting right now, but we all agreed it would be a good thing to add. 'd' must be done before 0.8 ships.

Comment 2 Lisa Lasher

2012-01-23 15:42:20 EST

changing target from M1 to M2

Comment 3 Justin Spadea

2012-02-01 13:42:32 EST

The work has been completed, as well as making the test server extensible.

Due to changes in the editor, 'e' is no longer applicable (the editor now always requires a user to specify the connection info - either point to a connection profile, or manually enter the info).

Comment 4 Justin Spadea

2012-02-22 08:52:34 EST

Closing