[Design of POJO Server] - Re: bean/mbean integration issue
by scott.stark@jboss.org
The remoting connector could not simply be ported to a mc bean as it does not support its configuration as a pojo. The workaround I came up with was to introduce an mc bean proxy for the connector mbean using factoryClass attribute and the existing org.jboss.mx.util.MBeanTyper factory type class:
| <bean name="ConnectorMBean">
| <!-- MBeanTyper.typeMBean(MBeanServer, ObjectName, Class iface) -->
| <constructor factoryClass="org.jboss.mx.util.MBeanTyper" factoryMethod="typeMBean">
| <parameter><inject bean="JMXKernel" property="mbeanServer"/></parameter>
| <parameter>jboss.remoting:service=Connector,transport=socket</parameter>
| <parameter>org.jboss.remoting.transport.ConnectorMBean</parameter>
| </constructor>
| </bean>
| <!--
| Add a ProfileService handler to the remoting socket connector
| -->
| <bean name="ProfileServiceInvocationHandler"
| class="org.jboss.aspects.remoting.AOPRemotingInvocationHandler">
| <install bean="ConnectorMBean" method="addInvocationHandler">
| <parameter>ProfileService</parameter>
| <parameter><this/></parameter>
| </install>
| <uninstall bean="ConnectorMBean" method="removeInvocationHandler">
| <parameter>ProfileService</parameter>
| </uninstall>
| </bean>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000198#4000198
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000198
19 years, 3 months
[Design the new POJO MicroContainer] - Retrowoven container project
by kabir.khan@jboss.com
A few of the JDK 1.4 tests in AOP are failing due to java.lang.reflect.ParameterizedType being used by the container project. while not supported in JBoss Retro. I tried adding that to Retro, but it now falls over on things like:
java.lang.reflect.Constructor.getGenericParameterTypes()[Lorg/jboss/lang/reflect/Type;
java.lang.NoSuchMethodError: java.lang.reflect.Constructor.getGenericParameterTypes()[Lorg/jboss/lang/reflect/Type;
at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getConstructors(IntrospectionTypeInfoFactoryImpl.java:143)
at org.jboss.reflect.plugins.ClassInfoImpl.getDeclaredConstructors(ClassInfoImpl.java:400)
at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getConstructors(AbstractBeanInfoFactory.java:177)
at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getBeanInfo(AbstractBeanInfoFactory.java:138)
at org.jboss.config.plugins.AbstractConfiguration.getBeanInfo(AbstractConfiguration.java:75)
at org.jboss.test.beaninfo.test.AbstractBeanInfoTest.getBeanInfo(AbstractBeanInfoTest.java:349)
at org.jboss.test.beaninfo.test.BeanInfoUnitTestCase.testBean(BeanInfoUnitTestCase.java:153)
at org.jboss.test.beaninfo.test.BeanInfoUnitTestCase.testBeanConstructors(BeanInfoUnitTestCase.java:73)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
So support for this needs implementing
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000190#4000190
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000190
19 years, 3 months
[Design of JBoss Portal] - 2.6 alpha release
by julien@jboss.com
I worked today to cleanup tests for the 2.6 release :
- I had to fix the CMS tests that were not able to run because it was relying on the UserModule from JNDI which was not available in the test environment. I fixed it by making the IdentityServiceController injected in the JCRCMS service instead
- commented out the 2 portlet test cases that cannot technically pass
- commented out one theme test that does not seem to exist anymore
- fixed the portal object and instance test cases that were broken due to my refactorings (I had to update the jboss-aop.xml and change the pointcuts, I can't wait to have Java 5 and annotations...)
- I updated the test framework to handle multi node testing (that was disabled after the refactorings done to handle test parameterization).
- I ported the 2.4 slight changes to portlet session replication to trunk.
All tests in the testsuite are passing for me now.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000184#4000184
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000184
19 years, 3 months