Post the answer as request.
I understand the technical reason, but for an user point of view
is weird configure a parameter in 2 files, my surprise was because
il starts a Mlet that I've removed from jboss.conf.
And the second is started for a small period with the new
configuration, then it get the old one.
What about a trivial time base check of confgiuration files before
save and then use the data included in jboss-auto?
Of course with a warning.
I think that the users will be confused for it.
Bye
Fulco
On Thu, Apr 05, 2001 at 09:42:50AM -0400, Vladimir Blagojevic wrote:
> Fulco,
>
> Can't post to jboss-dev at the moment, so please repost to jboss-dev.
>
> This was documented already at:
> http://www.jboss.org/documentation/HTML/ch02s02.html
>
> and you can see why it is happening here:
>
> http://www.mail-archive.com/[email protected]/msg00202.html
>
> There are some other difficulties with saving runtime instance that I have
> noticed which are somewhat serious.
>
> For example:
>
> If you make an MBean that has a nonprimitive (and String object) as an
> attribute it craps out on save because current setup does esentially
> object.toString() to save attributes into xml content and not
> serialization. This does not currently happen since all MBean have
> noncomplex objects as attributes. But we'll run into problems when people
> try to write their own custom MBeans that happen to have these attributes.
>
>
> So when jboss-auto.jcml is applied it barfs NPE since it can not
> handle these situations, leaving loaded MBean in essentially invalid
> object state.
>
> Actually I was just about to contact Rickard about this, since he is the
> most familliar with this code, for possbile solutions and maybe some
> changes to this autosave mechanism (maybe it shouldn't be so automatic but
> rather invoked from admin console, + have to take care of serializing
> attributes)
>
>
> Cheers,
> Vladimir
>
> On Thu, 5 Apr 2001, Fulco Muriglio wrote:
>
> > I've executed run.sh without change configuration, then I've stopped
> > jboss.
> > I've removed 'ConsoleLogging' in jboss.conf and changed the
> > pattern in FileLogging.
> > Then I've started and jboss starts, but the output file
> > was half with the new pattern and half with the old one.
> > Jboss logs also to console.
> > To start jboss as desired I've changed both jboss.cong and jboss-auto.jcml.
> >
> > This is a unusual configuration style and should be documented.
> >
> > Anyway the output without console logging is:
> >
> > --------
> >
>CLASSPATH=/opt/local/classes/log4j.jar:/opt/local/classes/classes12.zip:.:run.jar:../lib/crimson.jar
> > jboss.home = /home/fulco/sw/2.2test/jBoss-2.2
> > Using configuration "test1"
> > JAAS.startService, cachePolicy=null
> > JAAS.startService,
>SecurityProxyFactory=org.jboss.security.SubjectSecurityProxyFactory@3e0f0a
> > Server 1.4 is running
> > Press [Ctrl]+[C] to abort
> > Enhydra InstantDB - Version 3.21
> > The Initial Developer of the Original Code is Lutris Technologies Inc.
> > Portions created by Lutris are Copyright (C) 1997-2000 Lutris Technologies,
>Inc.All Rights Reserved.
> > --------
> >
> > Is it ok?
> >
> >
> > Bye
> > Fulco
> >
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
