
	Where results make sense

Topic: JNDI

Related Topics

JINI

LDAP

Java RMI

Mount Cook

Lotus Europa

Sibenik

In the News (Tue 22 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	JNDI Swiftlet (Site not responding. Last check: 2007-10-08)
		Every JNDI Swiftlet on each connected router receives this request and replies with the requested JNDI object in case the object with this name is registered at this router.
		JNDI lookups should be performed via a JMS listener on host www.swiftmq.com, port 4020, as user 'johnsmith', password 'ballaballa'.
		JNDI implementation classes have to be into the system classpath of the router, because the JNDI uses the system class loader to load the InitialContext class.
	www.swiftmq.com /products/router/swiftlets/jndi (1451 words)

	JBossNS —The JBoss JNDI Naming Service (Site not responding. Last check: 2007-10-08)
		JNDI serves a similar role in J2EE by enabling developers and administrators to create name-to-object bindings for use in J2EE components.
		JNDI is a standard Java API that is bundled with JDK1.3 and higher.
		The JNDI API is divided logically into a client API that is used to access naming services, and a service provider interface (SPI) that allows the user to create JNDI implementations for naming services.
	www.informit.com /articles/article.asp?p=28281&seqNum=1 (1286 words)

	Using WebLogic JNDI
		JNDI is a standard Java interface for accessing distributed services and data by name.
		The JNDI specification was defined independently of any specific naming or directory service implementation, but a developer can use it to access different, multiple naming and directory services such as LDAP, NDS, and NIS (YP).
		JNDI provides several ways to hook into the object retrieval machinery so that the implementor of a naming service can control what object is ultimately returned to the client performing a lookup.
	www.weblogic.com /docs/classdocs/API_jndi.html (4663 words)

	Java Naming and Directory Interface (JNDI)
		The Java Naming and Directory Interface (JNDI) is part of the Java platform, providing applications based on Java technology with a unified interface to multiple naming and directory services.
		JNDI works in concert with other technologies in the Java 2 Platform, Enterprise Edition (J2EE) to organize and locate components in a distributed computing environment.
		JNDI Tutorial See the latest version of the JNDI Tutorial.
	java.sun.com /products/jndi (338 words)

	NOVELL: DeveloperNet® University - Introducing JNDI
		JNDI is a pure Java interface for general naming systems programming.
		JNDI provides a common layer of abstraction that insulates the application programmer from multiple interfaces for dealing with the naming aspects of an object system.
		Although JNDI provides an interface to access named objects in naming systems, providers are required to implement certain JNDI methods for accessing a particular naming system.
	developer.novell.com /education/nds/jndi/introducing_jndi.html (378 words)

	[No title]
		JNDI defines the notion of a "reference" for use when an object cannot be stored in the directory directly, or when it is inappropriate or undesirable to do so.
		A common use for JNDI references is to represent connections to a network service such as a database, directory, or file system.
		A directory entry containing a JNDI reference is represented by the object class javaNamingReference, which is a subclass of javaObject.
	www.ietf.org /rfc/rfc2713.txt (4401 words)

	J2EE Naming and Directory Services (Site not responding. Last check: 2007-10-08)
		JNDI is a Java API that defines an interface to Naming and Directory Services for Java programs.
		JNDI is just an API and not, in itself, a Naming and Directory Service.
		JNDI is available as a standard Java extension for JDK 1.2 and earlier.
	www.informit.com /articles/article.asp?p=174364&seqNum=3 (1431 words)

	"Directory SDK for Java 4.0 Programmer's Guide": Using the JNDI Service Provider
		JNDI is a Java API that provides a common way for programmers to access a variety of naming and directory services.
		JNDI has a number of environment properties that you can set at the system level or pass directly to the initial context via a Hashtable.
		If a change or addition to the JNDI context environment occurs after an initial context is created, it will be immediately visible unless the changed property pertains to the connection.
	docs.sun.com /source/816-6402-10/jndichap.htm (1408 words)

	JNDI Frequently Asked Questions
		Developers using JNDI can produce queries that use LDAP or other access protocols to retrieve results; however, they are not limited to LDAP nor do they have to develop their applications wired to LDAP.
		JNDI is a generic directory API for Java programs.
		JNDI offers Java applications, regardless of whether they're running on Windows or accessing Active Directory, to access directories using the Java object model.
	java.sun.com /products/jndi/faq.html (695 words)

	The JNDI FAQ
		JNDI has classes provided by Sun that will help your application interact with an LDAP server.
		JNDI applications work similarly to JDBC applications - write applications once and be free to use "drivers" from different vendors.
		JNDI does not provide any connection pooling mechanism.
	www.angelfire.com /electronic/vikram/tech/faq/jndi.html (610 words)

	Code Snippet- JNDI (Site not responding. Last check: 2007-10-08)
		JNDI is defined independent of any specific naming or directory service implementation, so it enables Java applications to access different, possibly multiple naming and directory services using a single API.
		JNDI can be used to look up and locate local and remote EJBs.
		This constructor is used to create a context using the environment properties that are set in the Hashtable variable passed as parameter to the constructor.
	www.oracle.com /technology/sample_code/tech/java/codesnippet/j2ee/JNDI (1067 words)

	JNDI and OpenLDAP Tutorial (Site not responding. Last check: 2007-10-08)
		JNDI can be used as a general purpose service for accessing and retrieving a mixed set of data.
		We let JNDI know that we are trying to access an LDAP server by specifying the LDAP SPI, “com.sun.jndi.LdapCtxFactory” and specify the user name and password as we had stored in the slapd.conf file.
		This tells JNDI what our initial context should be (now that we have a root node object, we can tell JNDI to use it as the initial context).
	www.cris.com /~adhawan/tutorial (2085 words)

	Java Message Service: Chapter 2: Developing a Simple Example
		JNDI is a standard Java extension that provides a uniform API for accessing a variety of directory and naming services.
		Using JNDI, JMS clients can browse a naming service and obtain references to administered objects without knowing the details of the naming service or how it is implemented.
		JNDI is dynamic because it allows the JNDI drivers for specific types of naming and directory services to be loaded dynamically at runtime.
	www.oreilly.com /catalog/javmesser/chapter/ch02.html (3027 words)

	J2EE Naming and Directory Services (Site not responding. Last check: 2007-10-08)
		JNDI is a required technology for J2SE so you do not need to have a full blown J2EE server in order to use JNDI.
		There are several ways of defining the JNDI service properties for a program, but you only need to use one of them.
		This exception usually means the JNDI Server is not running, or possibly the JNDI properties for the server are incorrect.
	www.informit.com /articles/article.asp?p=174364&seqNum=3 (1154 words)

	jndi
		Note: unlike the Local Home Interface example, the reference to the Remote Home Interface is a conventional JNDI name that is generated by WSAD and is visible in the object's Deployment Desciptor.
		It is because WSAD generates a JNDI name to this interface, not the Local interface, that one must use the Reference form shown above.
		The JNDI server is identified by the IIOP protocol prefix, followed by the IP address and port of the server.
	www.cs.unc.edu /Courses/jbs/lessons/enterprise/ejb_jndi (858 words)

	JNDI overview, Part 1: An introduction to naming services
		JNDI provides a common-denominator interface to many existing naming services.
		As such, JNDI was not designed to replace existing technology; instead, it provides a common interface to existing naming services.
		JNDI provides an interface that supports all this common functionality.
	www.javaworld.com /javaworld/jw-01-2000/jw-01-howto.html (1221 words)

	Java Pro - Filtering JNDI Operations (Site not responding. Last check: 2007-10-08)
		During the course of the project schedule you need to make significant changes to the underlying architecture, redefine business processes, or need to identify transactional and performance problems.
		JNDI filters are intended for situations where the developer would, under ideal circumstances, customize the code of an existing resource, but cannot do so under practical circumstances.
		In many cases, modifying the code of a J2EE resource is not an option, and changes need to be loosely coupled around an existing architecture (see Resources).
	www.fawcette.com /javapro/2004_10/magazine/features/blimaye (363 words)

	Chapter 6 JNDI Resources
		JNDI is an application programming interface (API) for accessing different kinds of naming and directory services.
		The JNDI name of a resource and the name of the resource reference are not the same.
		In the JNDI Name field, enter the name that is to be used to access the resource.
	docs.sun.com /source/819-0076/jndi.html (1487 words)

	simple-jndi - Introduction
		This code however is not usable outside of a J2EE container as you cannot guarentee you have a JNDI implementation available, and to be honest, you don't want to start some other server to make your simple script run.
		The first property is a part of the jndi specification, java.naming.factory.initial.
		The second property is simple-jndi specific, com.generationjava.jndi.root is set to a directory containing all the jndi values for this application.
	www.generationjava.com /docs/simple-jndi-docs/docs-0.2/Intro.html (428 words)

	simple-jndi - Introduction
		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.
		This code however is not usable outside of a J2EE container as you cannot guarrentee you have a JNDI implementation available, and to be honest, you don't want to start some other server to make your simple script run.
		This property is a part of the jndi specification, java.naming.factory.initial.
	www.generationjava.com /docs/simple-jndi-docs/docs-0.3/Intro.html (351 words)

	JNDI - a Whatis.com definition (Site not responding. Last check: 2007-10-08)
		JNDI (Java Naming and Directory Interface) enables Java platform-based applications to access multiple naming and directory services.
		Sundsted says that JNDI organizes and locates components within a distributed computing environment similarly to the way that card catalogs (and increasingly computer applications) organize and represent the locations of books within a library.
		The current version, JNDI 1.2, was specified with input from Netscape, Novell, Tarantella, Sun, and BEA.
	searchvb.techtarget.com /gDefinition/0,,sid8_gci752924,00.html (227 words)

	jGuru: JNDI FAQ Home Page
		The Java Naming and Directory Interface (JNDI) is an application programming interface (API) for accessing different kinds of naming and directory services.
		JNDI is not specific to a particular naming or directory service, it can be used to access many different kinds of systems including file systems; distributed objects systems like CORBA, Java RMI, and EJB; and directory services like LDAP, Novell NetWare, and NIS+.
		I suspect that what your JNDI provider is telling you is that it cannot decrypt the password in order to compare it to the value that you have supplied.
	www.jguru.com /faq/home.jsp?topic=JNDI (724 words)

	jGuru: What is JNDI?
		JNDI is similar to JDBC in that they are both Object-Oriented Java APIs that provide a common abstraction for accessing services from different vendors.
		JNDI also has a SPI (Service-Provider Interface) which is a programming model that vendors use to write JNDI plug-ins or implementations for their specific product.
		For the most part, JNDI hides the implementation details of the a service-provider so that Java developer that uses JNDI can use the same objects and method regardless of the brand of naming or directory service accessed.
	www.jguru.com /faq/view.jsp?EID=10852 (355 words)

	ActiveMQ - JNDI Support (Site not responding. Last check: 2007-10-08)
		So we provide a simple JNDI InitialContextFactory which can be used to lookup JMS connection factory objects as well as Destination objects.
		The prefix topic and queue is stripped, so the jndi name begins after the prefix.
		This can be very handy if you can easily reconfigure the JNDI name to use to lookup something in JNDI, but don't want to have to double configure a jndi.properties to matchup.
	activemq.codehaus.org /JNDI+Support (691 words)

	J2EE or J2SE? JNDI works with both
		JNDI is the glue that holds together J2EE (Java 2 Platform, Enterprise Edition) applications.
		JNDI was designed to support highly dynamic application assembly and deployment, with components constantly being added and updated without rebuilding the entire system.
		A JNDI provider uses a variety of techniques, including serialization, to ensure that the object can move from JVM to JVM and still be retrieved in its original form.
	www.javaworld.com /javaworld/jw-04-2002/jw-0419-jndi.html (1137 words)

	Macromedia - JRun LiveDocs : JRun JNDI usage
		JRun includes a JNDI provider that stores and manages the JNDI contexts used by JRun.
		If you look up a service using this JNDI binding in a clustered environment, the context that is returned can be from any of the JRun servers in the cluster.
		For information on using JNDI to look up a JRun service in a clustered environment, see "Using object clustering with JRun services".
	livedocs.macromedia.com /jrun/4/JRun_Administrators_Guide/jndi3.htm (480 words)

	Managing JNDI
		The JNDI tree is represented by the left pane in the Administration Console.
		JNDI provides a common-denominator interface to many existing naming services, such as LDAP (Lightweight Directory Access Protocol) and DNS (Domain Name System).
		To load an object in the JNDI tree, choose a name under which you want the object to appear in the JNDI tree.
	e-docs.bea.com /wls/docs61/adminguide/jndi.html (270 words)

	WebLogic JNDI
		Therefore, it is important to understand the implications of binding an object to the JNDI tree in a clustered environment.
		The JNDI binding for an object can appear in the JNDI tree for one WebLogic Server in the cluster, or it can be replicated to all the WebLogic Servers in the cluster.
		Using the component environment rather than the global environment to set your JNDI name is advantageous because the name it refers to is resolved during deployment.
	e-docs.bea.com /wls/docs81/jndi/jndi.html (4577 words)

Try your search on: Qwika (all wikis)