I've come to learn that the problem is not Resin. As you've noted, it's
groovyc. I've not considered your suggestion before but I will give it a
try. Your blog post is quite interesting. Not sure what to make of this
whole thing and what it really says about groovy's use out said of grails.
It sucks to have to dig this deep just to use Groovy in a covenient way.
Thanks for the help.
Daniel López wrote:
> What we do is to use the Groovy scripts through the Java Scripting API
> during development and then compile them into class, if desired, for
> production. Accessing Groovy scripts is not too slow, after the first
> access, if you are careful not to throw the ScriptingEngine object after
> each access, as creating them is the most expensive operation.
> I did some experiments with it not that long ago:
> So we opted for scripting during development, as even though you might
> get groovyc compilation to work, I'm not sure why but Hot Swapping does
> not seem to work with groovyc generated classes and each time you make a
> change, the context is restarted and it can become quite a pain.
> bumzee escribió:
>> Yeah, it works for me too all pre-compiled, but I'm trying to get a
>> development environment.
>> Resin will compile your java classes and reload changes and supposedly do
>> this with groovy too, but I've not been able to get it to work.
>> bumzee wrote:
>>> Is anyone successfully using Groovy with Resin ?
>>> What does your resin.conf look like ?
>>> This is on the resin website, but it doesn't work for me in 3.1.5.
>>> When it gets to a groovy file the compilation just stops or times out.
>>> <compiling-loader path="WEB-INF/classes"
> resin-interest mailing list
View this message in context:
Sent from the Resin mailing list archive at Nabble.com.
resin-interest mailing list