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=26657.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Conal Tuohy wrote:
Jorg and Joerg wrote:
Dutch | German | English
ik | ich | I
kan | kann | can
mijn| mein | my
pdf | pdf | pdf
niet| nicht| not
openen | öffnen | open
kunt| kannst | can
u | du
Geoff Howard wrote:
Joerg Heinicke wrote:
On 02.02.2004 22:00, Tim Larson wrote:
BTW, I think there should be a check in each binding to make sure
the widget is of the required type. Perhaps JXPathBindingBase
should supply a method that the bindings could call to perform this
check?
Hi,
I'm trying to get my project set up in the above environment. I notice
cocoon uses Ant 1.6 (with import). I try to follow the info in Cocoon Wiki
YourCocoonBasedProject while trying to copy and paste from the Cocoon build
files.
I now run into trouble: I can't get Ant to find any of the
[EMAIL PROTECTED] wrote:
@@ -143,8 +137,57 @@
logger=sitemap.reader.resource
pool-max=32 pool-min=1 pool-grow=4/
!-- optional reader configuration --
-map:parameter name=expires value=8640/
+parameter name=expires value=8640/
/map:readers
Why not
Carrying the discussion over from users@
Why is variable substituion not allowed in @type attributes ?
(or: is there a better way to translate below pseudo-syntax into real
syntax?)
Imagine Tuomo's usecase a bit more extended
map:match pattern=*.*
map:generate src={1}.{2}/
Vadim Gritsenko wrote:
[EMAIL PROTECTED] wrote:
@@ -143,8 +137,57 @@
logger=sitemap.reader.resource
pool-max=32 pool-min=1 pool-grow=4/
!-- optional reader configuration --
-map:parameter name=expires value=8640/
+parameter name=expires
This was discussed several times, please have a look in the archives.
HTH
Carsten
-Original Message-
From: news [mailto:[EMAIL PROTECTED] Behalf Of Jorg Heymans
Sent: Wednesday, February 04, 2004 3:11 PM
To: [EMAIL PROTECTED]
Subject: variable substitution in @type attributes
Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
[EMAIL PROTECTED] wrote:
@@ -143,8 +137,57 @@
logger=sitemap.reader.resource
pool-max=32 pool-min=1 pool-grow=4/
!-- optional reader configuration --
-map:parameter name=expires value=8640/
+parameter name=expires
Vadim Gritsenko wrote:
Why not map:parameter here for consistency sake, like in:
map:matcher name=mount-table
src=org.apache.cocoon.matching.MountTableMatcher
map:parameter name=ignore-missing-tables value=true/
/map:matcher
This would be the first component that
Vadim, that post is from 2001.
The arguments are:
- it affects the cache -is this still relevant for the rewritten cache
mechanism in 2.1+ ?
- Flexibility syndrome -point taken
- It's a reactor pattern forcing distribution of control and increasing
the number of contracts between the different
True, this is a big security hole...
Well, for the exception, where is the difference btw calling a non existant
component and calling a non existant resource (like a file)??
But it seems hard use... At the same time, this'd be cool for readers (like
gif, jpeg,etc..)
What do you think?
Le
From: Nicolas Toper [mailto:[EMAIL PROTECTED]
True, this is a big security hole...
Well, for the exception, where is the difference btw calling
a non existant
component and calling a non existant resource (like a file)??
But it seems hard use... At the same time, this'd be cool for
Jorg Heymans wrote:
Vadim, that post is from 2001.
Well, it shows how solid our contracts are :-)
The arguments are:
- it affects the cache -is this still relevant for the rewritten
cache mechanism in 2.1+ ?
Not relevant, I'd think.
- Flexibility syndrome -point taken
- It's a reactor
Carsten Ziegeler wrote:
I think one major point is security or more precise: to detect possible
problems
early on. If you now use a wrong type information, which means address a
component that doesn't exist, you get an exception immediately on startup.
So, you know very early that your
Could you give a use case of this functionnality?
I'm curious to know how it could be useful compared to how it'll make the
sitemap unreadable?
Nicolas
Le Mercredi 04 Février 2004 16:18, Jorg Heymans a écrit :
Carsten Ziegeler wrote:
I think one major point is security or more precise: to
I'm curious to know how it could be useful compared to how it'll make the
sitemap unreadable?
map:match pattern=*.*
map:generate src={1}.{2}/
map:transform type={2}/
map:serialize type={2}/
/map:match
is less readable because you don't know which component is executed in
advance. From the
Tim Larson Escribio :-)
On Sat, Jan 31, 2004 at 06:41:49PM -0600, Antonio Gallardo wrote:
Hi again :-D
In another place we have a binding problem:
wb:context path=cuentaInventario
wb:value id=prod_id_inventario path=prod_id/
wb:value id=cc_id_inventario path=cc_id/
/wb:context
Carsten Ziegeler wrote:
I think one major point is security or more precise: to detect possible problems early on. If you now use a wrong type information, which means address a component that doesn't exist, you get an exception immediately on startup. So, you know very early that your
Happy birthday Ugo!
/Steven
--
Steven Noelshttp://outerthought.org/
Outerthought - Open Source Java XMLAn Orixo Member
Read my weblog athttp://blogs.cocoondev.org/stevenn/
stevenn at outerthought.orgstevenn at apache.org
Moreover, the use case shows a component type coming directly for the
request URI, which is a giant door open to component injection by
providing a value for the type that is not in the expected values and
executes arbitrary code on the server.
Wooo hold on here, what you just described sounds
Vadim Gritsenko wrote:
Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
[EMAIL PROTECTED] wrote:
@@ -143,8 +137,57 @@
logger=sitemap.reader.resource pool-max=32
pool-min=1 pool-grow=4/
!-- optional reader configuration --
-map:parameter name=expires value=8640/
+
Olivier Billard wrote:
On 04/02/2004 12:37, Vadim Gritsenko wrote:
Olivier Billard wrote:
Hi cocooners ! (again)
Is there a way to show the content at time t of objects pools ?
By debug traces ? a special-secret-powerfull-tool ;) ?
There is some secret super-powerful tool... Name is
Steven Noels wrote:
Happy birthday Ugo!
This isn't so silly, as it shows the friendlyness of this community, and
it happens that we're known for that (see the last comment in [1])
Happy Birthday!!!
BTW, we missed a lot of them in January...
Sylvain
[1]
This sounds interesting. However, isn't 2.2 dumping excalibur in favor of
fortress? (Just my impression from some of the emails here). Does fortress
have something similar?
Ralph
-Original Message-
From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 04, 2004 3:37
Jorg Heymans wrote:
Moreover, the use case shows a component type coming directly for the
request URI, which is a giant door open to component injection by
providing a value for the type that is not in the expected values and
executes arbitrary code on the server.
Wooo hold on here, what you
There is some secret super-powerful tool... Name is
excalibur-instrument-manager, and when instrumentation enabled, you can
launch some GUI app to see what's happening. I've not used it yet;
archives should have mentionings of it.
Any pointers on how to use it?
Thx!
Andrzej Jan Taramina
Yes that's how you can hack a lot of PHP servers (yes I was young ;=))
Le Mercredi 04 Février 2004 17:11, Sylvain Wallez a écrit :
Jorg Heymans wrote:
Moreover, the use case shows a component type coming directly for the
request URI, which is a giant door open to component injection by
Ralph Goers wrote:
This sounds interesting. However, isn't 2.2 dumping excalibur in favor of
fortress? (Just my impression from some of the emails here). Does fortress
have something similar?
Confusing project names. 2.2 uses Fortress to replace Excalibur
Component Manager (ECM). However,
That's not unlikely and doesn't require uploading classes. Consider the
following:
map:match pattern=*-*.html
map:generate src=repository/{1}.xml type=file/
map:transform type={2}/
map:serialize type=html/
/map:match
Now suppose we're in a CMS and that the user can upload the initial xml
Ralph Goers wrote:
This sounds interesting. However, isn't 2.2 dumping excalibur in favor of
fortress? (Just my impression from some of the emails here). Does fortress
have something similar?
Yes, of cource!
--
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business
Andrzej Jan Taramina wrote:
There is some secret super-powerful tool... Name is
excalibur-instrument-manager, and when instrumentation enabled, you can
launch some GUI app to see what's happening. I've not used it yet;
archives should have mentionings of it.
Any pointers on how to use it?
Hi peeps,
I finally managed to finish the new style of validation we discussed a
while ago.
This new validation allows *any* widget to have a validator. The
immediate effect is that wd:validator is now outside of wd:datatype
since not all widgets have a datatype.
The validator interface has
Hello Sylvain,
having additional start scripts is not nice IMO. Therefore I removed
some time ago the bin/runclient.bat and .sh for the instrumentation
client
(http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/tools/instrumentation/bin/Attic/)
and added a target start-instrumentation-client into a
Geoff Howard wrote:
Ralph Goers wrote:
This sounds interesting. However, isn't 2.2 dumping excalibur in favor of
fortress? (Just my impression from some of the emails here). Does
fortress
have something similar?
Confusing project names. 2.2 uses Fortress to replace Excalibur
Component
Joerg Heinicke wrote:
Hello Sylvain,
having additional start scripts is not nice IMO. Therefore I removed
some time ago the bin/runclient.bat and .sh for the instrumentation
client
(http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/tools/instrumentation/bin/Attic/)
and added a target
On 04.02.2004 15:18, [EMAIL PROTECTED] wrote:
Modified:src/blocks/ojb/samples/woody employee.js
Log:
fixed line endings issue
Revision ChangesPath
1.7 +32 -32cocoon-2.1/src/blocks/ojb/samples/woody/employee.js
This file was broken in that way that I had unix line
Does this mean we can now reference images using all Cocoon protocols? I
mean also for fo:external-graphic src=/ and similar?
On 04.02.2004 15:39, [EMAIL PROTECTED] wrote:
sylvain 2004/02/04 06:39:58
Modified:src/blocks/fop/java/org/apache/cocoon/serialization
On 04.02.2004 19:21, Sylvain Wallez wrote:
Hello Sylvain,
having additional start scripts is not nice IMO. Therefore I removed
some time ago the bin/runclient.bat and .sh for the instrumentation
client
(http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/tools/instrumentation/bin/Attic/)
and added
Tim Larson wrote:
I did a cvs up -d in cocoon-2.1 on January 28, followed by a
build clean and build. When I tried to run this with a full
installation of Jetty (4.2.11) it produced Address already in use
errors. It had been working fine for several months before this.
After an upgrade to Jetty
40 matches
Mail list logo
