Hi Dick
See my replies to the two subthreads ;-) going
on with this thread.
on the stack, while now it will be null instead. I do not
think other code
relies on that dubious feature.
So to me your fix looks ok.
Thank you very much for taking the time to check my fix
so fast. I will let
Zetterberg
- Original Message -
From: Vedovato Paolo [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, February 05, 2004 5:05 PM
Subject: RE: [OS-webwork] WW1.3 Memory Consumption
Ok, I Found some more on this issue.
This Query problems occur only when the ww:table tag is used
webwork 1.4 and see if you still have the
leak?
On Feb 5, 2004, at 11:05 AM, Vedovato Paolo wrote:
Ok, I Found some more on this issue.
This Query problems occur only when the ww:table tag is used.
As far as i see in my Profiling Tool the WebTable component
tries to do something
Hi Dick
for my replies see inline.
You are right that the Query class contains a cache of all expressions
(instances of Query). It is a static HashMap in WW1.3 so it
is never GC'd as
you know.
I can see a couple of cases that would make it grow:
1. Parameters that are sent in requests
this reference changes on each request putting
it in the Query Hashtable and so this grows with each
request.
Any clues about this phenomena?
Cheers
-Paolo
-Original Message-
From: Vedovato Paolo
Sent: Thursday, February 05, 2004 9:53 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [OS-webwork
tested this and I don't see the behaviour you describe in the
current CVS. Can you try webwork 1.4 and see if you still have the
leak?
On Feb 5, 2004, at 11:05 AM, Vedovato Paolo wrote:
Ok, I Found some more on this issue.
This Query problems occur only when the ww:table tag is used
quote
The problem is that the ChainingActionFactoryProxy copies all
parameters from the first Action to the target action (the Redirect
action in this case). This includes the errors and
errorMessages Maps.
So, is the problem then that the validate method in
ActionSupport throws
here some feedback related to the stuff I asked/reported
- WW-136 Redirect does not work properly. Reported by Paolo
Vedovato and discussed on list. Is Jason working on this?
open
- WW-89 Redirect problem. Reported by Paolo Vedovato. Is this
problem still there? Related to WW-136?
just
Yes I posted a version that would be backwards compatible but
it seemed as if others (Hani I think) preferred the default
behaviour to be changed to be like in the new version. I can
modify my posted version and then the table tag/template
would have to be modified as well in that case.
Hi Jason
I opened an issue in jira where I've attached a testwebapp which
demonstrates the bug.
http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-136
Thanks for having a look at it :-)
Cheers
-Paolo
---
This sf.net email is
Hi all
After having migrated to WW 1.3 I came across following problem:
We use the Redirect action from within our actions/commands to redirect to
an ErrorHandlingAction in case an Exception arises when executing an
action/command. To do so we've overwritten the execute method in our base
action
Hi Jason
Which version of 1.3 do you have? The released version or the latest
CVS? I made a change to make the Redirect action not implement
CommandDriven because I was getting this kind of problem when
trying to
redirect from a CommandDriven action, because the Redirect action did
not
sorry to come in so late...;-)
I think the default should be how it is now, since after the
last change, people
have on the whole adapter their code to the new behaviour.
no problem with that, but then it should be remembered to adapt the
webwork table jsp template to mirror the original
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]
I remember that it was asked in the mailing list if this change would affect
a
existing webapp. I remember also that I made a grep through our code and
I didn't see that we used the url tag directly without a value attribute.
BUT what was missed (I also did forget) was to make a grep though
Hi all
we use the webtable ww tag in our application. After installing 1.3.0 rc1
the sorting in our tables in our application doesn't behave correctly
anymore.
After some investigating I saw that the URLTag in the way that POST'ed data
isn't included anymore when the url tag has no value
PROTECTED]]
Sent: Monday, December 30, 2002 8:42 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Ognl as replacement for WW EL
Vedovato Paolo wrote:
I think that it's a very important point to be able to
switch to XWork
without having code changes AND to have all the improvements (like
performance
ww 1.2.1
I came scross following problem:
two variants of methods in an Action:
1) public boolean isList()
2) public boolean isLIST()
if I access 1) with the property or if tag (eg.: ww:property value=List
/) the method is NOT processed.
if I access 2) with ww:property value=LIST / it IS
hi pat
just a little wish...could you have a look at the webtable stuff I sent to
list and add it to the cvs so it comes also with 1.3?
btw: great redirect bug fix...now everything works also perfectly on bea
:-))
thanks!
cheers and good look for the xwork bet...
-paolo
-Original
Hi Webworker
how can I achieve such a behaviour:
ww:url value='anAction.action' id=url/
ww:bean...
ww:param name='link' value=@url/
/ww:bean
since the ww:url tag doesn't have an id to be able to reference to it,
I didn't find a way to reuse a ww:url content in a JSP.
TIA
-Paolo
ww: current cvs version
app server: wls7.0sp1, orion 1.6.0
using ww:include page=../navigation/header.jsp / fails with following
stacktraces:
orion:
--
javax.servlet.jsp.JspTagException: javax.servlet.ServletException: Not a
valid resource path:/html/access/navigation/header.jsp
at
Paolo,
Could you add the URL you used and your directory structure to
this bug
report?
Thanks,
Maurice
Vedovato Paolo wrote:
ww: current cvs version
app server: wls7.0sp1, orion 1.6.0
using ww:include page=../navigation/header.jsp / fails
with following
stacktraces:
orion
+1 to change the behaviour in 1.3
-Paolo
-Original Message-
From: Maurice C. Parker [mailto:maurice;vineyardenterprise.com]
Sent: Thursday, November 07, 2002 2:57 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] JIRA Issue WW-79: PropertyTag shouldn't print
when id is sepcify [PATCH]
23 matches
Mail list logo
