Default would be the java's "default" functionality and ScriptedClassLoader
might be used for Groovy classes. Depending on the loader used, the class
attribute will have a different meaning. Issues with this approach: The script language must be very very similar to Java suppporting objects
and interfaces and must be able to extend native Java classes. From what
I've read, Groovy would be a candidate.
The script language meta api must support reflection like interfaces to
create object, call methods introspection etc.
Xwork must support multiple loaders which not only load the objects but
which invokes the differents reflection like APIs as well. Kind of a
factory. That sound like its not a small change.


Sounds to me that using scripted Action with WebWork is not as easy to
implement as I originally thought. May be I missed something. I'd happy to
discuss may experience in order to find a solution. Or am I the only one
believing that scripted action will make development easier and faster and
still have the option of using Java actions if performance or any other
constraints require it?



I posted a sample of most of this on my blog a while back. It shows Groovy actions (scripted, but using Groovy classes that actually implement the Action interface should be pretty much the same) and Groovy results (templating). Since Velocity's performance was much better than Groovy's I ditched it, but James Strachan from the Groovy project added a comment to my site saying that a lot of performance enhancements are in the CVS head. Today, I grabbed the latest version and tested it but ran into some class loading problems that I haven't seen before. I'll try to get it sorted out tomorrow and add at least the GroovyAction class to a Jira issue.

Cheers,

Dag


------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to