On Tue, 3 Oct 2000, Francisco Andrades wrote:
> Another issue (because i don�t know if it�s a feature)
> is that when deploying the beans there can�t be any
> jboss.xml and ejb-jar.xml files in a directory named
> META-INF in the classpath, because jboss will use them
> more likely than the ones inside the bean�s jar (which
> in most cases messes up all the beans and forces you
> to start over).
In general, you should have as little as possible in your
CLASSPATH. The default startup scripts can be used with no CLASSPATH at
all. Can you take the directory with the META-INF files off your
classpath?
> There�s also the problem with the conf\jboss.jcml
> file. I have solved it modifying the run.bat script to
> regenerate it every time jboss starts.
Are you working from a current CVS build or the last binary? We
have a potential fix in CVS, but it was not in the binary. If worst comes
to worst, we should probably disable the configuration file overwriting
for the "production" version - or at least, default to not doing it.
Aaron
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
