JNDI in JSE?

Is it possible to use JNDI to fetch an EntityManager(!) in JSE, not JEE?
The alternative I have is store the EM in a Thread(Group) based store and fetch that on demand.

Oh, actually the reason is quite simple: I want to open an EM, store it somewhere and fetch it when I need it versus having to drag it through all method calls.
As said, it can be stored in a Thread based repository, but since JEE is using JNDI to access it, I was thinking that maybe doing something similar in JSE might be practical too.
Can you elaborate on how your suggestion would work? You mean a "Bootstrap" class which opens the EM and holds it in a static variable. Singleton alike?

Similar Messages

JNDI lookup fails for client applications

I am currently porting our j2ee application to weblogic 7.0. The application already
runs successfully on Orion and Jboss. I have got everything working now except
for our client applications, which all fail with a JNDI lookup error. The exception
is:
javax.naming.NameNotFoundException: Unable to resolve 'java:comp.env/ejb/QualiferInstance'
Resolved: '' Unresolved:'java:comp' ; remaining name 'java:comp.env
/ejb/QualifierInstance'
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutbound
equest.java:109)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
ef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
ef.java:229)
at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown Source
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at BatchIndexer.main(BatchIndexer.java:89)
I have looked up numerous postings on various mailing lists describing similar
problems, but none of them give an explanation which helps me.
I am convinced that I have the ejb deployment descriptors correct because all
our JSPs, servlets and session beans successfully lookup and use the EJBs.
I am also convinced that I have the correct code for the JNDI lookup in our client
applications, because they work perfectly well on Orion and Jboss and use syntax
which is described as correct in the jsee specification, i.e. "java:comp/env/..."
Here is the descriptor from weblogic-ejb-jar.xml for the EJB mentioned in the
example exception above:
<weblogic-enterprise-bean>
<ejb-name>QualifierInstance</ejb-name>
<jndi-name>comp/env/ejb/QualifierInstance</jndi-name>
</weblogic-enterprise-bean>
And here is the descriptor in the application-client.xml file:
     <ejb-ref>
          <ejb-ref-name>ejb/QualifierInstance</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>           <home>com.espritsoutron.xengine.ejb.metamodel.QualifierInstanceHome</home>
          <remote>com.espritsoutron.xengine.ejb.metamodel.QualifierInstance</remote>
          <ejb-link>QualifierInstance</ejb-link>
     </ejb-ref>
And here is the code in the client application that attempts to perform the lookup:
qiHome = (QualifierInstanceHome)PortableRemoteObject.narrow(context.lookup("java:comp/env/ejb/QualifierInstance"),
QualifierInstanceHome.class);
The annoying thing is that I know I can make this work if I change the code to
omit the "java:" prefix, but I don't want to do this because then it would no
longer work on either Orion and Jboss.
P.S. I have also tried changing the jndi-name in the weblogic-ejb-jar descriptor
to "ejb/QualifierInstance" and just "QualifierInstance", but neither of these
make any difference. I even tried chaning it to "java:comp/env/ejb/QualifierInstance"
but that totally breaks the server.
Can anyone can please help with this?

you can find the JNDI name in the JNDI tree from the admin console
right click on your server and choose "view jndi tree".
if you bind your ejb to ejb/QualifierInstance
you look it up with that exact same name ejb/QualifierInstance
Julian Fawcett wrote:
I am currently porting our j2ee application to weblogic 7.0. The application already
runs successfully on Orion and Jboss. I have got everything working now except
for our client applications, which all fail with a JNDI lookup error. The exception
is:
javax.naming.NameNotFoundException: Unable to resolve 'java:comp.env/ejb/QualiferInstance'
Resolved: '' Unresolved:'java:comp' ; remaining name 'java:comp.env
/ejb/QualifierInstance'
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutbound
equest.java:109)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
ef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
ef.java:229)
at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown Source
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at BatchIndexer.main(BatchIndexer.java:89)
I have looked up numerous postings on various mailing lists describing similar
problems, but none of them give an explanation which helps me.
I am convinced that I have the ejb deployment descriptors correct because all
our JSPs, servlets and session beans successfully lookup and use the EJBs.
I am also convinced that I have the correct code for the JNDI lookup in our client
applications, because they work perfectly well on Orion and Jboss and use syntax
which is described as correct in the jsee specification, i.e. "java:comp/env/..."
Here is the descriptor from weblogic-ejb-jar.xml for the EJB mentioned in the
example exception above:
<weblogic-enterprise-bean>
<ejb-name>QualifierInstance</ejb-name>
<jndi-name>comp/env/ejb/QualifierInstance</jndi-name>
</weblogic-enterprise-bean>
And here is the descriptor in the application-client.xml file:
     <ejb-ref>
          <ejb-ref-name>ejb/QualifierInstance</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>           <home>com.espritsoutron.xengine.ejb.metamodel.QualifierInstanceHome</home>
          <remote>com.espritsoutron.xengine.ejb.metamodel.QualifierInstance</remote>
          <ejb-link>QualifierInstance</ejb-link>
     </ejb-ref>
And here is the code in the client application that attempts to perform the lookup:
qiHome = (QualifierInstanceHome)PortableRemoteObject.narrow(context.lookup("java:comp/env/ejb/QualifierInstance"),
QualifierInstanceHome.class);
The annoying thing is that I know I can make this work if I change the code to
omit the "java:" prefix, but I don't want to do this because then it would no
longer work on either Orion and Jboss.
P.S. I have also tried changing the jndi-name in the weblogic-ejb-jar descriptor
to "ejb/QualifierInstance" and just "QualifierInstance", but neither of these
make any difference. I even tried chaning it to "java:comp/env/ejb/QualifierInstance"
but that totally breaks the server.
Can anyone can please help with this?

Unable to resolve JNDI DataSource in weblogic 12c When you upgrade web application

