Someone here pointed out to me that autodeploy worked properly in 2.0, but
is broken in 2.1 in that it says it is refreshing your jar (when you copy a
new verson into the deploy directory), but it still uses the old code.
Hopefully, this will be corrected soon as it is annoying to have to restart
JBoss every time you rebuild your EJB.
----- Original Message -----
From: Tom Davies <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, March 24, 2001 9:06 AM
Subject: [JBoss-user] Minimal JBoss config/Jbuilder debugging...
> Hi,
>
> I'm using JBuilder 4.0 foundation and JBoss, and want to be able to
> debug my bean implementation with JBuilder's debugger.
>
> It works fine, except that I need to restart jboss when I change my
> beans (i.e. autodeploy appears to work, but doesn't perhaps becuase the
bean
> classes are on the jboss classpath?).
>
> Restarting takes about 60 seconds under the debugger (6-7 seconds
> without) on a Celeron 700. I've hacked as many things as I can out of the
> jboss conf/jcml files. Does someone have the definitive minimal jboss
> config, given that I don't want to use any fancy features, just one
> XADataSource?
>
> Thanks,
> Tom
> --
> [EMAIL PROTECTED] http://members.optushome.com.au/tomdavies
>
>
> _______________________________________________
> 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
