Dain,
Please see my recent email in response to Bill.
I origionally started with this approach, but the more I thought about it, the more
untenable it seemed. Based on my experience so far, I just don't want the server
mucking with my deployment descriptors.
I'm sure I can figure out the autodeployer ;) But look what you're saying.
"Implement Persistence, modify deployer". Do you see how the two concerns are being
tightly bound by this approach?
We don't need AOP to solve this one ;) -- just locate the persistence in a separate
place (this is what it "wants" to do anyway, IMO -- consider standalone applications.
I've never seen an application open up its jars and stuff info into them. They always
use a separate DB).
BTW, I want to relocate this discussion to the Forums, as Bill suggests, but which
one? I see at least 3 JMX-related forums!
- Matt
-----Original Message-----
From: Dain Sundstrom [mailto:[EMAIL PROTECTED]]
Sent: Mon 1/13/2003 11:38 AM
To: [EMAIL PROTECTED]
Cc:
Subject: Re: [JBoss-dev] MBean persistence?
Yes basically.
Here is what I have in mind: as each attribute is loaded from the
source xml the location from where it was loaded is remembered. When
an attribute is changed that was loaded from the xml, the persistence
manager overwrites the existing XML. I don't think you have to explode
the jar, but I do think you basically have to rewrite the entire file.
I think the trick will be to convince the auto deployer to not redeploy
the modified file (if you can't figure that out it is ok... I get David
J to get it to work :-)
Does this sound do-able?
-dain
On Monday, January 13, 2003, at 09:54 AM, Bill Burke wrote:
> Matt,
>
> I think we want seemless integration here. If the MBean is packaged
> within a SAR, the SAR should be exploded, the XML file modified and
> the SAR re-jared. Same goes with straight XML files or SARS embedded
> within SARs (russian doll).
>
> I'm in the process of creating task lists at SourceForge for each
> project. I can assign you this task?
>
> Thanks for your effort,
>
>
> XXXXXXXXXXXXXXXX
> Bill Burke
> Chief Architect
> JBoss Group, LLC
> XXXXXXXXXXXXXXXX
>
> -----Original Message-----
> From: Matt Munz
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Matt Munz
> Sent: Monday, January 13, 2003 10:48 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] MBean persistence?
>
> Dain,
>
> > So Matt are you interested in working on the XML persistence?
>
> Yeah, I suppose I could put some more time into it. It sounds like
> you know a few people that might actually be users of this feature.
> Do you have a use case in mind?
>
> - Matt
>
> -----Original Message-----
> From: Dain Sundstrom [mailto:[EMAIL PROTECTED]]
> Sent: Mon 1/13/2003 10:07 AM
> To: [EMAIL PROTECTED]
> Cc:
> Subject: Re: [JBoss-dev] MBean persistence?
>
> So Matt are you interested in working on the XML persistence?
>
> -dain
>
> On Monday, January 13, 2003, at 08:32 AM, Matt Munz wrote:
>
> > Dain,
> >
> >> What is going on with MBean persistence?
> >
> > Not much, as far as I can tell.
> >
> >> Can we do this today?
> >
> > Yes, but only by persisting to ObjectOutputStream files. XML / JDBC
> > persistence engines have yet to be written.
> >
> >> If not is anyone working on it?
> >
> > I origionally wrote the code that I did to scratch an itch. As far
> as
> > I know, nobody else is using it...
> >
> >> When do you expect to have it finished?
> >
> > I reccommend not going to production with ObjectOutputStream
> > persistence as it is fragile.
> >
> > By reusing the code from the ServiceCreator (unmarshalling) and the
> > JMX Console (marshalling), the XML persistence engine should be
> fairly
> > simple to write.
> >
> > - Matt
> >
> > -----Original Message-----
> > From: Dain Sundstrom [mailto:[EMAIL PROTECTED]]
> > Sent: Sat 1/11/2003 1:42 PM
> > To: [EMAIL PROTECTED]
> > Cc:
> > Subject: [JBoss-dev] MBean persistence?
> >
> >
> >
> > What is going on with MBean persistence?
> >
> > I have been at lot of sites lately that are going into
> production with
> > JBoss and the one thing admins always ask for is the ability
> to have
> > changes to the beans in the JMX console to be written back out
> the the
> > XML files. They don't care if the formatting changes or if
> comments
> > are lost, they just want to be able to change and option and
> have it
> > preserved when the server reboots. I love the practicality of
> system
> > administrators.
> >
> > Can we do this today? If not is anyone working on it? When
> do you
> > expect to have it finished?
> >
> > I think this fairly simple feature will make 80% of the admins
> happy.
> >
> > -dain
> >
> >
> >
> > -------------------------------------------------------
> > This SF.NET email is sponsored by:
> > SourceForge Enterprise Edition + IBM + LinuxWorld = Something
> 2 See!
> > http://www.vasoftware.com
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
> > <winmail.dat>
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: FREE SSL Guide from Thawte
> are you planning your Web Server Security? Click here to get a FREE
> Thawte SSL guide and find the answers to all your SSL security issues.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
> <winmail.dat>
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
<<winmail.dat>>
