what other scripting languages will Alfresco support?

[bbailey]

The wiki roadmap mentions: 
"Release Quarter 2006 1 and 2…will also provide enhanced programming capabilities to allow non-Java developers to build extensions to Alfresco with various scripting languages."

Have you defined what scripting languages will be supported?

[rdanner]

The wiki roadmap mentions: 
"Release Quarter 2006 1 and 2…will also provide enhanced programming capabilities to allow non-Java developers to build extensions to Alfresco with various scripting languages."

Have you defined what scripting languages will be supported?

Today there is support for PHP

[rwetherall]

Hi,

Russ is correct,  today there is the starts of a PHP library that wraps access to the repository via the web service API.  I would like to start to get together a similar library for Ruby, thus allowing us to provide some Ruby-On-Rails examples that access Alfresco.

The other type of scripting support is for the repository itself to allow behaviour to be written in a scripting language.  For example it would allow you to write policy implementations in the scripting language of your choice and then configure the repository to recognise this behaviour and run it as part of the normal operation of the repository.

The fundamental framework to allow this to happen is in place, but as to languages we will support (and when it will be done) I'm not sure.  I guess we will look to the community for guidance on the scripting languages that are most in demand.

What scripting languages would you like to see us support?

Hope this helps,
Roy

[bbailey]

Thanks for the replies.

What scripting languages would you like to see us support?

Ruby-on-rails support is what I was wondering about. Also cold fusion would be nice.

[rdanner]

Thanks for the replies.

What scripting languages would you like to see us support?

Ruby-on-rails support is what I was wondering about. Also cold fusion would be nice.

What are your thoughts on cold fusion?   My understanding was that macromedia was going to end of life the scripting language (tag lib) and move to J2EE. 

Products are now available to emulate the CF servers on top of J2EE containers and servlet engines like tomcat (Blue Dragon) is the one I know of.

[miketedesco]

I'm also very interested to see Ruby-on-rails support.

[j-wicz]

The other type of scripting support is for the repository itself to allow behaviour to be written in a scripting language.  For example it would allow you to write policy implementations in the scripting language of your choice and then configure the repository to recognise this behaviour and run it as part of the normal operation of the repository.

The fundamental framework to allow this to happen is in place, but as to languages we will support (and when it will be done) I'm not sure.  I guess we will look to the community for guidance on the scripting languages that are most in demand.

What scripting languages would you like to see us support?

I think you mean the dynamic language support in spring, right? Writing interceptors in a dynamic would be really great, this would be a good duct tape within the running system, without redeployments. Would really appreciate this.

Unfortunatly the dynamic behaviour is currently broken in spring http://opensource2.atlassian.com/projects/spring/browse/SPR-1253
I think this does not only apply to Groovy but to all scripting in Spring.

Unfortunatly this bug is due to spring 2.0final which is planned not before March 06. But maybe you have an own implementation in your sleeves.

Speaking of Groovy: I would love to see Groovy support in Alfresco. Of course it had its hype in 2004 but with spring2.0 and the JSR finished it will be a nice niche scripting language in 2006. And we would have full access to all java-api of java SE50, spring and alfresco for free.

I read that the xwiki project implemented Groovy as their dynamic scripting language, but I didn't had time to look at it in detail.

[rwetherall]

I think you mean the dynamic language support in spring, right?

Not exactly.  What I mean is that Alfresco policy implementations, aspect behaviours, actions, rules and other plugable implementations could be  implemented in a scripting language (eg: Ruby) rather than just in Java as is currently possible.

This will allow behaviour to be added an Alfresco repository without the need to re-compile the server.  A powerful feature when you consider that not only can new types and aspects be added, but also behaviours to go with them.

Cheers,
Roy

[alexander]

Groovy Support is available to try:
http://forge.alfresco.com/frs/?group_id=105

This is a standard Alfresco module that can be installed with the tool (http://wiki.alfresco.com/wiki/Module_Management_Tool)

It support same object model as JavaScript and some Grails features: http://forge.alfresco.com/frs/shownotes.php?release_id=208.

Any feedback appreciated.

Thanks
Alexander

[rasputnik]

would like to start to get together a similar library for Ruby, thus allowing us to provide some Ruby-On-Rails examples that access Alfresco.

That's interesting. Are we talking about JRuby here?