RE: [JBoss-user] Cannot connect to an external RMI Server

2002-08-02 Thread Graham French
ubject: RE: [JBoss-user] Cannot connect to an external RMI Server If you're on windows, set your temp env variable to something without spaces in the filename, worked for me!   rick -Original Message-----From: Graham French [mailto:[EMAIL PROTECTED]] Sent: Friday

[JBoss-user] Cannot connect to an external RMI Server

2002-06-21 Thread Graham French
Title: Cannot connect to an external RMI Server Hi all Still on my quest to get our application deployed in JBoss and have come across another problem Have an EAR which contains several EJBs and a WAR. >From the webapp the client can execute a call to an in-house RMI Server (in this ca

RE: [JBoss-user] Multiple EARs / Classloading / Singletons

2002-06-21 Thread Graham French
both apps).  If you try this out you will want to load only one copy of each class, so one app will be "configuration only" david jencks On 2002.06.21 07:10:46 -0400 Graham French wrote: > Hi, > I'm relatively new to Jboss 3 so I may have missed something here.

[JBoss-user] Multiple EARs / Classloading / Singletons

2002-06-21 Thread Graham French
Title: Multiple EARs / Classloading / Singletons Hi, I'm relatively new to Jboss 3 so I may have missed something here. I have two EARs deployed in the same instance of JBoss3.0.0. The code libraries/EJB's are identical, the EJB's are identified by different JNDI namespaces. Inside each

RE: [JBoss-user] JBoss 2.4.4 NameAlreadyBoundException

2002-05-23 Thread Graham French
Message - From: "Graham French" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 10:28 AM Subject: [JBoss-user] JBoss 2.4.4 NameAlreadyBoundException > Hi, > > I have an jar that contains two ejbs: one stateless session > (AuthenticationMan

[JBoss-user] JBoss 2.4.4 NameAlreadyBoundException

2002-05-22 Thread Graham French
Hi, I have an jar that contains two ejbs: one stateless session (AuthenticationManager) and one BMP entity (ToolUser) When I deploy it under JBoss 2.4.4, I get the stack trace below. If I comment out one of the ejbs in the deployment descriptors, it deploys fine. When I put back just the minimal