If the user scripts are already existing, which version of Groovy were they
targeting? I've seen this behavior (of treating identifiers starting with
an uppercase letter as potential class names) for my entire life as a
Groovy developer, which started several years ago.
On Tue, 25 Feb 2020 at
User scripts were coded Beanshell, I try to migrate to Groovy ...
From: Alessio Stalla
Sent: Tuesday, February 25, 2020 11:16
To: users@groovy.apache.org
Subject: Re: please help : GroovyCastException: why ?
If the user scripts are already existing, which
It is still a bit hard to let you know the best way to proceed from just
the sample you have shown without more context.
If I had a class Article and an instance Article (I am assuming from the
binding), then I would either:
* use an alias for the class, i.e.:
import Article as MyArticle // then
Unfortunatly yes, that's what I need to do, passing an Article instance into a
variable named "Article", not "article" like it should be ...
Because of existing user scripts which must continue to work without
refactoring.
How can I deal with it ?
From: MG
