Re: [JBoss-user] Newbie JNDI Question
One thing you might want to do is turn logging up a little bit in log4j.properties and see if something is actually going south quietly. Mike Kenyon wrote: I just downloaded JBoss v.2.4.4 as part of an internal effort to migrate one of our test servers from another app server to JBoss. We're using iPlanet as a web server with JSPs connecting back to the EJBs running on JBoss. Are the JSPs running under JBoss/(Jetty|Tomcat), or are they running in iPlanet App. Server? If the JSPs are running in iPlanet, they're probably trying to do a lookup in IAS's JNDI, whereas the EJBs will be bound in JBoss' JNDI. Using Sun's JNDI browser, I can't locate anything that resembles an EJB (seeing only two entries, UserTransaction and UserTransactionSessionFactory). Which JNDI server was this pointed at? Further, I tried to examine it through JNDIView (which claims to start successfullly), however, nothing is bound to http://localhost:8082, as the documentation indicates there should be. You mean there's no http server listening at 'http://localhost:8082'? If so then something is going wronger with the startup. -danch ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Newbie JNDI Question
I just downloaded JBoss v.2.4.4 as part of an internal effort to migrate one of our test servers from another app server to JBoss. We're using iPlanet as a web server with JSPs connecting back to the EJBs running on JBoss. I'm experiencing inordinant difficulty trying to get the EJBs deployed successfully. I get no warnings or errors of any kind as JBoss is booting up and everything appears find and dandy. However, all attempts to look up EJBs by their jndi-name / have failed horribly with a name not bound exception. Using Sun's JNDI browser, I can't locate anything that resembles an EJB (seeing only two entries, UserTransaction and UserTransactionSessionFactory). Further, I tried to examine it through JNDIView (which claims to start successfullly), however, nothing is bound to http://localhost:8082, as the documentation indicates there should be. Anyone have an idea what stupid thing I'm doing wrong? Mike ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Newbie JNDI Question
I remember way back originally reading in the documentation that there was a difference in jboss in the way ejbs were looked up on the server versus a client. On the server, you had to use java:comp/env/ejbname whereas on the client it was simply ejbname. At the time, I remember thinking this was at odds with every example I had seen (normally there is no differentiation between naming on the client and the server. My fear is that we'll have to port to a server other than jboss and I'll have the opposite problem from you. What worked on jboss won't work on other servers. All my client code (luckily its all in one place) that tries to find ejbs without the comp/env will fail... Can someone please confirm or deny this difference? Thanks Eric -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Kenyon Sent: Wednesday, March 06, 2002 5:22 PM To: '[EMAIL PROTECTED]' Subject: [JBoss-user] Newbie JNDI Question I just downloaded JBoss v.2.4.4 as part of an internal effort to migrate one of our test servers from another app server to JBoss. We're using iPlanet as a web server with JSPs connecting back to the EJBs running on JBoss. I'm experiencing inordinant difficulty trying to get the EJBs deployed successfully. I get no warnings or errors of any kind as JBoss is booting up and everything appears find and dandy. However, all attempts to look up EJBs by their jndi-name / have failed horribly with a name not bound exception. Using Sun's JNDI browser, I can't locate anything that resembles an EJB (seeing only two entries, UserTransaction and UserTransactionSessionFactory). Further, I tried to examine it through JNDIView (which claims to start successfullly), however, nothing is bound to http://localhost:8082, as the documentation indicates there should be. Anyone have an idea what stupid thing I'm doing wrong? Mike ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Newbie JNDI Question
This is completely false. The java:comp/env context is local to J2EE components and can be used to isolate code from deployment specific names. The global JNDI can be used as it is on the client in the server. Read about the enterprise naming context and ejb-ref in any standard EJB book for an explanation. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Eric Kaplan [EMAIL PROTECTED] To: Mike Kenyon [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, March 06, 2002 2:57 PM Subject: RE: [JBoss-user] Newbie JNDI Question I remember way back originally reading in the documentation that there was a difference in jboss in the way ejbs were looked up on the server versus a client. On the server, you had to use java:comp/env/ejbname whereas on the client it was simply ejbname. At the time, I remember thinking this was at odds with every example I had seen (normally there is no differentiation between naming on the client and the server. My fear is that we'll have to port to a server other than jboss and I'll have the opposite problem from you. What worked on jboss won't work on other servers. All my client code (luckily its all in one place) that tries to find ejbs without the comp/env will fail... Can someone please confirm or deny this difference? Thanks Eric ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Newbie JNDI Question
I bound my EJBs with JNDI name: ejb/ejbname, I can look up my ejbs both from client and server side with the same JNDI name without problem. And I tested my application on IBM WebSphere, JBoss and J2EE server. Eric Kaplan wrote: I remember way back originally reading in the documentation that there was a difference in jboss in the way ejbs were looked up on the server versus a client. On the server, you had to use java:comp/env/ejbname whereas on the client it was simply ejbname. At the time, I remember thinking this was at odds with every example I had seen (normally there is no differentiation between naming on the client and the server. My fear is that we'll have to port to a server other than jboss and I'll have the opposite problem from you. What worked on jboss won't work on other servers. All my client code (luckily its all in one place) that tries to find ejbs without the comp/env will fail... Can someone please confirm or deny this difference? Thanks Eric -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Kenyon Sent: Wednesday, March 06, 2002 5:22 PM To: '[EMAIL PROTECTED]' Subject: [JBoss-user] Newbie JNDI Question I just downloaded JBoss v.2.4.4 as part of an internal effort to migrate one of our test servers from another app server to JBoss. We're using iPlanet as a web server with JSPs connecting back to the EJBs running on JBoss. I'm experiencing inordinant difficulty trying to get the EJBs deployed successfully. I get no warnings or errors of any kind as JBoss is booting up and everything appears find and dandy. However, all attempts to look up EJBs by their jndi-name / have failed horribly with a name not bound exception. Using Sun's JNDI browser, I can't locate anything that resembles an EJB (seeing only two entries, UserTransaction and UserTransactionSessionFactory). Further, I tried to examine it through JNDIView (which claims to start successfullly), however, nothing is bound to http://localhost:8082, as the documentation indicates there should be. Anyone have an idea what stupid thing I'm doing wrong? Mike ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user -- Jia (Christine) Li 524N ICT Building Department of Computer Science University of Calgary ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Newbie JNDI Question
I agree with Scott. I have tried both local and global JNDI from the server and both work. By the way I have worked with only the 3.0beta version and so cannot confirm the same for the earlier ones. I had one question for Scott though...When u say local to J2EE components, do you mean local to J2ee applications deployed on the server? -Vishwas. Scott M Stark wrote: This is completely false. The java:comp/env context is local to J2EE components and can be used to isolate code from deployment specific names. The global JNDI can be used as it is on the client in the server. Read about the enterprise naming context and ejb-ref in any standard EJB book for an explanation. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Eric Kaplan [EMAIL PROTECTED] To: Mike Kenyon [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, March 06, 2002 2:57 PM Subject: RE: [JBoss-user] Newbie JNDI Question I remember way back originally reading in the documentation that there was a difference in jboss in the way ejbs were looked up on the server versus a client. On the server, you had to use java:comp/env/ejbname whereas on the client it was simply ejbname. At the time, I remember thinking this was at odds with every example I had seen (normally there is no differentiation between naming on the client and the server. My fear is that we'll have to port to a server other than jboss and I'll have the opposite problem from you. What worked on jboss won't work on other servers. All my client code (luckily its all in one place) that tries to find ejbs without the comp/env will fail... Can someone please confirm or deny this difference? Thanks Eric ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user -- Vishwas Raman Software Engineer, Eternal Systems, Inc, 5290 Overpass Rd, Bldg D, Santa Barbara. CA 93111 Email: [EMAIL PROTECTED] Tel: (805) 696-9051 x246 Fax: (805) 696-9083 URL: http://www.eternal-systems.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Newbie JNDI Question
I had one question for Scott though...When u say local to J2EE components, do you mean local to J2ee applications deployed on the server? By definition the java:comp/env context is only accessible by the component that defined it. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Vishwas Raman [EMAIL PROTECTED] To: Scott M Stark [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, March 06, 2002 4:02 PM Subject: Re: [JBoss-user] Newbie JNDI Question ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
