Re: Groovy file as a service

[Joe Eckard]

Take a look at /framework/service/src/org/ofbiz/service/engine/ GroovyEngine.java... all you need to do to is create a map called "result" in your groovy script and put your OUT parameters there.

On Apr 14, 2010, at 10:24 AM, Kranti Agrawal wrote:

The error below is just a type mismatch... groovy strings in with variables in them (${ex}) are GStrings, not Strings. You can fix this by calling .toString() on the groovy string before putting it into the result map.

Can you please give some examples of groovy services which return a List?

Regards,
Kranti Agrawal
Student, IIIT Bangalore
krantiagrawal.blogspot.com

On Wed, Apr 14, 2010 at 7:53 PM, Robert Morley <rmor...@emforium.com> wrote:

We had a period of time where people wrote some services in groovy.

most part) have no OUT parameters and the ones that do return a

(granted it must have worked at one point in time).


On Apr 14, 2010, at 9:42 AM, Kranti Agrawal wrote:

Hi,

However, in our Obiz code we report the same error as what is listed here (with testGroovy). The groovy services we currently have in play (for the GenericEntity, a List, and an Integer (all of those I would suspect are working). Appears we have a bug here dealing with String OUT parameters

I tried running the service 'testGroovy' in the Service Engine under
webtools, I got the following error

<li>Service dispatcher threw an exceptionType check failed for field

[org.codehaus.groovy.runtime.GStringImpl]

[testGroovy.successMessage]; expected type is [String]; actual type is

smime.p7s
Description: S/MIME cryptographic signature