[OS-webwork] WW, XWork newbie,

Hi ! Can someone explain me what is XWork really !? Just a new version of WW, with additional functonalities, or WW with basic API implementation (Portlet API..). This question, because i want to port the Websphere Portal Server / portlet API to WW, if possible. Is it better to switch to XWork ?

Re: [OS-webwork] WW, XWork newbie,

I don't think we're sure yet. On Tue, 14 Jan 2003, [iso-8859-1] Joel Cordonnier wrote: Hi ! Can someone explain me what is XWork really !? Just a new version of WW, with additional functonalities, or WW with basic API implementation (Portlet API..). This question, because i want to port

Re: [OS-webwork] newbie: should I use 1.3 or 1.2.1?

I would suggest using 1.3.. I have been using it from CVS for a large number of projects and it's worked out great. There are many bug fixes that you would surely run into with 1.2. The documentation does need some help, if you read the JDJ (Dec issue) I have pointed this out. There are ways

Re: [OS-webwork] Scope for 1.4

Kirk, I think new users will tend to download the most stable version of a product instead of the latest cutting edge version especially when documentation is lacking. What do you guys think? Is 1.2 a lost cause at this point? Is it better to focus on the 1.3 release only? I agree

[OS-webwork] passing parameters to a field validator

I see you use PropertyDescriptor to do field validation. How do I pass parameters to propertyEditorClass so I can re-use a validator across different fields? Example: Suppose I have an IntegerValidator which can check a range. Have you guys thought about adding a field group validation

Re: A plea - WAS Re: [OS-webwork] Reflection

On Tue, 2003-01-14 at 21:17, Robert Nicholson wrote: Why does it have to be a MDB? Can't you just make a listener? What will an MDB buy you? In a word: transactions (oh also instance caching for tuning but that would be more than 1 word :) ) We use a lot of MDBs in our app for these

Re: [OS-webwork] Scope for 1.4

Mike, We use JIRA and the performance is fine but our product webwork code performance is awful at the moment. Have you any tips for the performance challenged ? On Tue, 2003-01-14 at 16:00, Mike Cannon-Brookes wrote: Kirk, As a guide, we've been shipping code based on 1.3 for a few months

RE: [OS-webwork] Scope for 1.4

I assume that JIRA uses OSCache, right? Jive 3.0 default skin uses webwork also but they avoid the UI tags completely. Here is what I did to make my countries list very fast. It isn't ideal but it works and it was plugin compatible to the ui:select tag. FYI I got the execution time down

Re: [OS-webwork] Scope for 1.4

Yup, Kirk's option here is the best way to get immediate performance improvements. I've made a very generic selectfastmap.jsp template for large lists of Map objects. Works much faster. -Pat - Original Message - From: Kirk Rasmussen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday,

RE: [OS-webwork] Scope for 1.4

Not really. It gets its speed because the template is single purpose -- i.e. for creating the select list for countries (254 elements). The list is not passed in to the template. The list is obtained by calling another action within the template. This was just one example of how to optimize

Re: [OS-webwork] Scope for 1.4

Kirk, Well - yes and no. JIRA uses OSCache, but not for the UI tags. None of those are cached at all, and we have literally hundreds ;) OSCache is only used where certain pages take a long time to generate for various reasons (most often because of the computations required to calculate the data

RE: [OS-webwork] Scope for 1.4

Mike, I should qualify that I am running the 1.2.1 build for my tests. I have not tried 1.3 RC1 yet. However, even when I eliminated the ui:select tag and used a straight webwork:iterator to product the select list it only reduced the execution time to 10 secs versus 13 secs. To me this

Re: [OS-webwork] Scope for 1.4

Kirk Rasmussen wrote: Has anyone profiled webwork with JProbe or similar tools to look for hot spots that could be optimized? Yes, but it was some time ago. I'm probably going to profile it again once I decide to update the webwork version that Jive is using (currently 1.2.1 + a lot of cvs

Re: [OS-webwork] Scope for 1.4

Kirk, Ahh - I would suggest that you update CVS, it is much, much faster and most of these performance improvements have already been made :) Cheers, Mike On 15/1/03 1:10 PM, Kirk Rasmussen ([EMAIL PROTECTED]) penned the words: Mike, I should qualify that I am running the 1.2.1 build for my

RE: [OS-webwork] Concern and Opinions

I also did some reflection on this issue and François summed up nicely all my thoughts. I completely agree with him. -Paolo -Original Message- From: Francois Beauregard [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 5:35 AM To: [EMAIL PROTECTED] Subject: [OS-webwork]