I've spent the last several days digging into this. If I got some guidance I think I might be able to help with this issue.

I'm interested, because I'm trying to move my actions for Struts 2 to Groovy. They need to have prototype scope to make it work though.

Thanks,

Mark

I will prepare a zip file which contains my workaround for this scope problem and upload here. In order to allow script bean has scope, you need to change the following file:
org.springframework.scripting.config.ScriptBeanDefinitionParser.java

In the ScriptBeanDefinitionParser java file, there is a method called parseInternal where you should find a RootBeanDefinition object which is used to control the scope of the script bean.
The current code of Spring 2.0.3 is:
,,,
protected AbstractBeanDefinition parseInternal(Element element, ParserContext parserContext) {
...
RootBeanDefinition beanDefinition =
new RootBeanDefinition(this.scriptFactoryClass);
beanDefinition.setSource(parserContext.extractSource(element));
...

In order to control the script bean scope, the above code should modify to:
,,,
protected AbstractBeanDefinition parseInternal(Element element, ParserContext parserContext) {
...
RootBeanDefinition beanDefinition =
new RootBeanDefinition(this.scriptFactoryClass);
beanDefinition.setSource(parserContext.extractSource(element));

// suppose you have already get the script scope value in above and
// store in a String variable called scriptScope. scriptScope should be
// either singleton or prototype
beanDefinition.setScope(scriptScope) ;
...
You can refer to the parseInternal method to get an idea how all the attribute values are retrieved. Also you need to edit the xsd file to allow script-scope attribute. The xsd file is:
src/org/springframework/scripting/config/spring-lang-2.0.xsd

Find the following section in spring-lang-2.0.xsd:
...
<xsd:complexType name="simpleScriptType">
...
<xsd:attribute name="script-source" type="xsd:string">
...
</xsd:attribute>
...

Then add a new xsd attribute script-scope after the above script-source attribute. For example:

...
<xsd:complexType name="simpleScriptType">
...
<xsd:attribute name="script-source" type="xsd:string">
...
</xsd:attribute>
<xsd:attribute name="script-scope" type="xsd:string">
</xsd:attribute>
...

Rebuild the spring.jar and with the update xsd file. You can add the "script-scope" attribute to groovy bean definition like normal bean. If you found any problem, please alert me. So far it works fine in my application. But I am still afraid of any hidden problem.

cheers
chris tam
xenium

This is a quick patch against 2.0.2 to enable 'prototype' and 'singleton' script beans. It adds 'script-scope' to the lang:script_lang tag. The acceptable values are 'prototype' and 'singleton'. If no script-scope is present beans are singleton.

I have not tested this extensively. I also have no experience with the Spring tests. If someone could provide some advice I'll write some tests.

This patch would probably also work against HEAD, but I had some issues with getting that working, and had the 2.0.2 source.

Dear Mark

Thanks a lot. I will try the patch. Since I am currently working on a project of my company, I will try your patch as soon as possible and give any feedback.

cheers
chris tam
xenium

Dear Mark

Thanks a lot for your patch. I have ported my junit test programs for 2.0.3 to 2.0.2 and your patch passes all junit test programs for Groovy. Since there are some problems for Beanshell and JRuby in 2.0.2, I have skipped the test for Beanshell and JRuby. You have mentioned a "HEAD" problem in your comment. Would you mind tell me what is "HEAD" problem? I have 2 concerns about the solution:
1. Is there any hidden problem with the refresh attribute?
2. Is there any hidden problem with inline-script?
If you find any problem, please alert me. Since my junit programs contains some codes which are related to my current project of my company. I need to clean it up before I attach my junit test program here. I must thank again for your help.

cheers
chris tam
xenium

Thanks for pointing this out! While we do support custom script scopes at the ScriptFactory level already (as of 2.0.3), this is not exposed in the "lang" namespace yet.

Hence I've added a "scope" attribute to all script tags in the "lang" namespace, allowing for non-singleton script objects defined in that convenient style, analogous to the "scope" attribute in a standard bean definition.

This should be available in tonight's 2.0.4 snapshot. Please give it a try and let me know whether it works for you!

Juergen

The "scope" attribute in 2.0.4 snapshot works fine in my application and junit test programs. Thanks Juergen.

cheers
chris tam
xenium