cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas BOUSSUGE <nicolas.bouss...@atosorigin.com>
Subject Re: getComponent with JavaFlow 2.1.9
Date Wed, 13 Dec 2006 17:32:42 GMT

Thanks Bart, that seems to solve the problem !

Cheers,
Nicolas


Bart Molenkamp a écrit :
> I've had problems with JavaFlow and classes compiled with debug information (in Eclipse).
You could try to compile without debug information, and see if it works. 
>
> Bart.
>
>   
>> -----Oorspronkelijk bericht-----
>> Van: Nicolas BOUSSUGE [mailto:nicolas.boussuge@atosorigin.com]
>> Verzonden: woensdag 13 december 2006 10:00
>> Aan: dev@cocoon.apache.org
>> Onderwerp: getComponent with JavaFlow 2.1.9
>>
>> Hello,
>>
>> The users list was maybe not the appropriate list to post my message.
>> This seems to be a known bug of JavaFlow, according to the "TODO.txt" I
>> saw in the javaflow source.
>> Have the mentionned patches been applied to the jakarta-bcel project in
>> the 2.1.10 upcoming release ?
>> Is there a trick to get it to work with the current version ?
>> Thanks a lot
>>
>> Best Regards,
>> Nicolas
>>
>>
>> Nicolas BOUSSUGE a écrit :
>>     
>>> Hello,
>>>
>>> I got the following problem in JavaFlow (Cocoon 2.1.9) when trying to
>>> lookup a custom component :
>>>
>>> Instruction GETSTATIC constraint violated: Class
>>> 'com.test.service.ManagementService' is referenced, but cannot be
>>> loaded and resolved: 'VERIFIED_REJECTED Number of LocalVariableTable
>>> attributes of Code attribute '<CODE>' (method 'static void
>>> <clinit>()') exceeds number of local variable slots '0' ('There may be
>>> no more than one LocalVariableTable attribute per local variable in
>>> the Code attribute.'). '. InstructionHandle: 1: getstatic[178](3) 15
>>> Execution Frame: Local Variables: 0: com.test.flow.java.AdminFlow 1:
>>> <unknown object> 2: <unknown object> 3: <unknown object> 4:
<unknown
>>> object> OperandStack: Slots used: 1 MaxStack: 4.
>>> com.test.flow.java.AdminFlow (Size: 1) Execution flow: 0: aload_0
>>> [InstructionContext] 1: getstatic 15 [InstructionContext]
>>>
>>> Then I replaced the lookup as suggested by Torsten in a message on the
>>> mailing list (use a literal String instead of the ROLE), which results
>>> in the following exception :
>>>
>>> Instruction CHECKCAST constraint violated: Class
>>> 'com.test.service.ManagementService' is referenced, but cannot be
>>> loaded and resolved: 'VERIFIED_REJECTED Number of LocalVariableTable
>>> attributes of Code attribute '<CODE>' (method 'static void
>>> <clinit>()') exceeds number of local variable slots '0' ('There may be
>>> no more than one LocalVariableTable attribute per local variable in
>>> the Code attribute.'). '. InstructionHandle: 6: checkcast[192](3) 21
>>> Execution Frame: Local Variables: 0: com.test.flow.java.AdminFlow 1:
>>> <unknown object> 2: <unknown object> 3: <unknown object> 4:
<unknown
>>> object> OperandStack: Slots used: 1 MaxStack: 4. java.lang.Object
>>> (Size: 1) Execution flow: 0: aload_0 [InstructionContext] 1: ldc 15
>>> [InstructionContext] 3: invokevirtual 17 [InstructionContext] 6:
>>> checkcast 21 [InstructionContext]
>>>
>>> Is that a known bug of JavaFlow ? Or did I do something wrong ?
>>> My webapp is running under Tomcat 5.5.20.
>>>
>>> Thanks a  lot.
>>>
>>> Regards,
>>> Nicolas
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>>> For additional commands, e-mail: users-help@cocoon.apache.org
>>>       
>
>
>
>   

-- 
-----------------------------------------------
Nicolas BOUSSUGE
Atos Origin - Agence Sud-Ouest
18 av de l escadrille Normandie-Niemen  BP 20
31701 Blagnac Cedex

Bureau   : 05.62.74.59.69
Télécopie: 05.62.74.59.00
 
mailto :nicolas.boussuge@atosorigin.com


Mime
View raw message