Re: [JBoss-user] Unable to resolve JNDI name
Thanks everybody for helping me out.. jboss.xml and ejb-jar.xml were correct. The reason for the error was that the jboss.xml was not being read at all as it is case sensitive and I had put the file name as JBOSS.xml. It has to be in lower case only(even on NT platform) and only then is it read during deployment time. Is it a bug? Shouldn't jBoss report that it could not find jboss.xml during deployment? Thanks Again. regards Manu __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Unable to resolve JNDI name
Is it a bug? Shouldn't jBoss report that it could not find jboss.xml during deployment? No, if no jboss.xml found, it uses the standardjboss.xml in the configuration dir. Same applies to the jaws.xml (it uses standardjaws.xml instead). Only ejb-jar.xml is required. Roman ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Unable to resolve JNDI name
FWIW, I see a lot of ppl who use the classname as the lookup. jim - Original Message - From: Guy Rouillier [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 11, 2001 1:10 PM Subject: Re: [JBoss-user] Unable to resolve JNDI name My apologies for my previous post, which I wrote in a hurry. You should of course do a lookup on the jndi name, which gets mapped to the ejb-name (via jboss.xml). My second point still holds, however - using the home class name as your jndi name is confusing. - Original Message - From: Guy Rouillier [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 10, 2001 7:49 PM Subject: Re: [JBoss-user] Unable to resolve JNDI name You are supposed to do a lookup on the remote interface. You will be returned a reference to a home object, from which you can call the create() method to get an object of the target class. So I think the failure you indicate is appropriate. In your jboss.xml, why are you using your home classname as your jndi name? This is confusing, to say the least. jBoss.xml = jboss session ejb-namecom.asset.SMTPAdapter/ejb-name jndi-namecom.asset.SMTPAdapterHome/jndi-name configuration-name/configuration-name /session /enterprise-beans /jboss Code snippet in my jsp == Context ctx = getInitialContext(); Object home = ctx.lookup(com.asset.SMTPAdapter);//WORKS! Object home = ctx.lookup(com.asset.SMTPAdapterHome);//DOES NOT WORK!!! ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Unable to resolve JNDI name
Manu Srivastava wrote: Hi, jBoss.xml = jboss enterprise-beans !-- you seem to be missing this tag -- session ejb-namecom.asset.SMTPAdapter/ejb-name jndi-namecom.asset.SMTPAdapterHome/jndi-name configuration-name/configuration-name /session /enterprise-beans /jboss Also if use keep the file name of jboss.xml in small letters the deployment fails. If you rename it to all caps or jBoss.xml it starts deploying. If you mosted your jboss.xml completely, this is because of the syntax problem I point out above. When it's spelled in lower case, JBoss tries to read it and deployment fails because it isn't well-formed XML. -danch ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Unable to resolve JNDI name
You are supposed to do a lookup on the remote interface. You will be returned a reference to a home object, from which you can call the create() method to get an object of the target class. So I think the failure you indicate is appropriate. In your jboss.xml, why are you using your home classname as your jndi name? This is confusing, to say the least. jBoss.xml = jboss session ejb-namecom.asset.SMTPAdapter/ejb-name jndi-namecom.asset.SMTPAdapterHome/jndi-name configuration-name/configuration-name /session /enterprise-beans /jboss Code snippet in my jsp == Context ctx = getInitialContext(); Object home = ctx.lookup(com.asset.SMTPAdapter);//WORKS! Object home = ctx.lookup(com.asset.SMTPAdapterHome);//DOES NOT WORK!!! ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Unable to resolve JNDI name
Hi Danch, Thanks for the answer. Problem in copy and paste :-( enterprise-beans tag is there in the jBoss.xml but it still it does not get the correct JNDI name. It deploys correctly though. Any other clues?? Thanks and regards Manu Manu Srivastava wrote: Hi, jBoss.xml = jboss enterprise-beans !-- you seem to be missing this tag -- session ejb-namecom.asset.SMTPAdapter/ejb-name jndi-namecom.asset.SMTPAdapterHome/jndi-name configuration-name/configuration-name /session /enterprise-beans /jboss Also if use keep the file name of jboss.xml in small letters the deployment fails. If you rename it to all caps or jBoss.xml it starts deploying. If you mosted your jboss.xml completely, this is because of the syntax problem I point out above. When it's spelled in lower case, JBoss tries to read it and deployment fails because it isn't well-formed XML. -danch __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Unable to resolve JNDI name
My apologies for my previous post, which I wrote in a hurry. You should of course do a lookup on the jndi name, which gets mapped to the ejb-name (via jboss.xml). My second point still holds, however - using the home class name as your jndi name is confusing. - Original Message - From: Guy Rouillier [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 10, 2001 7:49 PM Subject: Re: [JBoss-user] Unable to resolve JNDI name You are supposed to do a lookup on the remote interface. You will be returned a reference to a home object, from which you can call the create() method to get an object of the target class. So I think the failure you indicate is appropriate. In your jboss.xml, why are you using your home classname as your jndi name? This is confusing, to say the least. jBoss.xml = jboss session ejb-namecom.asset.SMTPAdapter/ejb-name jndi-namecom.asset.SMTPAdapterHome/jndi-name configuration-name/configuration-name /session /enterprise-beans /jboss Code snippet in my jsp == Context ctx = getInitialContext(); Object home = ctx.lookup(com.asset.SMTPAdapter);//WORKS! Object home = ctx.lookup(com.asset.SMTPAdapterHome);//DOES NOT WORK!!! ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
