On Tuesday, January 28, 2003, at 12:45 AM, David Jencks wrote:
On Tuesday, January 28, 2003, at 12:47 AM, Dain Sundstrom wrote:
On Monday, January 27, 2003, at 09:36 PM, David Jencks wrote:
On Monday, January 27, 2003, at 07:39 PM, Dain Sundstrom wrote:
Wow, I had no idea it was this compli
On Tuesday, January 28, 2003, at 12:47 AM, Dain Sundstrom wrote:
On Monday, January 27, 2003, at 09:36 PM, David Jencks wrote:
On Monday, January 27, 2003, at 07:39 PM, Dain Sundstrom wrote:
Wow, I had no idea it was this complicated. Anyway the real problem
is a Dynamic MBean has a setAttr
On Monday, January 27, 2003, at 09:36 PM, David Jencks wrote:
On Monday, January 27, 2003, at 07:39 PM, Dain Sundstrom wrote:
Wow, I had no idea it was this complicated. Anyway the real problem
is a Dynamic MBean has a setAttributes method to group together an
entire set of attribute changes
On Monday, January 27, 2003, at 07:39 PM, Dain Sundstrom wrote:
Wow, I had no idea it was this complicated. Anyway the real problem is
a Dynamic MBean has a setAttributes method to group together an entire
set of attribute changes in one operator, but when we go to standard
mbeans we lose tha
Wow, I had no idea it was this complicated. Anyway the real problem is
a Dynamic MBean has a setAttributes method to group together an entire
set of attribute changes in one operator, but when we go to standard
mbeans we lose that concept because we only have a bunch of setters.
That sucks.
W
ssage-
From: David Jencks [mailto:[EMAIL PROTECTED]]
Sent: Fri 1/24/2003 9:00 PM
To: [EMAIL PROTECTED]
Cc:
Subject: Re: FW: [JBoss-dev] [ jboss-Change Notes-672538 ] Master
Configuration Service
Yes, that's the idea. It goes
> Yes, that's the idea. It goes like this when jboss instantiates an
> mbean from a *-service.xml file:
>
> (create mbean)
> state: instantiated
> (set attributes)
> state: configured
> (call create method) ~(call destroy method)
> state: created
> (call start method) ~(call stop method)
> state:
Yes, that's the idea. It goes like this when jboss instantiates an
mbean from a *-service.xml file:
(create mbean)
state: instantiated
(set attributes)
state: configured
(call create method) ~(call destroy method)
state: created
(call start method) ~(call stop method)
state: started
where the
David,
We are miscommunicating.
>In all the mbeans I have written and seen in jboss, aside from
>egregious bugs, if setting an attribute doesn't have an immediate
>effect, it does have the desired effect if you run through the service
>lifecyc
On Friday, January 24, 2003, at 03:23 PM, Matt Munz wrote:
this one didn't make it either...
-Original Message-
From: Matt Munz
Sent: Fri 1/24/2003 12:18 PM
To: [EMAIL PROTECTED]
Cc:
Subject: RE: [JBoss-dev] [ jboss-Change Notes-672538 ] Master
Configuration Service
David,
While I'm sure what you are proposing can be made to work, it would be
a really big redesign of how mbeans are thought of in jboss. Something
you can do today, in just a few minutes, and will make your proposal
work with jboss as it is currently written is to use the service
lifecycle methods
this one didn't make it either...
-Original Message-
From: Matt Munz
Sent: Fri 1/24/2003 12:18 PM
To: [EMAIL PROTECTED]
Cc:
Subject: RE: [JBoss-dev] [ jboss-Change Notes-672538 ] Master Configuration
Service
12 matches
Mail list logo
