Thanks -- between this and AjaxTags for JSP, there is something of a  
consensus on script.aculo.us -- I'd passed over it at first since it  
looked infernally complicated but on second glance it's no worse than  
YUI, and perhaps more flexible.  It certainly has a different idea of  
AJAX data, it can apparently work from an XHTML fragment.

Thanks also to George, but since this is also for an authority-control  
prototype I'm hoping to use something already supported and maintained  
for the popular browser platforms, so that makes a homebrew solution  
less desireable.

It is actually not too difficult to produce the AJAX responses through  
a special Cocoon pipeline.  I wrote a simple generator that emits SAX  
events and added a pipline that essentially leaves it alone; might be  
easier than adding a servlet.  I'll have that in the prototype.  This  
way, users of other AJAX libraries can just add transformation steps  
to the pipeline to get the XML schema they need.

The XHTML->XHTML translation is a neat trick.  For the prototype I'm  
working with a slightly extended DRI (to add metadata authority values  
since they have to get pre-loaded into forms for the round trip), so  
I'll stick with DRI->XHTML for now.

OBTW, I did notice the Cocoon Forms stuff but figured since the DRI/ 
Wing architecture sidesteps it completely, it would not be productive  
to try to use it.

thanks,

   -- Larry

On Jun 4, 2009, at 12:27 PM, Tim Donohue wrote:

> At Illinois, we are using Scriptaculous (http://script.aculo.us/)  
> with the XMLUI to perform autocomplete on our Subject, Publisher and  
> Author fields.  (For Author, instead of having separate lastname and  
> firstname fields, we combine it all in one field which expects  
> 'last, first m' format).
>
> We actually add in the necessary Javascript code for each of these  
> fields in our Theme by using an XSL which transforms XHTML -> XHTML.  
> So, we have our theme's sitemap.xmap setup to do the following:
>
> (1) Run through our normal DRI -> XHTML conversion via XSLT
> (2) If the path matches */*/*/submit/*.continue (i.e. in Submission  
> process), run the resulting XHTML through another XSLT to add in the  
> autocomplete javascript for the necessary form fields.
>
> On the server side of things, we did have to create a custom Java  
> Servlet (which we registered in the web.xml alongside Cocoon), to  
> process those AJAX requests and return the properly formatted  
> results. So, essentially, our autocomplete functionality is running  
> *outside* of Cocoon.
>
> There might be an easier way to do all of this...but, this is  
> essentially what we came up with as a relatively quick solution.  If  
> it is of interest, I am willing to share the code we've written for  
> this.
>
> - Tim


------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to