Frank, Having used your JWP to implement a text auto-complete gadget I though both the implementation and the instructions were great. I had it working in a few hours. Thanks!
Following the earlier thread entitled Tags For Pagination I wondered if JWP might take this generic problem up. Paging through results seems to me an ideal use of AJAX. After following your example with JWP I turned to this exact situation a month or two ago and couldn't see a quick solution, but then I'm a dummy when it comes to AJAX. Suppose you have a search facility that performs an initial search that returns 5000 results and you wish to provide functionality to allow users to page through the 5000 results 100 or 500 results at a time. The initial search can easily store ids of objects in the users session and additionally you can easily write a servlet ( as in your examples ) that builds up the appropriate page of results into html. On the jsp I wrote a paging section like this: <Previous> 1 - 2 - 3 - 4 .... <Next> Each a link to the servlet that built up the appropriate set of results using the page number. The problem was that the paging navigation needs to change each time. For example if you are on page 1 there is no <previous>. If you are on the last page there is no <Next> and also I wanted the current page not to be a link. You already have that page and it helps the user to know where they are so I coloured that page in red I think. But I couldn't see a way of making the servlet redraw the links. I hope this makes sense.. Is there a work around to this or am I just talking nonsense? I feel that this should be possible and perhaps could be turned into some generic JWP tags. Certain from reading the other threads I can see other developers looking at the same problem. Rgds Kevin -----Original Message----- From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] Sent: 24 January 2006 05:19 To: Struts User; Tomcat User Subject: [OT-ANN] Java Web Parts v1.0 beta3 Hi all... I haven't been posting JWP release announcements here lately, and generally I will refrain from doing so, but the team just put out a new release last night and I think it has some features that might be of interest to many of you... * AjaxTags now has some new capabilities, including the ability to have multiple config files, the ability to have static parameters on the target URLs, a built-in debugging facility and an implicit passing in of the ajaxRef with each request, so now you can always determine which element fired the event. * The Chain implementation now supports loading config files from JAR files, and there is now a SimpleCommand that you can extend (instead of implementing Command) that has default implementations of all three Command methods (init(), execute() and destroy()), so you can only worry about the ones that interest you. * A new popup calendar widget has been added to the UIWidgets taglib. * JSDigester was added to the JSTags taglib. JSDigester, as you may be able to guess, is a client-side implementation of our beloved Commons Digester. It is not as full-featured as it's big brother, but it can come in *very* handy, just like the full-fledged Digester. Take care! -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ------ -------------------------------------------------------------------------------- The information contained herein is confidential and is intended solely for the addressee. Access by any other party is unauthorised without the express written permission of the sender. If you are not the intended recipient, please contact the sender either via the company switchboard on +44 (0)20 7623 8000, or via e-mail return. If you have received this e-mail in error or wish to read our e-mail disclaimer statement and monitoring policy, please refer to http://www.drkw.com/disc/email/ or contact the sender. 3166 -------------------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
