SV: SV: [JBoss-user] Multiple deployment problem

2001-03-27 Thread Lennart Petersson
cally downloaded from the server then there may be some problem if i'm not restarting the client. Will test it! /Lennart - Original Message - From: danch <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 27, 2001 4:38 PM Subject: Re: SV: [JBoss-user] Mul

Re: [JBoss-user] Multiple deployment problem

2001-03-27 Thread Guy Rouillier
(plus anything else I need) and it runs fine. - Original Message - From: "Lennart Petersson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 27, 2001 5:40 AM Subject: SV: [JBoss-user] Multiple deployment problem Hi! - Original Message - F

Re: [JBoss-user] Multiple deployment problem

2001-03-27 Thread Tim Taylor
I ran into this too... The code for the deployer (org.jboss.deployment.J2eeDeployer) uses a new URLClassLoader per deployment. The problem is that the URLClassLoader loads classes from its parent classloader _before_ looking in archive (.jar, .war, or .ear) pointed to by its URL. If the bea

RE: SV: [JBoss-user] Multiple deployment problem

2001-03-27 Thread Swami Iyer
Message- From: danch [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 27, 2001 9:38 AM To: [EMAIL PROTECTED] Subject: Re: SV: [JBoss-user] Multiple deployment problem Lennart Petersson wrote: > Hi! Yes i've read numerous messages over the last couple of days about the non-fun

Re: SV: [JBoss-user] Multiple deployment problem

2001-03-27 Thread danch
Lennart Petersson wrote: > Hi! Yes i've read numerous messages over the last couple of days about the >non-functioning autodeploy. And i can't still understand what the problem is... I'VE >NO PROBLEM WITH IT!!! Did a new test right now, with todays CVS. First i changed the >behaviour of a remo

SV: [JBoss-user] Multiple deployment problem

2001-03-27 Thread Lennart Petersson
Hi! - Original Message - From: Daniel Sadilek <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 27, 2001 11:39 AM Subject: Re: [JBoss-user] Multiple deployment problem > Hello, > > :) I got it working. > The problem was that my development-dire

Re: [JBoss-user] Multiple deployment problem

2001-03-27 Thread Daniel Sadilek
Hello, :) I got it working. The problem was that my development-directory was in the jboss-classpath. Since taking this directory out of the classpath, auto-deployment works very well. However, this is mysterious to me because in the development-directory are the same class-files as are in the de

SV: [JBoss-user] Multiple deployment problem

2001-03-26 Thread Lennart Petersson
lt;[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 27, 2001 5:30 AM Subject: Re: [JBoss-user] Multiple deployment problem > Please read numerous messages here over the last couple days. Autodeploy > has problems in 2.1 - it is not picking up new versions. The only r

Re: [JBoss-user] Multiple deployment problem

2001-03-26 Thread Guy Rouillier
t;[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 26, 2001 3:43 AM Subject: [JBoss-user] Multiple deployment problem > Hello, > > when I try to redeploy a jar-packaged bean the deployment seems to work > correctly. But when I access the bean the container seems to

Re: [JBoss-user] Multiple deployment problem

2001-03-26 Thread Daniel Sadilek
g very simplistic here, but it's from own (sad) experience > (manchmal hat man einfach nicht genug Hintern, in die man sich beissen > moecht!). > > Regards, > Gregor > > > -Original Message- > > From: Daniel Sadilek [mailto:[EMAIL PROTECTED]] > > Sent

RE: [JBoss-user] Multiple deployment problem

2001-03-26 Thread gregor . giebel
l hat man einfach nicht genug Hintern, in die man sich beissen moecht!). Regards, Gregor > -Original Message- > From: Daniel Sadilek [mailto:[EMAIL PROTECTED]] > Sent: 26 March 2001 10:44 > To: [EMAIL PROTECTED] > Subject: [JBoss-user] Multiple deployment problem > > &

[JBoss-user] Multiple deployment problem

2001-03-26 Thread Daniel Sadilek
Hello, when I try to redeploy a jar-packaged bean the deployment seems to work correctly. But when I access the bean the container seems to execute the old version. That even happens if I first delete the jar-packaged bean from the deploy-directory and then copy the new version into it. This prob