Sylvain Wallez wrote:
A solution is to keep the uploaded content in a temp area until the form
is valid. But what if the user leaves and never re-submits the form?
Should we rely on the garbage collector to finalize() the upload widget
to clean the temp area?
How about catching the expiration
Joerg Heinicke wrote:
Chris, please add [EMAIL PROTECTED] to CC if you assign a bug to
your self. Otherwise the list won't get informed about any comments or
status changes.
Joerg, did you add the CC or did it appear by default? ('cause I didn't
since I believe it used to be that dev is always
On 09.11.2003 09:48, Christian Haul wrote:
Joerg Heinicke wrote:
Chris, please add [EMAIL PROTECTED] to CC if you assign a bug to
your self. Otherwise the list won't get informed about any comments or
status changes.
Joerg, did you add the CC or did it appear by default? ('cause I didn't
Joerg Heinicke wrote:
On 09.11.2003 09:48, Christian Haul wrote:
Joerg Heinicke wrote:
Chris, please add [EMAIL PROTECTED] to CC if you assign a bug to
your self. Otherwise the list won't get informed about any comments
or status changes.
Joerg, did you add the CC or did it appear by default?
Christian Haul wrote:
Subscribers register themselves with the EventManager. However, in order
to do this, they need to live in the same component manager space as the
portal. This prevents e.g. startable + threadsafe components to
subscribe. As a consequence, the
Carsten Ziegeler wrote:
Christian Haul wrote:
Subscribers register themselves with the EventManager. However, in order
to do this, they need to live in the same component manager space as the
portal. This prevents e.g. startable + threadsafe components to
subscribe. As a consequence, the
On 8 Nov 2003, at 23:21, David Crossley wrote:
joerg wrote:
Modified:src/webapp/samples/text-wrap welcome.html
Log:
fixed typo
we have a HTML file in our CVS ;-)
LOL.
I am ashamed to say that i sometimes find it easier to
knock up a simple html cover page to drive a sample,
On 9 Nov 2003, at 00:06, Sylvain Wallez wrote:
Hi all,
I'm attacking the problem of uploads in Woody. Upayavira started to
work on this some time ago but hadn't the time to finish, so I asked
him to send me the baby for it to continue growing.
But upload is a difficult problem when the nice
Stefano Mazzocchi wrote:
On 9 Nov 2003, at 00:06, Sylvain Wallez wrote:
Hi all,
I'm attacking the problem of uploads in Woody. Upayavira started to
work on this some time ago but hadn't the time to finish, so I asked
him to send me the baby for it to continue growing.
But upload is a
Christian Haul wrote:
Carsten Ziegeler wrote:
Christian Haul wrote:
Subscribers register themselves with the EventManager. However, in order
to do this, they need to live in the same component manager space as the
portal. This prevents e.g. startable + threadsafe components to
subscribe.
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24463.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Carsten Ziegeler wrote:
Christian Haul wrote:
Still, DefaultChangeAspectDataEventSubscriber is a hack since components
should subscribe themselves instead of this proxy.
Yes, it's a hack and yes components should subscribe themselves, but data
objects are not components and therefore shouldn't
First I want to say thanks to David for putting the text-wrap sample
together.
--- Additional Comments From [EMAIL PROTECTED]
2003-11-09 01:58 ---
Sorry for being destructive, but I do not see a real problem.
Or better said
this problem resulting from trying to handle all types of
starts tonight - release is (hopefully) on thursday.
Regards
Carsten
Sylvain Wallez wrote:
Ugo Cei wrote:
Sylvain Wallez wrote:
A solution is to keep the uploaded content in a temp area until the
form is valid. But what if the user leaves and never re-submits the
form? Should we rely on the garbage collector to finalize() the
upload widget to clean the temp
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24498.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Sylvain Wallez wrote:
Ryan Hoegg wrote:
peter royal wrote:
Anyone:
Any thoughts about using Jelly as the builder for the sitemap?
Its usage can be completely hidden, but as a tag processor, it might
work very well. We could use it to construct a bean-graph to model
the sitemap.
-pete
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24500.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24498.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24500.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Quick and nasty one... me feels a bit stupid now. Since in javascript
delete is a reserved keyword, how do I call a delete() function of a
java object? I know there must be a quick 'n easy solution out there,
but it's escaping my mind ATM.
Suggestions?
--
Gianugo Rabellino (preparing his
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24463.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Me felt stupid too once ;-)
http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=106500375605928w=2
-Original Message-
From: Gianugo Rabellino [mailto:[EMAIL PROTECTED]
Sent: maandag 10 november 2003 1:26
To: [EMAIL PROTECTED]
Subject: Newbie flow question: calling a delete() method
That's why I'm suggesting an action of type flowscript that would call a
function defined in the script files listed in map:flow and thus be able to
share the session-global variables with map:call statements. Think of this
action as a secondary controller in a MVC model (they fine-tune the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24463.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
It might sound pedantic, but it is about efficiency.
I have wasted a lot of time during my committer life with
confusing patches that contain mainly whitespace changes.
Not to criticise the patcher or their tools, but today
was a classic. With some manual tweaks to whitespace,
i managed to bring
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24463.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
David Crossley wrote:
It might sound pedantic, but it is about efficiency.
I have wasted a lot of time during my committer life with
confusing patches that contain mainly whitespace changes.
Not to criticise the patcher or their tools, but today
was a classic. With some manual tweaks to
Gianugo Rabellino wrote:
Quick and nasty one... me feels a bit stupid now. Since in javascript
delete is a reserved keyword, how do I call a delete() function of a
java object? I know there must be a quick 'n easy solution out there,
but it's escaping my mind ATM.
javaObject[delete]
--
31 matches
Mail list logo