[Design of POJO Server] - Re: migrating TransactionManager and Invokers to POJO
by bstansberry@jboss.com
That doesn't work, at least not trivially, as the remoting connector as configured actually needs the unified invoker since it's specified as a handler:
| 2008-03-29 17:16:16,815 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=jboss.remoting:service=Connector,transport=socket state=Create mode=Manual requiredState=Installed
| java.lang.reflect.UndeclaredThrowableException
| at $Proxy45.setMBeanServer(Unknown Source)
| at org.jboss.remoting.transport.Connector.addInvocationHandler(Connector.java:1192)
| at org.jboss.remoting.transport.Connector.configureHandlersFromXML(Connector.java:848)
| at org.jboss.remoting.transport.Connector.start(Connector.java:317)
| ....
| Caused by: javax.management.InstanceNotFoundException: jboss:service=invoker,type=unified is not registered.
| at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529)
| at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:608)
| at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:193)
| ... 54 more
|
I recall in some unit test or other I actually injected another handler after the fact, although IIRC getting it to work was a hack. Perhaps it wasn't; I'll see if I can find it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139881#4139881
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139881
16 years, 1 month
[Design of POJO Server] - Re: migrating TransactionManager and Invokers to POJO
by bstansberry@jboss.com
We don't need a separate file due to the cluster defaults deployer; having two different files in the tomcat module is a bit of legacy cruft. A file with the clustering deployers in it should work just fine in default.
That said, I'd like the clustering deployer out of the file too. IIRC it mostly isn't because I somewhat wanted the deployer in jbossweb.deployer/META-INF folder and if I put a second -beans.xml there it wouldn't get deployed.
Re: the various test-config stuff, yes, there has to be a cleverer way. The biggest case of using a test-config to override instead of add is to change server.xml. A couple do that to inject sso valves; that can probably be done with a separate mbean instead. Not particularly "clever", but will work. Don't know if that kind of thing can be done with some of the others, which try to override stuff like connectors and the security realm, which may not be changeable after the web server starts.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139878#4139878
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139878
16 years, 1 month