groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andres Almiray (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GROOVY-8076) A more helpful error message should be logged when a custom Java class cannot be resolved by the Groovy component due to a Java major/minor version mismatch
Date Tue, 07 Feb 2017 11:47:41 GMT

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

Andres Almiray commented on GROOVY-8076:
----------------------------------------

Could you provide a list of steps to reproduce the problem, perhaps the full stacktrace as
well?
How's the setup for loading MyReallyUsefulCustomClass? Is it through a groovy script loaded
via a script runner, GroovyShell, JSR-223 bridge, or other?

> A more helpful error message should be logged when a custom Java class cannot be resolved
by the Groovy component due to a Java major/minor version mismatch
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GROOVY-8076
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8076
>             Project: Groovy
>          Issue Type: Bug
>          Components: groovy-runtime
>            Reporter: ANDREY GRIGORYEV
>
> I spent a couple of hours investigating why my application would no longer successfully
deploy to the mule standalone ESB server, yet it would deploy fine to the embedded mule ESB
runtime in Anypoint Studio. The error message that I found in the server log was something
along the lines of the following:
> "... Script1.groovy: 1: unable to resolve class com.mycompany.MyReallyUsefulCustomClass
..."
> I went down all the wrong avenues trying to figure out why the Java class was not being
resolved by the Groovy interpreter.
> Eventually I stumbled upon an explanation of the problem via a Google search: a Java
major/minor version mismatch between the version of the Java runtime being used by the Mule
ESB runtime and the Java target version of the compiled custom Java classes used by a Mule
application being deployed to the Mule ESB server.
> The cause of my problem was indeed due to a Java version mismatch: the ESB server runtime
was running JRE 1.7, but the custom class being referenced by the embedded Groovy script was
compiled in Anypoint Studio using JDK 1.8.
> I would like to formally submit an Enhancement Request for Engineering to improve the
customer experience for us developers; possibly by updating the Groovy interpreter component
to detect the conflicting Java version issues and log a more helpful error message to the
logger.
> The current message "... unable to resolve class ..." is too general and does not adequately
reflect the problem of a mismatch between the JRE version and the compiled byte-code version.
> An "Unsupported major.minor version x.yy" error message instead would be an improvement.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message