RE: [OS-webwork] Chaining Actions

Title: Message so if parameter1 is null from JSP to Action1 and is set to parameter1=2 in Action1, andthen chain toAction2. Should the parameter1 be null or 2? tricky question :) For methe result gets: parameter1=null in Action2. I use ChainingInterceptor is this right? Haven't i

Re: [OS-webwork] webwork 2 - iterator status

It works!.and the reference for status should go without the '. Thanks! try using ww:if test=#rowstatus.modulus(3) == 0 [EMAIL PROTECTED] wrote: I'm having problem getting the iterator status to work. Here's a snip of the code: ww:iterator value=dataList status='rowstatus'

RE: [OS-webwork] ww2 initial impressions docs

Jason, under URLtag the encode stuff needs to be removed in webwork.tld (and maybe taglib.tld). I´m using the following configuration in web.xml: taglib taglib-uriwebwork/taglib-uri taglib-location/WEB-INF/webwork.tld/taglib-location /taglib After removing the encode stuff it works.

[OS-webwork] Unit-testing actions in WW1.3

Hi, I have a base class from which all my actions extend. This base class uses ActionContext to read properties file, initialize database connections, and so on. Now, when I create a new action, how can I unit-test it? I haven't tried it because the idea seems absurd to me, but do I need to

RE: [OS-webwork] Unit-testing actions in WW1.3

You could try refactoring your base Action class to use Dependency Injection with a container like Spring (there's docs on using Spring with WW1.x on the Wiki). Then, to unit test, you could just create a Mock DataSource, etc.. Otherwise, you'll need to manage ActionContext scopes yourself, in

[OS-webwork] Problems validating optional fields

Recently I wondered if it's possible to validate optional fields using the ValidationInterceptor, and there seemed to be a bug in the email validator not accepting an empty value. I have the same problem with the url validator. Can someone confirm that these don't work so it's not a mistake in

[OS-webwork] Re: WW2 doesn't work in Suse Linux 9

Carlos Jacobs schrieb: WW2 doesn't work in Suse Linux 9. Servlet container Tomcat 4.1.27 I've dropped webwork-example.war in Tomcat's webapps directory. If I test any sample, ww2 fails. Errors: [...] java.lang.RuntimeException: Unable to instantiate VelocityEngine! [...] What JDK version do

RE: [OS-webwork] Problems in validating optional fields

I've fixed both the URL and Email Validator in CVS, and the fixed versions will be available in the 1.0.1 release of Xwork. -Original Message- From: Sakke Wiik [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 17, 2004 12:28 PM To: [EMAIL PROTECTED] Subject: [OS-webwork] Problems in

Re: [OS-webwork] WW2 doesn't work in Suse Linux 9

Thank you Well, now it is working. Velocity couldn't access to some files. I've setted permissions properly and all works fine. I'm sorry, I'm a newbie ... Carlos Los mejores usados y las más tentadoras ofertas de 0km están en Yahoo! Autos. Comprá o vendé tu auto en

[OS-webwork] Validating length of optional string-field

One more validation problem... How can I validate the length of an optional String with the ValidationInterceptor when there's no String-validator, just a requiredstring one? Other types like int and date are not a problem since you can give them the min and max parameters. Shouldn't there be

RE: [OS-webwork] Validating length of optional string-field

You can just write your own validator class and add it to your validators.xml... It's very easy, just look at the validator classes in Xwork. -Original Message- From: Sakke Wiik [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 17, 2004 1:59 PM To: [EMAIL PROTECTED] Subject:

RE: [OS-webwork] bug in select tag (WW2)?

duh, I think I've been bitten by the JBoss UCL. I've deployed every example/skeletal war file I could find including a few from Webwork1.4. I went back and looked at the select.vm from webwork1.4 and, at the least, it had the odd line #bean (webwork.util.ContainUtil $contain), which isn't in the

RE: [OS-webwork] bug in select tag (WW2)?

Thanks for the update... Has anyone else had problems having both WW 1.x and WW 2 installed? -Original Message- From: Alex Radka [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 17, 2004 4:57 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] bug in select tag (WW2)? duh, I

Re: [OS-webwork] Unit-testing actions in WW1.3

Why not just use GenericDispatcher? You should be able to set up your environment programatically and make sure everything is populated correctly in your ActionContext (given of course that you avoid all web-specific calls). Have a look at ServletDispatcher, you'll see that all it is is a

Re: [OS-webwork] XMLRPC dispatcher and view

Does it supports different encoders. Few monts ago I had to write my own XMLRPC library, only because no one had support for character encoding. Regards Remis - Original Message - From: Simon Stewart [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 17, 2004 6:07 AM