How to Install and Uninstall simple-jndi.noarch Package on Fedora 34

Last updated: October 06,2024

1. Install "simple-jndi.noarch" package

Please follow the guidelines below to install simple-jndi.noarch on Fedora 34


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                simple-jndi.noarch
            
                    
    
    Copied

2. Uninstall "simple-jndi.noarch" package

Please follow the guidelines below to uninstall simple-jndi.noarch on Fedora 34:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                simple-jndi.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the simple-jndi.noarch package on Fedora 34

Last metadata expiration check: 3:01:19 ago on Tue Sep 6 02:10:55 2022.
Available Packages
Name : simple-jndi
Version : 0.11.4.1
Release : 19.fc33
Architecture : noarch
Size : 51 k
Source : simple-jndi-0.11.4.1-19.fc33.src.rpm
Repository : fedora
Summary : A JNDI implementation
URL : https://github.com/hen/osjava
License : BSD
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.