Jason, you are behind the curve here. Again the MLet solution was already superior |Perhaps XML would be a better idea, so we can pass in arguments to the |mbeans. Currently the Log4jService can only read a log.properties file, |where it was configurable before. log4j should be configured as a full xml mbean in the configuration files. It should not be configured through the MLet stuff. The logging situation is in flux right now. |Do we have the resources durring this phase to make use of the xml <mbean> |stuff? no, these calls set it up (if you read closely :) marcf | |--jason | | |On Fri, 7 Sep 2001, Jason Dillon wrote: | |> In Main currently we hardcode serveral MBean creations. Why not read a |> autoload.properties (or whatever) from run.jar, which lists the sequence, |> then simply iterate over it and startup components: |> |> component.0=org.jboss.logging.Logger |> component.1=org.jboss.logging.Log4jService |> component.2=org.jboss.system.Info |> component.3=org.jboss.system.Shutdown |> component.4=org.jboss.system.ServiceController |> component.5=org.jboss.deployment.ServiceDeployer |> |> This could be XML too, but properties will work just as well. |> |> --jason |> |> | | |_______________________________________________ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
