[#JDO-316] TCK should allow user to configure their own JNDI provider

JDO

TCK should allow user to configure their own JNDI provider

Created: 25/Feb/06 07:29 AM Updated: 02/Mar/06 06:37 AM

Return to search

Component/s:

tck2

Affects Version/s:

JDO 2 rc1

Fix Version/s:

JDO 2 final

Time Tracking:

Not Specified

File Attachments:

	File Name	Date Attached	Attached By	Size
	JDO-316.patch	2006-03-01 06:16 AM	Michelle Caisse	1 kB

Resolution Date:

02/Mar/06 06:37 AM

Description

« Hide

Currently, to reconfigure the JNDI provider, the user has to edit both the jndi.properties file and the project.properties.

We should allow the user to only edit the jndi.properties by changing the project.properties to automatically add all the jar files in lib/ext to the classpath.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Michelle Caisse added a comment - 01/Mar/06 06:16 AM

I've attached a patch for review. All jar files in lib/ext are included on the classpath.

[ Permlink | « Hide ]

Michael Bouschen added a comment - 01/Mar/06 10:19 PM

Th patch looks good!

Just one comment: should we give the new path a better name than 'jndi'?. This path can include any third party library, not only a jndi implementation. How about calling it 'external.libs'?

[ Permlink | « Hide ]

Michelle Caisse added a comment - 02/Mar/06 02:17 AM

I think that's a good idea. Thanks!

[ Permlink | « Hide ]

Michelle Caisse added a comment - 02/Mar/06 06:37 AM

Fixed in revision 382166