[ 
https://issues.apache.org/jira/browse/AXIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071745#comment-17071745
 ] 

George Vasiliu commented on AXIS-2937:
--------------------------------------

Thanks for the reply!

 

We will see if the v1.6.4 could be a valid solution. You mentioned the axis2 
1.8 trunk client code still has references there, so it won't work, but is 
there some estimation/plan on fixing this in future versions ?  (eg. we might 
consider waiting for that version)

> ClassReader bytecode error in axis2 1.6.2-kernel
> ------------------------------------------------
>
>                 Key: AXIS-2937
>                 URL: https://issues.apache.org/jira/browse/AXIS-2937
>             Project: Axis
>          Issue Type: Bug
>            Reporter: George Vasiliu
>            Priority: Major
>         Attachments: Axis2Error.txt, image-2020-03-27-10-46-17-413.png
>
>
> Hello everyone,
>  
> We are upgrading our project and intend to keep the axis-2 1.6.2 distribution 
> we were using. Until now, we were using JDK 8 to compile & run the project, 
> now we have switched to JDK 11 and for only 1 webservice project we have, it 
> fails with the error seen in the attached file.
>  
>  
> I have already scrubbed the surface with 
> https://issues.apache.org/jira/browse/AXIS2-5966 and 
> https://issues.apache.org/jira/browse/AXIS2-5935, however, those fixes are 
> intended for 1.8.0, whileas we would like to add this patch for the 1.6.2 
> version, as there are many breaking changes between 1.6.2 and 1.8.0 (that 
> cause alot of validation tests to fail for XML messages due to the parser 
> inside axis2 and other issues).
>  
> Do you have any recommendations on how to approach this issue? If possible, 
> we would like to get the patch for 1.6.2 and build with maven ourselves and 
> keep it in our internal nexus as a patched jar, however, we do not know the 
> necessary changes to the ClassReader.java class that need to be done to make 
> it work.
>  
> If there is a possible workaround that can be done outside axis 2 (ie. modify 
> our webservices in a certain way) to make it work, we are also open to that.
>  
> Besides that, to confirm the issues, we compiled the entire project under 
> jdk11, but that particular sub-project was compiled under jdk8, when starting 
> the server the error is no longer shown, so a conclusion : compiling the 
> project under jdk11 breaks it when running the server. The server is a JBoss 
> 7.2.6 one.
>  
> Note that the project that fails actually contains a lot more webservices, it 
> only fails for that very specific one. I will come back with an update 
> regarding whether java7/8/9/10/11 features are used in the classes inside, 
> however, I doubt it.
>  
> The axis2.xml for the project has the following deployers configured :
> !image-2020-03-27-10-46-17-413.png|width=782,height=173!
>  
> So no .aar being deployed, issue is caused by a .class from somewhere.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to