|Do you have any idea how to find out? I can't find any publicly available
|info. I did notice a very large number of "no" votes on it, all of which
|said "this is too vague and preliminary. Do some more research"
oh no yet another JSR that will end up ripping JBoss and claiming official
status.
On 2002.02.26 15:17:00 -0500 marc fleury wrote:
> |This is unclear though, are you saying "what should the service
> controller
> |do on a change?"
> |if that is the question then the values should be
> |
> |state-action-on-update {KEEP-RUNNING| RE-START | RE-INSTANCIATE}
>
> hey supposedly JSR
The model mbean descriptors can include information per-attribute about
what level of service shutdown is necessary. No need to bother the service
itself. See some later messages.
david jencks
On 2002.02.26 18:40:24 -0500 Jason Dillon wrote:
> Again, why not use a notification here? If an att
>
To: "marc fleury" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, February 26, 2002 3:40 PM
Subject: Re: [JBoss-dev] notes on configuration
> Again, why not use a notification here? If an attrib is exposed, then
> we have to poll. If the service s
Again, why not use a notification here? If an attrib is exposed, then
we have to poll. If the service sends a note, then we just sit until we
get one...
Or am I missing the point?
--jason
marc fleury wrote:
>|If we used ModelMBeans, the Attribute's desriptor
>|could include a field "runti
|This is unclear though, are you saying "what should the service controller
|do on a change?"
|if that is the question then the values should be
|
|state-action-on-update {KEEP-RUNNING| RE-START | RE-INSTANCIATE}
hey supposedly JSR 111 deals with this? does it? the HP guys have been
talking abou
David,
bringing you to the training was the best thing ever,
since then you have become quite the man ...
|Right now I'm working on xdoclet tags >> xmbean xml (I want to get this in
|xdoclet 1.1.2, this weekend) and xmbean modifications to go with improved
|xmbean dtd. Then we can start conve
On 2002.02.26 13:38:37 -0500 marc fleury wrote:
> 3 of 4 imho
>
> |Yes. Also there is the choice of
> |-change attribute value while mbean is "started"
>
> yes
>
> |-stop, change attribute value, start
>
> yes
>
> |-stop, destroy, create(with new values), start
>
> no (use below)
I agree,
3 of 4 imho
|Yes. Also there is the choice of
|-change attribute value while mbean is "started"
yes
|-stop, change attribute value, start
yes
|-stop, destroy, create(with new values), start
no (use below)
|-stop, destroy, remove, install, create(with new valuew), start
yes
|These could a
|If we used ModelMBeans, the Attribute's desriptor
|could include a field "runtimeConfigurable".
|The service deployer can then determine if a redeploy
|is required.
ohhh so pretty
we will use modelMBeans very soon, if we could get you get to put something
out
marcf
__
On 2002.02.26 08:57:05 -0500 Adrian Brock wrote:
> If we used ModelMBeans, the Attribute's desriptor
> could include a field "runtimeConfigurable".
> The service deployer can then determine if a redeploy
> is required.
>
> Regards,
> Adrian
Yes. Also there is the choice of
-change attribute val
If we used ModelMBeans, the Attribute's desriptor
could include a field "runtimeConfigurable".
The service deployer can then determine if a redeploy
is required.
Regards,
Adrian
> |Why not make more usage of notifications here. Such
> that jetty could
> |send a notificatioin when it needs to be
|Why not make more usage of notifications here. Such that jetty could
|send a notificatioin when it needs to be redeployed due to config
|change. It may know best for some/most config changes.
correct, jetty knows best what requires a restart and what does not, all
this handling should be done
>|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
>|Dillon
>|Sent: Tuesday, February 26, 2002 12:41 AM
>|To: marc fleury
>|Cc: Jboss-Development@Lists. Sourceforge. Net
>|Subject: Re: [JBoss-dev] notes on configuration
>|
>|
>|Does this mean that we will always have seperate .xml?
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
|Dillon
|Sent: Tuesday, February 26, 2002 12:41 AM
|To: marc fleury
|Cc: Jboss-Development@Lists. Sourceforge. Net
|Subject: Re: [JBoss-dev] notes on configuration
|
|
|Does this mean that we will
Does this mean that we will always have seperate .xml? Packaged is nice
for classes and file systems, but when the config is inside too, then it
is a pain to configure. Take jetty-plugin.sar. If a user wants to
change ports or add/remove listeners then need to unjar/edit/rejar...
kinda pain
There is a fundamental weakness we carry in our design since 2.0 days
the jboss.jcml/service.xml files
we mix in SAR/jcml
existence of the bean
configuration of the bean
classes for the bean
If we change the configuration of the service we are requiring that we
restart the service. Only changes
17 matches
Mail list logo
