-
1. Re: Service Binding Manager and Log4jService
dimitris Apr 18, 2005 5:38 PM (in response to anguyen)I am not sure if this is related to the order the BindingManager appears in conf/jboss-service.xml, i.e. after Log4jService. Try to put it first.
Another thing you can try is to use a JVM property, e.g.
./run -Dmy.log4j.config=....
and then<mbean code="org.jboss.logging.Log4jService" name="jboss.system:type=Log4jService,service=Logging" xmbean-dd="resource:xmdesc/Log4jService-xmbean.xml"> <attribute name="ConfigurationURL">${my.log4j.config}</attribute> ...
-
2. Re: Service Binding Manager and Log4jService
anguyen Apr 19, 2005 10:19 AM (in response to anguyen)Dimitris, you're a genius!
Changing the order worked, but as I expected, the XSLTFileDelegate didn't work. I'm gonna try my hand at implementing XSLTURLDelegate. Should be very similar to the file delegate.
It's unfortunate that the binding delegates aren't setup well to be extended. They provide no hooks for subclasses to alter small pieces of functionality. It seems a basic abstract delegate should be provided to share functionality as well as offer subclasses a way to handle specific parameter types.
For example, XSLTConfigDelegate allows for arbitrary parameter bindings into the transformation. XSLTFileDelegate only allows parameter bindings for "host" and "port". IMO, that functionality should be refactored into a base class.
If there's interest, I would be willing to do the refactoring and submit the code. -
3. Re: Service Binding Manager and Log4jService
dimitris Apr 19, 2005 10:54 AM (in response to anguyen)If you can refactor it to make it more extensible, without breaking the existing bindings, that would be great.
Register that in JIRA as a feature request and submit the patch there.
Thanks!