Information for RPM simple-jndi-0.11.4.1-10.fc24.src.rpm
ID | 21242 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | simple-jndi | ||||||||||||
Version | 0.11.4.1 | ||||||||||||
Release | 10.fc24 | ||||||||||||
Epoch | |||||||||||||
Arch | src | ||||||||||||
Summary | A JNDI implementation | ||||||||||||
Description | Simple-JNDI is intended to solve two problems. The first is that of finding a container independent way of opening a database connection, the second is to find a good way of specifying application configurations. 1. Unit tests or prototype code often need to emulate the environment within which the code is expected to run. A very common one is to get an object of type javax.sql.DataSource from JNDI so a java.sql.Connection to your database of choice may be opened. 2. Applications need configuration; a JNDI implementation makes a handy location for configuration values. Either as a globally available system, or via IoC through the use of some kind of JNDI configuration facade (see gj-config). A solution: simple implementation of JNDI. It is entirely library based, so no server instances are started, and it sits upon Java .properties files, XML files or Windows-style .ini files, so it is easy to use and simple to understand. The files may be either on the file system or in the classpath. | ||||||||||||
Build Time | 2016-02-05 06:33:02 GMT | ||||||||||||
Size | 46.72 KB | ||||||||||||
419165a36634476cd5fffd71cc11b927 | |||||||||||||
License | BSD | ||||||||||||
Provides | No Provides | ||||||||||||
Obsoletes | No Obsoletes | ||||||||||||
Conflicts | No Conflicts | ||||||||||||
Requires |
|
||||||||||||
Recommends | No Recommends | ||||||||||||
Suggests | No Suggests | ||||||||||||
Supplements | No Supplements | ||||||||||||
Enhances | No Enhances | ||||||||||||
Files |
|
||||||||||||
Component of | No Buildroots |