Hey,
I'm struggling a bit over XWork's Result, ActionChainResult and
ResultInterceptor.
It all started because:
a) if I try to createActionProxy for an action that doesn't exist I get
a ConfigurationException.
b) ActionChainResult and ResultInterceptor swallow exceptions when the
action I
jason
i'm using Iterator and get some values fom the database, and i need to
give a link to the value and in that link i need to pass
parameters (i,e thru querystring). how do i pass the values thru the
querystring
This is my code and the parameter for result.jsp?qid is null. hopw do i
get
no it's not working,
in this the ID is displayed and not set as a QueryString,
even i'm able to display it but, setting it as a querystring is creating
problems
any other way for this
snehal
Cathal Cullinane wrote:
try something like this
a href=webwork:url
anyway i found it out, thnx for the reply,
a href=result.jsp?qid=webwork:property value='qid'/it:property
value='ques'//a
this one works. thnx
snehal
Cathal Cullinane wrote:
try something like this
a href=webwork:url page=SomeAction.action?qid=/webwork:property
value=qid/it:property
-Original Message-
From: Trevor Squires [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 4:21 AM
To: Webwork List
Subject: Re: [OS-webwork] can't grok XWork Result workings
Yowch.
I think I've figured out what the 'magic' was. It would
appear that there is only
Alright, so based on the feedback so far, the consensus seems to be:
webwork jsp UI tags are much slower than velocity equivalents. So the
culprit seems to be the webwork UI tags, not jsp itself.
On Thursday, March 13, 2003, at 12:13 PM, boxed wrote:
scriptlets will probably be almost as fast,
hi
how do i get values from a querystring inanother page
a href=result.jsp?qid=webwork:property value='qid'/it:property
value='ques'//a
here i'm passing the qid to result.jsp, how do i get the value of the qid
i tried webwork:property value=qid/ in my result,jsp
how to do it?
thnx
regards
snehal
Hani,
It is fairly simple to test - given that CVS HEAD has tags based on
either velocity or jsp.
There are two sources of potential slowness with jsp:
- parsing rendering overhead
- rd.include() overhead.
From my experience both of the above can be reduced by using velocity.
Tomcat (until
Hani Suleiman wrote:
Alright, so based on the feedback so far, the consensus seems to be:
webwork jsp UI tags are much slower than velocity equivalents. So the
culprit seems to be the webwork UI tags, not jsp itself.
Well, it's the base JSP include overhead that is bad, really. Including
a JSP
Well, again, that tests webwork, not jsp vs velocity. A 'real' test
would be one where webwork is NOT part of the equation, or at least,
there is a VERY thin 'glue' UI specific layer.
Also using tomcat for any kind of performance test like this one would
be rather...silly. It'd be like using
after getting the value thru the querystring qid how do i set it to a
method in my class and send it as a parameter.
in my class i have a method called
public void setQID(int _qid){
this._qid=_qid;
}
and in my JSP,
poll:property value=$qid/hr
poll:action
11 matches
Mail list logo
