I assumed that the ldap jars were part of java1.3. Still, I put the two
ldap jars (ldap.jar and ldapbp.jar) into the lib/ext directory.
This gave the following trace:
[AutoDeployer] Auto deploy of
file:/export/home/nick/servers/jboss/JBoss-2.4.0BETA/deploy/admin-ejb.jar
[J2EE Deployer Default] Deploy J2EE application:
file:/export/home/nick/servers/jboss/JBoss-2.4.0BETA/deploy/admin-ejb.jar
[J2EE Deployer Default] Create application admin-ejb.jar
[J2EE Deployer Default] install module admin-ejb.jar
[Container factory]
Deploying:file:/export/home/nick/servers/jboss/JBoss-2.4.0BETA/tmp/deploy/Default/admin-ejb.jar
[Verifier] Verifying
file:/export/home/nick/servers/jboss/JBoss-2.4.0BETA/tmp/deploy/Default/admin-ejb.jar/ejb1004.jar
[Container factory] Deploying ClientEJB
[Container factory] javax.naming.NamingException. Root exception is
java.net.MalformedURLException: Not an LDAP URL: ldap:
[Container factory] at
com.sun.jndi.ldap.LdapURL.parse(LdapURL.java:89)
[Container factory] at
com.sun.jndi.ldap.LdapURL.<init>(LdapURL.java:73)
[Container factory] at
com.sun.jndi.url.ldap.ldapURLContextFactory.getUsingURLIgnoreRootDN(ldapURLContextFactory.java:54)
[Container factory] at
com.sun.jndi.url.ldap.ldapURLContext.getRootURLContext(ldapURLContext.java:47)
[Container factory] at
com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
[Container factory] at
com.sun.jndi.url.ldap.ldapURLContext.lookup(ldapURLContext.java:80)
[Container factory] at
javax.naming.InitialContext.lookup(InitialContext.java:350)
[Container factory] at
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.rebind(JRMPContainerInvoker.java:580)
[Container factory] at
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.start(JRMPContainerInvoker.java:269)
[Container factory] at
org.jboss.ejb.StatefulSessionContainer.start(StatefulSessionContainer.java:228)
[Container factory] at
org.jboss.ejb.Application.start(Application.java:218)
[Container factory] at
org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:370)
[Container factory] at
org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:304)
[Container factory] at java.lang.reflect.Method.invoke(Native
Method)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[Container factory] at
org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:486)
[Container factory] at
org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:464)
[Container factory] at
org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:208)
[Container factory] at java.lang.reflect.Method.invoke(Native
Method)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[Container factory] at
org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:379)
[Container factory] at
org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:217)
[Container factory] at java.lang.Thread.run(Thread.java:484)
[J2EE Deployer Default] Starting admin-ejb.jar failed!
[Default] org.jboss.ejb.DeploymentException: Could not deploy
file:/export/home/nick/servers/jboss/JBoss-2.4.0BETA/tmp/deploy/Default/admin-ejb.jar,
Cause:javax.naming.NamingException [Root exception is
java.net.MalformedURLException: Not an LDAP URL: ldap:]
[Default] at
org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:402)
[Default]
[Default] at
org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:304)
[Default]
[Default] at java.lang.reflect.Method.invoke(Native Method)
[Default]
[Default] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[Default]
[Default] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[Default]
[Default] at
org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:486)
[Default]
[Default] at
org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:464)
[Default]
[Default] at
org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:208)
[Default]
[Default] at java.lang.reflect.Method.invoke(Native Method)
[Default]
[Default] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[Default]
[Default] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[Default]
[Default] at
org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:379)
[Default]
[Default] at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:217)
[Default]
[Default] at java.lang.Thread.run(Thread.java:484)
[Default]
[J2EE Deployer Default] Module admin-ejb.jar is not running
[J2EE Deployer Default] Destroying application admin-ejb.jar
[AutoDeployer] Deployment
failed:file:/export/home/nick/servers/jboss/JBoss-2.4.0BETA/deploy/admin-ejb.jar
[AutoDeployer] org.jboss.deployment.J2eeDeploymentException: Error while
starting admin-ejb.jar: Could not deploy
file:/export/home/nick/servers/jboss/JBoss-2.4.0BETA/tmp/deploy/Default/admin-ejb.jar,
Cause: org.jboss.ejb.DeploymentException: Could not deploy
file:/export/home/nick/servers/jboss/JBoss-2.4.0BETA/tmp/deploy/Default/admin-ejb.jar,
Cause:javax.naming.NamingException [Root exception is
java.net.MalformedURLException: Not an LDAP URL: ldap:]
[AutoDeployer] at
org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:511)
[AutoDeployer] at
org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:464)
[AutoDeployer] at
org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:208)
[AutoDeployer] at java.lang.reflect.Method.invoke(Native Method)
[AutoDeployer] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[AutoDeployer] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[AutoDeployer] at
org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:379)
[AutoDeployer] at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:217)
[AutoDeployer] at java.lang.Thread.run(Thread.java:484)
....... it looks as though the url is getting ground up somewhere?
Scott M Stark wrote:
>
> No, where are the ldap provider jars on the classpath? A resource-env-ref is
> just an alias to an existing binding in JNDI that has been created by
> an adimistrator. It causes nothing to be created other than an alias from
> the bean ENC to the existing binding.
>
> ----- Original Message -----
> From: "Nick Betteridge" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, July 12, 2001 1:04 AM
> Subject: Re: [JBoss-dev] jboss + jndi + ldap for ejb referencing
>
> > The LDAP provider is defined in the <resource-env-ref-type>
> >
> > The ejb-jar.xml file is :
> >
> > <ejb-jar>
> > <enterprise-beans>
> >
> > <session>
> > <ejb-name>ClientEJB</ejb-name>dmin
> > <home>com.syntactics.server.admin.ejb.ClientHome</home>
> > <remote>com.syntactics.server.admin.ejb.Client</remote>
> > <ejb-class>com.syntactics.server.admin.ejb.ClientEJB</ejb-class>
> > <session-type>Stateful</session-type>
> > <transaction-type>Container</transaction-type>
> > <resource-env-ref>
> > <resource-env-ref-name>
> > ClientEJB
> > </resource-env-ref-name>
> > <resource-env-ref-type>
> > com.sun.jndi.ldap.LdapCtxFactory
> > </resource-env-ref-type>
> > </resource-env-ref>
> > </session>
> >
> > </enterprise-beans>
> > </ejb-jar>
> >
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
