Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow creating Derby as a JNDI datasource #5

Open
10 tasks
bindul opened this issue Dec 11, 2015 · 0 comments
Open
10 tasks

Allow creating Derby as a JNDI datasource #5

bindul opened this issue Dec 11, 2015 · 0 comments

Comments

@bindul
Copy link
Contributor

bindul commented Dec 11, 2015

The goal for this issue is to be able to set up and run tests looking up data sources from a JNDI lookup (as in an application server or servlet container); without requiring full blown application server (or servlet container) running.

This one builds on (hence, depends on) #24

  • Define optional JNDI context initialization mechanism
  • Provide implementation for using Tomcat Naming context (with Tomcat as an optional dependency)
  • Extend the configuration to be able to define Context Initialization mechanism or none (context initialized outside)
  • Allow creation of a JNDI datasoure; which should be able to use any context provided (our sample one; or a standard app server one).
  • Unit test to use Tomcat context initialized through above, or outside
    • In Memory
    • Directory
    • Jar
    • Classpath
  • Extend the datasource documentation to talk about all of the above
@bindul bindul added the feature label Dec 11, 2015
@bindul bindul self-assigned this Dec 11, 2015
@bindul bindul added this to the JUnit Helper 0.1 milestone Dec 11, 2015
@bindul bindul removed their assignment Dec 18, 2015
@bindul bindul removed the blocked label Feb 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant