There is also another issue with Rhino not being available that I will deal with
tomorrow.
Stuart
On 30/10/2011, at 12:10 AM, Jaikiran Pai wrote:
Actually, this looks more like semantic change in the
Module.forClassLoader(classloader,searchParent) method. In previous
version of JBoss Modules, this method returned a "system" module if the
class (like java.io.Serializable) was loaded by the system classloader.
The JBoss Marshalling ModularClassResolver used to rely on that
behaviour. In the newer 1.1 version of JBoss Modules, the system module
isn't returned which causes this problem.
Was this semantic change intentional? If so, I guess this would require
a JBMAR change too.
-Jaikiran
On Friday 28 October 2011 08:20 PM, David M. Lloyd wrote:
> This is a strong indication that the modular class resolver is installed
> in the deserialize end but not in the serialize end.
>
> On 10/28/11 7:29 AM, Kabir Khan wrote:
>> For the timer service ones I see a lot of these errors:
>>
>> Caused by: java.io.InvalidClassException: java.io.Serializable; Class is not
present in any module
>> at
org.jboss.marshalling.ModularClassResolver.annotateClass(ModularClassResolver.java:63)
>> at
org.jboss.marshalling.river.RiverMarshaller.writeNewClass(RiverMarshaller.java:1297)
>> at
org.jboss.marshalling.river.RiverMarshaller.writeClass(RiverMarshaller.java:1140)
>> at
org.jboss.marshalling.river.RiverMarshaller.writeNewSerializableClass(RiverMarshaller.java:1367)
>> at
org.jboss.marshalling.river.RiverMarshaller.writeSerializableClass(RiverMarshaller.java:1339)
>> at
org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:877)
>> at
org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
>> at
org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
>> at
org.jboss.as.ejb3.timerservice.mk2.persistence.filestore.FileTimerPersistence.writeFile(FileTimerPersiste
>>
>> On 28 Oct 2011, at 13:20, Kabir Khan wrote:
>>
>>> Most of these seem to be timer service related. FWIW I've attached the
test report files
>>>
>>> Failed tests:
testAnnotationTimeoutMethod(org.jboss.as.test.integration.ejb.mdb.timerservice.SimpleTimerMDBTestCase)
>>>
testTimedObjectTimeoutMethod(org.jboss.as.test.integration.ejb.mdb.timerservice.SimpleTimerMDBTestCase)
>>>
testArountTimeoutInterceptorOrder(org.jboss.as.test.integration.ejb.timerservice.aroundtimeout.TimerServiceInterceptorOrderTestCase)
>>>
testRequestScopeActive(org.jboss.as.test.integration.ejb.timerservice.cdi.requestscope.CDIRequestScopeTimerServiceTestCase):
expected:<Hello> but was:<null>
>>>
createTimerService(org.jboss.as.test.integration.ejb.timerservice.persistence.TimerServicePersistenceFirstTestCase)
>>>
testCreateTimerWithInfo(org.jboss.as.test.integration.ejb.timerservice.serialization.TimerServiceSerializationFirstTestCase)
>>>
testAnnotationTimeoutMethod(org.jboss.as.test.integration.ejb.timerservice.simple.SimpleTimerServiceTestCase)
>>>
testTimedObjectTimeoutMethod(org.jboss.as.test.integration.ejb.timerservice.simple.SimpleTimerServiceTestCase)
>>>
testRollbackRetry(org.jboss.as.test.integration.ejb.timerservice.tx.retry.TimerRetryTestCase)
>>>
testExceptionRetry(org.jboss.as.test.integration.ejb.timerservice.tx.retry.TimerRetryTestCase)
>>>
testAnnotationTimeoutMethod(org.jboss.as.test.integration.ejb.timerservice.view.ViewTimerServiceTestCase)
>>>
testTimedObjectTimeoutMethod(org.jboss.as.test.integration.ejb.timerservice.view.ViewTimerServiceTestCase)
>>>
>>>
>>>
<failed-test-reports.zip>_______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev