Apache JDO Project - [jira] Commented: (JDO-316) TCK should allow user to configure

This is Interesting: Free IT Magazines  
Home > Archive > Apache JDO Project > March 2006 > [jira] Commented: (JDO-316) TCK should allow user to configure





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Commented: (JDO-316) TCK should allow user to configure
Michael Bouschen (JIRA)

2006-03-01, 7:45 am

[ http://issues.apache.org/jira/brows...action_12368278 ]

Michael Bouschen commented on JDO-316:
--------------------------------------

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'?

> TCK should allow user to configure their own JNDI provider
> ----------------------------------------------------------
>
> Key: JDO-316
> URL: http://issues.apache.org/jira/browse/JDO-316
> Project: JDO
> Type: Bug
> Components: tck20
> Versions: JDO 2 rc1
> Reporter: Craig Russell
> Assignee: Michelle Caisse
> Priority: Minor
> Fix For: JDO 2 final
> Attachments: JDO-316.patch
>
> 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.


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com