avalon-apps-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <Paul_Hamm...@yahoo.com>
Subject Re: MX4j components (2)
Date Thu, 01 Aug 2002 22:51:54 GMT
Peter,

> thanks for the tips it is working now except that I can't connect via 
> the HTTPAdapter on the configured port 8082 for some reason.

Try getting a fresh copy of Phoenix from CVS.  We did this today at work 
and it works flawlessly.

> But another question, This way the MBeanServer is part of the kernel 
> and also configured in kernel.xml and not available as a block for 
> other components. Not let's say I want to create other components that 
> want to publish MBeans via this MBeanServer how would I use it?

Good question.  Ideas Huw?

> Wouldn't it be possible to realize the MX4J server as a standard block 
> in "user-space"? One could also realize the adapters as their own 
> components so that one could chose whether to use a HTTP, RMI or other 
> adapter just in the assembly.xml. 

Yup.  We have modelled the concept of supervisor-mode blocks before.... 
but it is a difficult concept.

- Paul


--
To unsubscribe, e-mail:   <mailto:avalon-apps-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-apps-dev-help@jakarta.apache.org>


Mime
View raw message