[JBoss JIRA] Created: (JBPORTAL-1343) Create an Ant task to execute a TestDriver
by Julien Viet (JIRA)
Create an Ant task to execute a TestDriver
------------------------------------------
Key: JBPORTAL-1343
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1343
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Julien Viet
Fix For: 2.8 Final
An org.jboss.portal.common.test.driver.TestDriver is executed in Ant though the usage of the org.jboss.portal.common.test.junit.JUnitAdapter which adaps the TestDriver protocol to junit.
It has several limitations :
- the way to pass parameters to the test driver is convoluted and basically an hack (that works)
- it is not possible to filter the set of tests returned by the TestDriver easily which force many times to create subclasses in order to execute each test separately
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBMICROCONT-118) Fix the introspection assumption in ClassInfo
by Adrian Brock (JIRA)
Fix the introspection assumption in ClassInfo
---------------------------------------------
Key: JBMICROCONT-118
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-118
Project: JBoss MicroContainer
Issue Type: Task
Components: BeanInfo
Affects Versions: JBossMC_2_0_0 Beta
Reporter: Adrian Brock
Priority: Minor
Fix For: JBossMC_2_0_0_CR1
Although the javassist version of the ClassInfo works fine, there are still some places
in the base ClassInfoImpl that assume introspection (i.e. java.lang.reflect objects).
The javassist impl works around these issues by subclassing.
Additionally, the deprecated ClassInfo.getType() needs removing.
This will require understanding where it is currently used and fixing it
(I think it is mainly related to determining the classloader?)
Moving this method and its dependencies to the ReflectClassInfoImpl
Whether we actually remove the deprecated method is another issue
since it is useful to temporarily fix problems (in future) where we don't provide an equivalent
in the ClassInfo api.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBMICROCONT-130) Array part of the Javassist reflection implementation is broken
by Adrian Brock (JIRA)
Array part of the Javassist reflection implementation is broken
---------------------------------------------------------------
Key: JBMICROCONT-130
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-130
Project: JBoss MicroContainer
Issue Type: Task
Components: BeanInfo
Affects Versions: JBossMC_2_0_0 Beta
Reporter: Adrian Brock
Javassist is returning wrong values for interfaces of arrays and modifiers of array classes.
These errors have been suppressed in org.jboss.test.classinfo.test.JavassistArrayUnitTestCase
by subclassling the tests to do nothing:
protected void assertInterfaces(Class<?> clazz, ClassInfo classInfo) throws Throwable
{
// TODO this is broken for javassist
}
protected void assertModifiers(Class<?> clazz, ClassInfo classInfo) throws Throwable
{
// TODO this is broken for javassist
}
This needs fixing in javassist
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBAS-4963) invocationHasReachedAServer calls within exception handling vary from UnifiedInvokerHAProxy to JRMPInvokerProxyHA
by Galder Zamarreno (JIRA)
invocationHasReachedAServer calls within exception handling vary from UnifiedInvokerHAProxy to JRMPInvokerProxyHA
-----------------------------------------------------------------------------------------------------------------
Key: JBAS-4963
URL: http://jira.jboss.com/jira/browse/JBAS-4963
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta3
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Exception handling is different between JRMPInvokerProxyHA and
UnifiedInvokerHAProxy when it comes to, at least, calls to invocationHasReachedAServer():
1.- JRMPInvokerProxyHA
Exception handling that does not lead to invocationHasReachedAServer() being called:
* java.net.ConnectException
* java.net.UnknownHostException
* java.rmi.ConnectException
* java.rmi.ConnectIOException
* java.rmi.NoSuchObjectException
* java.rmi.UnknownHostException
* GenericClusteringException.NO
Exception handling that leads to invocationHasReachedAServer() being called:
* GenericClusteringException.YES
* java.rmi.ServerException
* java.lang.Exception
2.- UnifiedInvokerHAProxy
Exception handling that does not lead to invocationHasReachedAServer() being called:
* org.jboss.remoting.CannotConnectException
* GenericClusteringException.NO
* java.rmi.RemoteException
* java.lang.Throwable
Exception handling that leads to invocationHasReachedAServer() being called:
* GenericClusteringException.YES
This JIRA tracks discussions to clarify the correctness of UnifiedInvokerHAProxy and any
potential coding required.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBAS-3753) HAParititonImpl implements org.jgroups.ChannelListener
by Brian Stansberry (JIRA)
HAParititonImpl implements org.jgroups.ChannelListener
------------------------------------------------------
Key: JBAS-3753
URL: http://jira.jboss.com/jira/browse/JBAS-3753
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.1.CR1
Currently if a JChannel is shunned and disconnects, higher level services are unaware of this and can't take any remedial action.
We need to do something like implement ChannelListener so an HAPartition is aware when the events on the underlying channel occur. Then devise a scheme to propagate some of the events to user code. Preferably this will follow as much as possible the existing notification scheme; i.e. pass a new view to HAMembershipListener impls that doesn't include the current node.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBCLUSTER-139) Create a general purpose group RPC API
by Brian Stansberry (JIRA)
Create a general purpose group RPC API
--------------------------------------
Key: JBCLUSTER-139
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-139
Project: JBoss Clustering
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: Q3Y6
Abstraction on top of JGroups RpcDispatcher.
Start with HAPartition as a base, but minus DRM and DS. Consider what Messaging has done as well as JBCACHE-311.
Consider separating the group membership API from the RPC API. RPC API would probably be a subinterface of the group membership one, as group RPC implies being aware of who the group is.
This is lower priority, as, except for AS, its an internal implementation detail that can be changed. But, AS exposes HAPartition as an API for end-user code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months