Firsthand, you shouldn't really be putting them in the conf directory, this
is the location for global Mule settings, not app. Put them in lib/user
instead, either jarred or unpacked.
Next, if you import a class, it *must be a compiled class*. Doesn't matter
if it's in Java originally or Groovy, but it has be compiled.
HTH,
Andrew
On Mon, Nov 9, 2009 at 3:31 PM, Steve A. <steve@asanderson.com> wrote:
>
> Greetings!
>
> I'm having trouble importing a custom groovy class from my custom groovy
> script.
>
> I keep getting an "unable to resolve class" error although both scripts are
> located in $MULE_HOME/conf/groovy.
>
> Is there something special that needs to be done configuration-wise in
> order
> for custom groovy scripts to be recognized on the classpath?
>
> Steve
> --
> View this message in context:
>
http://old.nabble.com/importing-custom-groovy-class-in-custom-groovy-component-tp26273164p26273164.html> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
>