> > >This is already the case, Jason. Invokers are configured as an MBean. >standardjboss.xml binds the ProxyFactory to the container. Implicitly, a >default invoker is bound to the container. You can bind your own invoker to >the container by specifying <home-invoker> or <bean-invoker> with an MBean >name in jboss.xml. >
Just for my own clarity, these can be specified with out having to put in the entire container config? It was my impression that you need to specify the entire container config... though I don't know if that has changed in 3.x. >In the future we'll need to expand things so that you can bind multiple >invokers to the same container via standardjboss.xml and jboss.xml. > Do we really want to have people changing standardjboss.xml? Seems like it would be better to have a user flip a switch somewhere in jboss-service.xml (or some other deployed xml) rather than need to touch this file... but that is just my preference. I try to keep users from mucking with standard configurations, as they just tend to break things... or when upgrading there is more work for them to make sure there hacked configs make it over to the new files. Any ways, just a thought... =) --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