I create a datasource which jndi name is jdbc/allianzB2CDataSource and the target is AdminServer ,and i deploy a web application in AdminServer.In that web application,the code(base on spring framework) is:
public static DataSource getJndiDataSource(String name) {
JndiDataSourceLookup dsLookup = new JndiDataSourceLookup();
Properties jndiEnvironment = new Properties();
jndiEnvironment.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
dsLookup.setJndiEnvironment(jndiEnvironment);
try {
dsLookup.setResourceRef(false);
return dsLookup.getDataSource(name);
} catch (Exception e) {
dsLookup.setResourceRef(true);
return dsLookup.getDataSource(name);
And the parameter is jdbc/allianzB2CDataSource,everything work fine,but when i restart or upgrate the web application,i got the error like this:
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'
Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'

I create a datasource which jndi name is jdbc/allianzB2CDataSource and the target is AdminServer ,and i deploy a web application in AdminServer.In that web application,the code(base on spring framework) is:
public static DataSource getJndiDataSource(String name) {
JndiDataSourceLookup dsLookup = new JndiDataSourceLookup();
Properties jndiEnvironment = new Properties();
jndiEnvironment.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
dsLookup.setJndiEnvironment(jndiEnvironment);
try {
dsLookup.setResourceRef(false);
return dsLookup.getDataSource(name);
} catch (Exception e) {
dsLookup.setResourceRef(true);
return dsLookup.getDataSource(name);
And the parameter is jdbc/allianzB2CDataSource,everything work fine,but when i restart or upgrate the web application,i got the error like this:
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'
Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'

LDAP or JNDI Synchronization Across JVMs?

I need to perform an atomic operation (get & set) in
LDAP that is synchronized between multiple
applications (i.e. across JVMs).
Is that possible using iDS 4.x or 5.x?
Does iDS implementation of JNDI/LDAP API provide a
global lock mechanism (I know that this feature is not
supported in the API)?
Here is my actual problem. I need to generate a unique
id of type "long". This id should be unique across
several Java applications. I would like to store this
id in LDAP.
Any help is appreciated.
Thanks, Shahriar

There is no such locking mechanism. Is there a reason the unique id has to be type long? If not, then how about using a UUID? If it needs to be long, perhaps apportioning the number space between applications would work for you.

Easy JNDI + Connection Pool Question

This is an easy question:
Once I get the object represented by my connection pool from the
Weblogic JNDI tree, how do I get a connection from the returned object
of type weblogic.common.internal.ResourceAllocator?
I keep getting ClassCastExceptions. I have tried
ConnectionPoolDataSource, Connection, and DataSource.
String conPool = "weblogic.jdbc.connectionPool.demoPool";
try {
Object obj = ctx.lookup(conPool);
msg(DEBUG,"FROM LOOKUP" + obj.getClass().getName());
//DataSource ds = (DataSource)ctx.lookup(conPool);
//con = ds.getConnection();
} catch (NameNotFoundException e) {
// binding does not exist
msg(ERROR,"BINDING DOES NOT EXIST",e);
} catch (NamingException e) {
// a failure occurred
msg(ERROR,"NAMING FAILURE OCCURED",e);
} catch (Exception e) {
msg(ERROR,"SOME RANDOM ERROR",e);
Thanks,
-Jacob

"Jacob Meushaw" wrote in message
Once I get the object represented by my connection pool from the
Weblogic JNDI tree, how do I get a connection from the returned object
of type weblogic.common.internal.ResourceAllocator?
I keep getting ClassCastExceptions.
DataSource ds = (DataSource)ctx.lookup(conPool);I think, you must use narrow operation:
Object reference = ctx.lookup(conPool);
DataSource ds =
(DataSource) PortableRemoteObject.narrow (ds,DataSource.class);
I haven't got time to check it, but I hope that works.
Wojtek

Help: Connecting Tomcat to CA-IDMS Using JDBC Type 4 Drivers (JNDI)

Hi there,
I have a rather interesting / complex problem......creating a connection to CA-IDMS from Tomcat using JDBC type 4 drivers (CA provide the type 4 driver).
We have a zSeries 9 IBM mainframe running CA-IDMS r16.1, and I need to connect to the IDMS from Tomcat (running on Linux) using the JDBC Type 4 drivers provided by CA.
At this stage I am struggling with the actual setup and configuration of Tomcats server.xml and web.xml files. These are the files where the JDBC configuration is set (I think). I have to setup the CA-IDMS part of the configuration, but that is a different problem. Basically there is a TCP/IP listener on the IDMS, waiting for incoming connections from the JDBC type 4 driver.
I set up a Tomcat to MySQL connection using MySQL Connector / J, which is a similar kind of process to what I am trying to achieve with IDMS. MySQL connector / J came with a jar file which is placed in Tomcats lib folder, and then the JDBC setup for the web application is created in Tomcat's server.xml and web.xml files. You can then connect to the MySQL database using JSP and the configured JDBC driver / connection. The CA-IDMS Server comes with an idmsjdbc.jar file, which I think is the JDBC typr 4 driver. I think it needs to be placed in the Tomcat /lib folder, but I dont know how to set up the configuration.
There is a JDBC DriverManager which allows JDBC drivers to connect to CA-IDMS. The DriverManager recognises the following syntax:
jdbc:idms://hostname:port/database
This allows the JDBC driver running within Tomcat to connect to the IDMS which is running on the IDM mainframe. CA IDMS r16 supports direct connections from the Type 4 JDBC driver to the Central Version on IDMS. "hostname" is the DNS name or IP address of the machine where the CV is running, and "port" is the IP port that was specified for the listener PTERM (setup on the IDMS side).
There is a caidms.properties file for the JDBC driver, which is used to specify user ID, password, and optional accounting information. It can also be used to specify physical connection information, allowing an application to connect to a CA-IDMS database without requiring the definition of an ODBC style data source. However, I dont know where to place this file within the Tomcat setup.
There is also an IdmsDataSource class. I dont know where to configure this or how to set it up; the CA-IDMS Server manual states the following:
This class implements the JDBC DataSource interface. It is used with an application server (Tomcat) providing Java Naming and Directory Interface (JNDI) naming service to establish a connection to a CA IDMS database. IdmsDataSource properties conform to the Java Beans naming conventions and are implicitly defined by public setter and getter methods. For example, the description property, which is required for all DataSource implementations, is set using the setDescription(String) method. The application server may use the java.lang.reflection methods to discover DataSource properties and provide an interface to set them, or may simply require that they are defined in some configuration file. IdmsDataSource properties are used to specify the connection parameters. These properties are the equivalent of the DriverPropertyInfo attributes described in the previous section and can be used to completely define the parameters needed to connect to a database. Like a URL, an IdmsDataSource object can also reference an ODBC style data source name, where the connection parameters are defined in the configuration file on Linux.
Is there anyone that can try to point me in the right direction to setting up the JDBC connection? I am totally new to Java and so the instructions are not making much sense at the moment. Any help, hints, tips..anything will be greatly appreciated as I have just hit a brick wall here. I can't find much to do with setting up the CA-IDMS Server JDBC type 4 driver online either....if anyone can point me to some resources that would also be extremely useful.
Kind regards
Jp

You say you've managed to get the JDBC driver working
in an application but not in a JSP. You also say that
the error you get is
"com.microsoft.jdbc.sqlserver.SQLServerDriver".
I'd be willing to bet that the exception that you have
got is a ClassNotFoundException. I.E. your application
server hasn't found the JDBC driver classes. The
application server probably doesn't use your current
CLASSPATH to look for classes. It will be setup within
the application server in some way and you'll need to
check your app server documentation to see how it is
done.
Try replacing
e.printStackTrace();with
e.printStackTrace(out);to get a full stack trace of your error.
ColTried it. Got this error when I tried to run the JSP.
Incompatible type for method. Can't convert javax.servlet.jsp.JspWriter to java.io.PrintWriter.
e.printStackTrace(out);
I'm currently using Apache Tomcat 4.0.3 as my JSP/Servlet Container.
I'm also using Type 4 MS SQL Server 2000 JDBC driver version 2.0 on my NT4.0 Server.
Do I need to set my JDBC driver in my container? if so, how do I do that?

JMS connection from SAP PI to Oracle AQ via JNDI...

Hi,
I am currently working on a project that requires connections between PI and Oracle AQ. It was advised that we shoule use PI JMS adpater with JNDI driver. However, it seems that not many people have tried this approach.
Has anyone had similar solutions in production ? How repliable it is ?
Your help is very much appreciated
Tim

Hi Tim,
We implemented a similar scenario and now itu2019s still working.
You have to configure a JNDI connection, but not directly with the Oracle AQ. The Oracle AQ are just queues, and you need a JMS provider in order to establish the connection with these queues. The solution we implemented was:
1. Configure one OC4J server as JMS provider for the Oracle AQ queues.
2. Configure JMS communication channels in SAP PI to establish the connection with the OC4J server.
Maybe you can use a different and newer JMS provider, as BEA Weblogic or SAP WAS (I donu2019t know if itu2019s possible).
We implement the scenario in SAP PI 7.0, and with this version we had a problem: When the communication between JMS adapter and the queues was broken (the DDBB fell down for example), the channel failed, itu2019s normal. But when the DDBB was already running the channel stayed in an error state, and we had to restart the channel manually. The response of SAP to this issue was that the channel behavior was correct because the connection failed.
But this problem occurred rarely, maybe once a month. The solution is very reliable, we exchange a lot of message with this solution, and support messages of any size with an excellent performance.
Best Regards,
Roberto

Unable to launch Java Swing application with JSE 5.0

Hi,
we have a swing appln that gets downloaded via java webstart - which was working fine with 1.4.x until 5.0 came. I know that JSE 5.0 includes java webstart too - but when I start my application, I get Marshal error & filenotfound Exception. What we are doing in the application is to download some XML files that are to be used by the program. But the program is unable to find the files.
If I manually install 1.4.x & Web Start separately, everything works fine.....
Is there any change needed in the JNLP file?
TIA

Hi there,
Here's the issue:
I have modified our web page that helps the user download the swing appln - as per the guidelines given in the web site:
http://java.sun.com/j2se/1.5.0/docs/guide/javaws/developersguide/launch.html
Let's say that I already have JRE 1.4x & JWS installed on my m/c. When I visit our web page that downloads / starts the client application, I get an error:
Java Web Start : Invalid Argument Error.
General
An error occurred while launching/running the application.
Category: Invalid Argument error
Could not load file/URL specified: http://myserver:8080/testdev/app/testb.jnlp
Exception
CouldNotLoadArgumentException[ Could not load file/URL specified: http://myserver:8080/testdev/app/testb.jnlp]
     at com.sun.javaws.Main.main(Unknown Source)
Wrapped Exception
java.io.IOException: Service Unavailable : http://myserver:8080/testdev/app/testb.jnlp
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.Main.main(Unknown Source)
If I uninstall JRE 1.4+ & etal - JRE 5.0 gets downloaded and everything works smooth. But I need to take care of backward compatibility... Hence this post....
BTW, the JNLP file looks like:
<?xml version="1.0" encoding="utf-8"?>
<jnlp spec="1.0+"
     codebase="$$codebase"
     href="testb.jnlp">
<information>
<title>Test Application</title>
<vendor>TP</vendor>
<homepage href="help.htm"/>
<description>TEST Application using Java Web Start </description>
<description kind="short">TEST Application.</description>
<icon href="logocropped.jpg"/>
<icon kind="splash" href="logocropped.jpg"/>
<offline-allowed/>
</information>
<resources>
<j2se version="1.4+"/>
<jar href="bars.jar" part="lpc" />
<jar href="castor-0.9.4.3.jar" part="lpc" download="eager" />
<jar href="xercesImpl.jar" download="eager"/>
<jar href="xmlParserAPIs.jar" download="eager"/>
<jar href="bsh-1.2b6.jar" download="eager"/>
<jar href="gnujaxp.jar" download="eager"/>
<jar href="itext-0.99.jar" download="eager"/>
<jar href="jcommon-0.8.2.jar" download="eager"/>
<jar href="junit.jar" download="eager"/>
<jar href="pixie-0.8.0.jar" download="eager"/>
<jar href="BarsUtil.jar" download="eager"/>
</resources>
<application-desc main-class="bars.Bars"/>
<security>
<all-permissions/>
</security>
</jnlp>
Is there a version incompatibility issue that I need to take care of ?
TIA for any help/direction......

Some JMS objects do not show up in JNDI tree

Hello friends. I have a situation where some of my JMS Queues do not show up in
the JNDI tree. Other Queues / Topics show up fine. I cannot find any difference
in the interface that tells me what my cause this to happen. Any insight would
be appreciated.
brian

are you using a cluster? if so check the multicast to see if its working
right.
Where are you looking up the JNDI tree? in the console or are you checking
the JNDI tree via weblogic.Admin LIST command? the LIST command may be a
better way to see it for sure.
sree
"Brian" <[email protected]> wrote in message
news:40b74519$1@mktnews1...
>
Hello friends. I have a situation where some of my JMS Queues do not showup in
the JNDI tree. Other Queues / Topics show up fine. I cannot find anydifference
in the interface that tells me what my cause this to happen. Any insightwould
be appreciated.
brian

EJB 3.0 and jndi lookup (simple question)

hi all,
i am newbie on Weblogic Application Server and i have some issues,
i have weblogic application server 10.0, also i have oracle timesten in-memory database, i have configured datasource and deploy my ejb 3.0 application, but i could not done jndi lookup?
here is my example:
1. one stateless session bean :
import javax.ejb.Remote;
@Remote
public interface InsertSubscriber {
     public void insertSubscriber(SubscriberT subscriberT);
} 2. here is it's implementation :
@Remote(InsertSubscriber.class)
@Stateless
public class InsertSubscriberBean implements InsertSubscriber {
     @PersistenceContext(unitName = "TimesTenDS")
     private EntityManager oracleManager;
     public void insertSubscriber(SubscriberT subscriber)
          try {
               System.out.println("started");
               oracleManager.persist(subscriber);
               System.out.println("end");
          } catch (Exception e) {
               e.printStackTrace();
}3 and my test client :
public class Client {
     public static void main(String[] args) {
          Context ctx = null;
          Hashtable ht = new Hashtable();
          ht.put(Context.INITIAL_CONTEXT_FACTORY,
                    "weblogic.jndi.WLInitialContextFactory");
          ht.put(Context.PROVIDER_URL, "t3://192.9.200.222:7001");
          try {
               ctx = new InitialContext(ht);
               InsertSubscriber usagefasade = (InsertSubscriber) ctx
                         .lookup("ejb.InsertSubscriberBean");
          } catch (NamingException e) {
               e.printStackTrace();
          } finally {
               try {
                    ctx.close();
               } catch (Exception e) {
                    e.printStackTrace();
}what i did incorrect ???
i got error like this : Name not fount exception
when i tried to view jndi tree on weblogic server application console i found this :
     Binding Name:
TimestenExampleTimestenExample_jarInsertSubscriberBean_InsertSubscriber
     Class:
test.InsertSubscriberBean_o7jk9u_InsertSubscriberImpl_1000_WLStub
     Hash Code:
286
     toString Results:
weblogic.rmi.internal.CollocatedRemoteRef - hostID: '2929168367193491522S::billing_domain:AdminServer', oid: '286', channel: 'null'what does it mean how i can done lookup to jndi ?
Regards,
Paata Lominadze,
Magticom LTD.
Georgia.

Hi All,
I am using the weblogic cluster with session replication and EJB 2.0 with Local entity beans.
for fail-over session should be replicated to another server so we can achive the same session if 1st server fails.
Suppose i m using two managed server(server1,server2) in the cluster.I am storing the object of class ABC into session and object contains the instance of Local-EntityBean home but i put that as a transient.I have also override the readObject and write object method.
when write object is called on 1st server,readObject method should be called on second server so we will be sure that session is replicating properly.
pleaase find the code below : -
public IssuerPageBean() {
initEJB();
private void readObject(java.io.ObjectInputStream stream) throws IOException, ClassNotFoundException {
stream.defaultReadObject();
initEJB();
initializeCommonObject();
private void writeObject(java.io.ObjectOutputStream stream) throws IOException {
stream.defaultWriteObject();
private void initEJB() {
try {
ic = new InitialContext();
issuerHome = (LocalIssuerHome) ic.lookup("java:comp/env/Issuer");
} catch (NamingException e) {
e.printStackTrace();
in my case if i am calling the constructor IssuerPageBean(),it calls the initEJB() method and lookeup the entity local home properly but when readObject method is called on another server only initEJB() method is called directly and getting the exception below :
WARNING: Error during create -
javax.naming.NameNotFoundException: remaining name: env/ejb/Client
at weblogic.j2eeclient.SimpleContext.resolve(Ljavax/naming/Name;Z)Ljavax/naming/Context;(SimpleContext.java:35)
at weblogic.j2eeclient.SimpleContext.resolve(Ljavax/naming/Name;)Ljavax/naming/Context;(SimpleContext.java:39)
at weblogic.j2eeclient.SimpleContext.lookup(Ljavax/naming/Name;)Ljava/lang/Object;(SimpleContext.java:57)
at weblogic.j2eeclient.SimpleContext.lookup(Ljavax/naming/Name;)Ljava/lang/Object;(SimpleContext.java:57)
at weblogic.j2eeclient.SimpleContext.lookup(Ljava/lang/String;)Ljava/lang/Object;(SimpleContext.java:62)
at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(Ljava/lang/String;)Ljava/lang/Object;(ReadOnlyCont
extWrapper.java:45)
at weblogic.jndi.internal.AbstractURLContext.lookup(Ljava/lang/String;)Ljava/lang/Object;(AbstractURLContext.jav
a:130)
at javax.naming.InitialContext.lookup(Ljava/lang/String;)Ljava/lang/Object;(InitialContext.java:347)
at com.lb.equities.veda.tools.salesvault.jsp.ClientPageBean.initEJB()V(ClientPageBean.java:218)
at com.lb.equities.veda.tools.salesvault.jsp.ClientPageBean.readObject(Ljava/io/ObjectInputStream;)V(ClientPageB
ean.java:191)
at java.lang.LangAccessImpl.readObject(Ljava/lang/Class;Ljava/lang/Object;Ljava/io/ObjectInputStream;)V(Unknown
Source)
at java.io.ObjectStreamClass.invokeReadObject(Ljava/lang/Object;Ljava/io/ObjectInputStream;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava/lang/Object;Ljava/io/ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava/lang/Object;(Unknown Source)
at java.util.HashMap.readObject(Ljava/io/ObjectInputStream;)V(Unknown Source)
at java.lang.LangAccessImpl.readObject(Ljava/lang/Class;Ljava/lang/Object;Ljava/io/ObjectInputStream;)V(Unknown
Source)
at java.io.ObjectStreamClass.invokeReadObject(Ljava/lang/Object;Ljava/io/ObjectInputStream;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava/lang/Object;Ljava/io/ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Ljava/lang/Object;Ljava/io/ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Ljava/lang/Object;Ljava/io/ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava/lang/Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava/lang/Object;(Unknown Source)
at weblogic.common.internal.ChunkedObjectInputStream.readObject()Ljava/lang/Object;(ChunkedObjectInputStream.jav
a:120)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(Ljava/lang/Class;)Ljava/lang/Object;(MsgAbbrevInputStream.java:
121)
at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(ILweblogic/rmi/spi/InboundRequest;Lweblogic/rmi
/spi/OutboundResponse;Ljava/lang/Object;)Lweblogic/rmi/spi/OutboundResponse;(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(Lweblogic/rmi/extensions/server/RuntimeMethodDescriptor;Lweblogic
/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;)V(BasicServerRef.java:492)
Please help .
Thanks in Advance.
Edited by hforever at 03/04/2008 7:28 AM

New version of JDev causing JNDI problems

We just upgraded to the newest Developer Preview of JDEV and all of a sudden client code that compiled and ran fine under the old version is no longer running. I'm guessing something changed in the libraries, but I'm not sure what and why this is occurring.
Here's what happened:
1) It seems that the constructor for InitialContext having a parameter for Properties is no longer available. PITA...but whatever, I switched it to use the Hashtable environment which should I figured work. However:
2) Upon switching to the new environment passage I get an exception:
javax.naming.CommunicationException with the topmost stacked function being oracle.oc4j.security.KeyExchange.getKeyAgreement.
I'm guessing that passing the string password into the environment is no longer acceptable?!? WTF!
So, does anyone have any suggestions to fix this. I'm sure we should be using jndi.properties and all that jazz, but we have tons of client code that works this way and I'm not about to go changing it all unless I really have to.
edit: I tried a sample piece of code using jndi.properties file and am getting the same exception. Maybe this is a problem between the two libraries (OC4J server & the lib on JDev??) GRRRRRRR!
Message was edited by:
[email protected]

OK...turned out to be the second one. I guess the new JDEV libs aren't compatible with the older server I'm running? I just had to remove all the Jdev libraries from the project and point them to the libs within the server install.
So...if anyone else runs into this...that's how I fixed it. Sorry I wasted y'alls time and threadspace :D.

Problem with JNDI and JSP in Tomcat

Hi,
Basically, what I've done is to use the Tomcat administration web
application to create the DataSource, which looks like it populated the
server.xml (see below). I then try to access the testconn.jsp, and am
getting that "Name java:comp is not bound in this Context" error.
I was wondering if anyone could tell me what I'm doing wrong?
Thanks,
Feri
My Configuration:
- Tomcat 5.0.19
- MySQL 4.0.18-nt
- mysql-connector-java-3.0.15-ga-bin.jar
server.xml:
<GlobalNamingResources>

<Environment name="simpleValue" type="java.lang.Integer" value="30"/>

<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>

     <Context crossContext="true" debug="5" docBase="injury" path="/injury" reloadable="true">
     <Logger className="org.apache.catalina.logger.FileLogger" prefix="localhost_injury_log." suffix=".txt" timestamp="true"/>
          <Resource name="jdbc/injury" auth="Container"
type="javax.sql.DataSource">
</Resource>
<ResourceParams name="jdbc/injury">
     <parameter>
          <name>factory</name>
          <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
     </parameter>
<parameter>
<name>username</name>
<value>root</value>
</parameter>
<parameter>
<name>password</name>
<value>root</value>
</parameter>
     <parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.Driver</value>
</parameter>
     <parameter>
<name>url</name>
<value>jdbc:mysql://localhost:3306/injury</value>
</parameter>
     <parameter>
          <name>maxIdle</name>
          <value>30</value>
     </parameter>
     <parameter>
          <name>maxActive</name>
          <value>10</value>
     </parameter>
     <parameter>
          <name>maxWait</name>
          <value>10000</value>
     </parameter>
</ResourceParams>
     </Context>

</GlobalNamingResources>
\webapps\injury\WEB-INF\web.xml:
<resource-ref>
<description>Resource reference to a factory for java.sql.Connection instances that may be used for talking to a particular database that is configured in the server.xml file.</description>
<res-ref-name>jdbc/injury</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
\webapps\injury\testconn.jsp
<%@ page import="java.sql.*" %>
<%@ page import="javax.sql.*" %>
<%@ taglib prefix="ct" uri="/injury" %>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1250">
<h1>Connection test</h1>
<ct:connection name="jdbc/injury">
<%
Statement stmt= conn.createStatement();
ResultSet rs;
rs = stmt.executeQuery("select * from user");
while (rs.next()){
%><%=rs.getString(1)%><%=rs.getInt(2) %><br><%
rs.close();
stmt.close();
%>
</ct:connection>
ConnectionTag.java
import java.io.*;
import java.sql.*;
import javax.servlet.*;
import javax.servlet.jsp.*;
import javax.servlet.jsp.tagext.*;
import javax.naming.*;
import javax.sql.*;
import javax.sql.DataSource;
public class ConnectionTag extends TagSupport implements TryCatchFinally {
private Connection conn;
// JNDI name of the connection
private String name;
public void setName(String name)
     this.name = name;
public int doStartTag()
     throws JspException
     try {
     Context env = (Context) new InitialContext().lookup("java:comp/env");
     DataSource ds = (DataSource) env.lookup(name);
     if (ds != null)
          conn = ds.getConnection();
     } catch (Exception e) {
     throw new JspException(e);
     if (conn == null)
     throw new JspException("can't open connection " + name);
     pageContext.setAttribute("conn", conn);
     return EVAL_BODY_INCLUDE;
public void doCatch(Throwable t)
     throws Throwable
     throw t;
public void doFinally()
     try {
     Connection conn = this.conn;
     this.conn = null;
     pageContext.removeAttribute("conn");
     conn.close();
     } catch (Exception e) {
Tomcat 5.0\conf\Catalina\localhost\injury.xml
<?xml version='1.0' encoding='utf-8'?>
<Context displayName="Injury" docBase="E:\Tomcat 5.0\webapps\injury" path="/injury" className="org.apache.catalina.core.StandardContext"
cachingAllowed="true" charsetMapperClass="org.apache.catalina .util.CharsetMapper" cookies="true" crossContext="false" debug="0"
mapperClass="org.apache.catalina.core.StandardContextMapper" useNaming="true" wrapperClass="org.apache.catalina.core.StandardWrapper" >
<Resource auth="Container" description="Resource reference to a factory for java.sql.Connection instances that may be used for talking to a particular database that is configured in the server.xml file." name="jdbc/injury" type="javax.sql.DataSource"/>
<ResourceLink global="jdbc/injury" name="injury" type="javax.sql.DataSource"/>
</Context>

Hi,
First of all, you can find alot of information about this in the forum about jsp's.
I think a good thing to do is not to put your context tag directly into the server.xml file.
What you should do is create a context.xml file with the context-tag in it, and put it in the META-INF directory of your .war file. Upon deployment to tomcat5 this file will be extracted from the war, copied to the conf\enginename\hostname directory, and it will be renamed to contextName.xml.
I think you are developing directly into the webapps directory, and I believe you should avoid that and use the deployment feature of the manager web-app or you should use the deployertool from you ide or standalone ant.
anyway, for starters try to remove the context tag from the server.xml file as described above, and check out the jsp / jdbc forums for simular problems and answers.
good luck

Problem with JNDI in WLS 5.1

Hi all,
i have a problem with JNDI in WLE 5.1.
i am accessing an LDAP on another machine running Netscape Directory Server.
The host URL is ldap://myhost:65535/o=marco, c=fi
i am always getting back the following exception:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.
WLInitialContextFactory. Root exception is java.lang.ClassCastException: weblog
ic.jndi.WLInitialContextFactory
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
58)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242
at javax.naming.InitialContext.init(InitialContext.java:218)
at javax.naming.InitialContext.<init>(InitialContext.java:194)
and my code is this:
Hashtable _environment = new Hashtable();
try {
environment.put(Context.INITIALCONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
environment.put(Context.PROVIDERURL, "ldap://myhost:65535");
if ((principal!=null) || (credentials!=null)) {
environment.put(Context.SECURITYAUTHENTICATION, "simple");
environment.put(Context.SECURITYPRINCIPAL, principal);
environment.put(Context.SECURITYCREDENTIALS, credentials);
context = new InitialContext(environment);
parser = context.getNameParser(initialCtxFactory);
} catch(Exception e) {
e.printStackTrace();
can anyone help me please??
thanx in advance
marco

Take out the "weblogic.jndi.WLInitialContextFactory" and add the respective factory NAME..
environment.put(Context.INITIALCONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
Cheers,
Naggi
Senthil Kumar S wrote:
http://weblogic.com/docs51/classdocs/API_jndi.html#delegate
Marco wrote:
Hi all,
i have a problem with JNDI in WLE 5.1.
i am accessing an LDAP on another machine running Netscape Directory Server.
The host URL is ldap://myhost:65535/o=marco, c=fi
i am always getting back the following exception:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.
WLInitialContextFactory. Root exception is java.lang.ClassCastException: weblog
ic.jndi.WLInitialContextFactory
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
58)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242
at javax.naming.InitialContext.init(InitialContext.java:218)
at javax.naming.InitialContext.<init>(InitialContext.java:194)
and my code is this:
Hashtable _environment = new Hashtable();
try {
environment.put(Context.INITIALCONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
environment.put(Context.PROVIDERURL, "ldap://myhost:65535");
if ((principal!=null) || (credentials!=null)) {
environment.put(Context.SECURITYAUTHENTICATION, "simple");
environment.put(Context.SECURITYPRINCIPAL, principal);
environment.put(Context.SECURITYCREDENTIALS, credentials);
context = new InitialContext(environment);
parser = context.getNameParser(initialCtxFactory);
} catch(Exception e) {
e.printStackTrace();
can anyone help me please??
thanx in advance
marco--
http://www.net4tech.com

Problem with OpenLDAP and JNDI

I'm having problem working with OpenLDAP and JNDI.
First I have changed LDAP's slapd.conf file:
suffix          "dc=antipodes,dc=com"
rootdn          cn=Manager,dc=antipodes,dc=com
directory     "C:/Program Files/OpenLDAP/data"
rootpw          secret
schemacheck offthan i used code below, to create root context:
package test;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.naming.NameAlreadyBoundException;
import javax.naming.directory.*;
import java.util.*;
public class MakeRoot {
     final static String ldapServerName = "localhost";
     final static String rootdn = "cn=Manager,dc=antipodes,dc=com";
     final static String rootpass = "secret";
     final static String rootContext = "dc=antipodes,dc=com";
     public static void main( String[] args ) {
               // set up environment to access the server
               Properties env = new Properties();
               env.put( Context.INITIAL_CONTEXT_FACTORY,
                          "com.sun.jndi.ldap.LdapCtxFactory" );
               env.put( Context.PROVIDER_URL, "ldap://" + ldapServerName + "/" );
               env.put( Context.SECURITY_PRINCIPAL, rootdn );
               env.put( Context.SECURITY_CREDENTIALS, rootpass );
               try {
                         // obtain initial directory context using the environment
                         DirContext ctx = new InitialDirContext( env );
                         // now, create the root context, which is just a subcontext
                         // of this initial directory context.
                         ctx.createSubcontext( rootContext );
               } catch ( NameAlreadyBoundException nabe ) {
                         System.err.println( rootContext + " has already been bound!" );
               } catch ( Exception e ) {
                         System.err.println( e );
}this worked fine, I could see that by using "LDAP Browser/Editor".
and then I tried to create group with code:
package test;
import java.util.Hashtable;
import javax.naming.*;
import javax.naming.ldap.*;
import javax.naming.directory.*;
public class MakeGroup
     public static void main (String[] args)
          Hashtable env = new Hashtable();
          String adminName = "cn=Manager,dc=antipodes,dc=com";
          String adminPassword = "secret";
          String ldapURL = "ldap://127.0.0.1:389";
          String groupName = "CN=Evolution,OU=Research,DC=antipodes,DC=com";
          env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
          //set security credentials, note using simple cleartext authentication
          env.put(Context.SECURITY_AUTHENTICATION,"simple");
          env.put(Context.SECURITY_PRINCIPAL,adminName);
          env.put(Context.SECURITY_CREDENTIALS,adminPassword);
          //connect to my domain controller
          env.put(Context.PROVIDER_URL,ldapURL);
          try {
               // Create the initial directory context
               LdapContext ctx = new InitialLdapContext(env,null);
               // Create attributes to be associated with the new group
                    Attributes attrs = new BasicAttributes(true);
               attrs.put("objectClass","group");
               attrs.put("samAccountName","Evolution");
               attrs.put("cn","Evolution");
               attrs.put("description","Evolutionary Theorists");
               //group types from IAds.h
               int ADS_GROUP_TYPE_GLOBAL_GROUP = 0x0002;
               int ADS_GROUP_TYPE_DOMAIN_LOCAL_GROUP = 0x0004;
               int ADS_GROUP_TYPE_LOCAL_GROUP = 0x0004;
               int ADS_GROUP_TYPE_UNIVERSAL_GROUP = 0x0008;
               int ADS_GROUP_TYPE_SECURITY_ENABLED = 0x80000000;
               attrs.put("groupType",Integer.toString(ADS_GROUP_TYPE_UNIVERSAL_GROUP + ADS_GROUP_TYPE_SECURITY_ENABLED));
               // Create the context
               Context result = ctx.createSubcontext(groupName, attrs);
               System.out.println("Created group: " + groupName);
               ctx.close();
          catch (NamingException e) {
               System.err.println("Problem creating group: " + e);
}got the error code: Problem creating group: javax.naming.directory.InvalidAttributeIdentifierException: [LDAP: error code 17 - groupType: attribute type undefined]; remaining name 'CN=Evolution,OU=Research,DC=antipodes,DC=com'
I tried by creating organizational unit "ou=Research" from "LDAP Browser/Editor", and then running the same code -> same error.
also I have tried code for adding users:
package test;
import java.util.Hashtable;
import javax.naming.ldap.*;
import javax.naming.directory.*;
import javax.naming.*;
import javax.net.ssl.*;
import java.io.*;
public class MakeUser
     public static void main (String[] args)
          Hashtable env = new Hashtable();
          String adminName = "cn=Manager,dc=antipodes,dc=com";
          String adminPassword = "secret";
          String userName = "cn=Albert Einstein,ou=Research,dc=antipodes,dc=com";
          String groupName = "cn=All Research,ou=Research,dc=antipodes,dc=com";
          env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
          //set security credentials, note using simple cleartext authentication
          env.put(Context.SECURITY_AUTHENTICATION,"simple");
          env.put(Context.SECURITY_PRINCIPAL,adminName);
          env.put(Context.SECURITY_CREDENTIALS,adminPassword);
          //connect to my domain controller
          env.put(Context.PROVIDER_URL, "ldap://127.0.0.1:389");
          try {
               // Create the initial directory context
               LdapContext ctx = new InitialLdapContext(env,null);
               // Create attributes to be associated with the new user
                    Attributes attrs = new BasicAttributes(true);
               //These are the mandatory attributes for a user object
               //Note that Win2K3 will automagically create a random
               //samAccountName if it is not present. (Win2K does not)
               attrs.put("objectClass","user");
                    attrs.put("samAccountName","AlbertE");
               attrs.put("cn","Albert Einstein");
               //These are some optional (but useful) attributes
               attrs.put("giveName","Albert");
               attrs.put("sn","Einstein");
               attrs.put("displayName","Albert Einstein");
               attrs.put("description","Research Scientist");
                    attrs.put("userPrincipalName","[email protected]");
                    attrs.put("mail","[email protected]");
               attrs.put("telephoneNumber","999 123 4567");
               //some useful constants from lmaccess.h
               int UF_ACCOUNTDISABLE = 0x0002;
               int UF_PASSWD_NOTREQD = 0x0020;
               int UF_PASSWD_CANT_CHANGE = 0x0040;
               int UF_NORMAL_ACCOUNT = 0x0200;
               int UF_DONT_EXPIRE_PASSWD = 0x10000;
               int UF_PASSWORD_EXPIRED = 0x800000;
               //Note that you need to create the user object before you can
               //set the password. Therefore as the user is created with no
               //password, user AccountControl must be set to the following
               //otherwise the Win2K3 password filter will return error 53
               //unwilling to perform.
                    attrs.put("userAccountControl",Integer.toString(UF_NORMAL_ACCOUNT + UF_PASSWD_NOTREQD + UF_PASSWORD_EXPIRED+ UF_ACCOUNTDISABLE));
               // Create the context
               Context result = ctx.createSubcontext(userName, attrs);
               System.out.println("Created disabled account for: " + userName);
               //now that we've created the user object, we can set the
               //password and change the userAccountControl
               //and because password can only be set using SSL/TLS
               //lets use StartTLS
               StartTlsResponse tls = (StartTlsResponse)ctx.extendedOperation(new StartTlsRequest());
               tls.negotiate();
               //set password is a ldap modfy operation
               //and we'll update the userAccountControl
               //enabling the acount and force the user to update ther password
               //the first time they login
               ModificationItem[] mods = new ModificationItem[2];
               //Replace the "unicdodePwd" attribute with a new value
               //Password must be both Unicode and a quoted string
               String newQuotedPassword = "\"Password2000\"";
               byte[] newUnicodePassword = newQuotedPassword.getBytes("UTF-16LE");
               mods[0] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("unicodePwd", newUnicodePassword));
               mods[1] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("userAccountControl",Integer.toString(UF_NORMAL_ACCOUNT + UF_PASSWORD_EXPIRED)));
               // Perform the update
               ctx.modifyAttributes(userName, mods);
               System.out.println("Set password & updated userccountControl");
               //now add the user to a group.
                    try     {
                         ModificationItem member[] = new ModificationItem[1];
                         member[0]= new ModificationItem(DirContext.ADD_ATTRIBUTE, new BasicAttribute("member", userName));
                         ctx.modifyAttributes(groupName,member);
                         System.out.println("Added user to group: " + groupName);
                    catch (NamingException e) {
                          System.err.println("Problem adding user to group: " + e);
               //Could have put tls.close() prior to the group modification
               //but it seems to screw up the connection or context ?
               tls.close();
               ctx.close();
               System.out.println("Successfully created User: " + userName);
          catch (NamingException e) {
               System.err.println("Problem creating object: " + e);
          catch (IOException e) {
               System.err.println("Problem creating object: " + e);               }
}same error.
I haven't done any chages to any schema manually.
I know I'm missing something crucial but have no idea what. I have tried many other code from tutorials from net, but they are all very similar and throwing the same error I showed above.
thanks in advance for help.

I've solved this.
The problem was that all codes were using classes from Microsoft Active Directory, and they are not supported in OpenLDAP (microsoft.schema in OpenLDAP is just for info). Due to this some fields are not the same in equivalent classes ("user" and "person").
so partial code for creating user in root would be:
import java.util.Hashtable;
import javax.naming.ldap.*;
import javax.naming.directory.*;
import javax.naming.*;
import javax.net.ssl.*;
import java.io.*;
public class MakeUser
     public static void main (String[] args)
          Hashtable env = new Hashtable();
          String adminName = "cn=Manager,dc=antipodes,dc=com";
          String adminPassword = "secret";
          String userName = "cn=Albert Einstein,ou=newgroup,dc=antipodes,dc=com";
          env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
          //set security credentials, note using simple cleartext authentication
          env.put(Context.SECURITY_AUTHENTICATION,"simple");
          env.put(Context.SECURITY_PRINCIPAL,adminName);
          env.put(Context.SECURITY_CREDENTIALS,adminPassword);
          //connect to my domain controller
          env.put(Context.PROVIDER_URL, "ldap://127.0.0.1:389");
          try {
               // Create the initial directory context
               LdapContext ctx = new InitialLdapContext(env,null);
               // Create attributes to be associated with the new user
                    Attributes attrs = new BasicAttributes(true);
                              attrs.put("objectClass","user");
               attrs.put("cn","Albert Einstein");
               attrs.put("userPassword","Nale");
               attrs.put("sn","Einstein");
               attrs.put("description","Research Scientist");
               attrs.put("telephoneNumber","999 123 4567");
               // Create the context
               Context result = ctx.createSubcontext(userName, attrs);
               System.out.println("Successfully created User: " + userName);
          catch (NamingException e) {
               System.err.println("Problem creating object: " + e);
}hope this will help anyone.

How to setup a JNDI connection from Crystal report 12 (2008) ?

I've CR 12 (2008)
I've a report actually bind to datasource via DSN to a sql server.
Now we need to migrate this connection to JDBC.
So i downloaded microsft sql driver for jdbc and copied as
C:\Program Files (x86)\Business Objects\Common\4.0\java/lib/external/sqljdbc4.jar
I edited CRConfig.xml. adding this full path and file name at <Classpath>
The parameters i entered are:
URL: jdbc:sqlserver://10.1.2.40:1433;DatabaseName=CPR;username=selyon;password=......
class name: com.microsoft.sqlserver.jdbc.SQLServerDriver
in the second page i entere my usernmae, my password and the db name,
but when click on 'finish' CR tell me 'unable to fine JNDI driver'.
What's the problem now

Sorry, but I'm not on a home pc, I'm working on a virtualized pc with a long chain of permissions ... so I cannot simply download and run an utility...
Instead... I think (I WAS thinking) someone from SAP can tell me this info ... Probably I'll buy a paid assistance ticket... But really it's a strange thing that a simply connection from a (so) paid software need a so difficult problem solving routine..
I edited my environment variales: JAVA, PATH; CLASSPATH; JAVA_DIR, and a long list of others ... to ALL point to ALL of directory containing used jars...
.. I asked my SysAdmin to edit CrConfig.xml and it's done ... classpath are rights, jdbc infos are also ok, ...
.. but none ...

JNDI in JSE?

Similar Messages

Maybe you are looking for