[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, 4 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, 4 months
[JBoss JIRA] Created: (JBAS-5065) Create a Debian/Ubuntu package
by David Rabinowitz (JIRA)
Create a Debian/Ubuntu package
------------------------------
Key: JBAS-5065
URL: http://jira.jboss.com/jira/browse/JBAS-5065
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Build System
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.5.GA
Environment: Debian, Ubuntu
Reporter: David Rabinowitz
Assigned To: Rajesh Rajasekaran
JBoss is often used in Linux based servers. Since Debian and Ubuntu are gathering momentum, it would be very helpful toi integrate with their package system. It will simplify the installation process very much (like currently with tomcat, or with the RPM version, which is quite old)
--
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, 4 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, 5 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, 5 months
[JBoss JIRA] Created: (JBAS-5245) JBossMQ services: table creation fails with Sybase Adaptive Server Anywhere (ASA)
by Luc Texier (JIRA)
JBossMQ services: table creation fails with Sybase Adaptive Server Anywhere (ASA)
---------------------------------------------------------------------------------
Key: JBAS-5245
URL: http://jira.jboss.com/jira/browse/JBAS-5245
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.2.GA
Reporter: Luc Texier
Assigned To: Adrian Brock
the database is Sybase Adaptive Server Anywhere (ASA). The JDBC driver jConnect for JDBC 3.0 v6.0x
2008-02-14 18:25:01,640 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Could not create table with SQL: CREATE TABLE dbo.JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER NULL, TXOP CHAR(1) NOT NULL, MESSAGEBLOB IMAGE NOT NULL, PRIMARY KEY (MESSAGEID, DESTINATION) ) LOCK DATAROWS
com.sybase.jdbc3.jdbc.SybSQLException: SQL Anywhere Error -131: Syntax error near 'LOCK' on line 1
at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.updateLoop(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.executeUpdate(Unknown Source)
at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeUpdate(Unknown Source)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:251)
at org.jboss.mq.pm.jdbc2.PersistenceManager.createSchema(PersistenceManager.java:280)
at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1796)
Note that those issues do NOT occur when these services are connected to Adaptive Server Enterprise (ASE)
Note2: internal reference Issue #162081
--
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, 5 months