Here is what I propose to move:
1) ImageReader
2) Paginator
3) JXTemplate*
anything else?
--
Stefano.
Miles Elam wrote:
Stefano Mazzocchi wrote:
on 5/27/03 4:19 PM Sylvain Wallez wrote:
How is this different from a resource? Resources also allow to define
overloaded generators and transformers. So do we really need a new
concept ?
...
Resources were supposed to be reusable pipelines,
Tony Collen wrote:
Hi everybody,
I've decided to unplug for a while.
...
http://manero.org/weblog/
David Crossley wrote, On 28/05/2003 2.22:
Thanks Tony, for all the excellent contributions that you
have made while you have been with us. Hope to see you back
again sometime. You are not alone
cziegeler2003/05/28 00:14:41
Modified:src/blocks/portal/samples/skins/common/styles header.xsl
tab.xsl
src/blocks/portal/samples sitemap.xmap
src/blocks/portal/java/org/apache/cocoon/portal/profile/impl
cziegeler2003/05/28 00:23:55
Modified:src/blocks/portal/java/org/apache/cocoon/portal/profile/impl
AuthenticationProfileManager.java
Log:
Cleaning up on logout
Revision ChangesPath
1.5 +11 -7
Marc Portier wrote, On 28/05/2003 8.38:
Miles Elam wrote:
...
What is the purpose of resources if this new syntax goes into effect
(which I like by the way)? What can a resource do that an overloaded
pipeline element cannot?
I think as Stefano said (slightly rephrased): it would deprecate the
Hello,
In our current site developed using a homegrown C++ framework,
we are able to provide customized webs or products, ie, the site can be
customized on
a page by page basis for specific customers (the custom web is denoted by an
additional component in the URL, so if the basic product is
We are investigating using Cocoon for our next generation product. The
internationalization stuff,
OK we can handle with the I18n Transformer. But what about the
customization? I'd like to start a discussion
for ideas on how to extend Cocoon to be able to do this in order
to come up
with a
On Tuesday, May 27, 2003, at 10:24 US/Pacific, Stefano Mazzocchi wrote:
on 5/27/03 1:44 AM Stefano Mazzocchi wrote:
Pier and I already stated a while back that our current implementation
of the FOM is weak and its design poor.
In the past, it was exactly such comments that made Ovidiu abandon
crossley2003/05/28 00:48:36
Modified:.forrest.properties
Log:
Exclude status.xml for validate.xdocs
Revision ChangesPath
1.12 +1 -1 cocoon-2.1/forrest.properties
Index: forrest.properties
Nicola Ken Barozzi wrote:
Marc Portier wrote, On 28/05/2003 8.38:
Miles Elam wrote:
...
What is the purpose of resources if this new syntax goes into effect
(which I like by the way)? What can a resource do that an overloaded
pipeline element cannot?
I think as Stefano said (slightly
On 28.May.2003 -- 09:25 AM, Nicola Ken Barozzi wrote:
Marc Portier wrote, On 28/05/2003 8.38:
Miles Elam wrote:
...
What is the purpose of resources if this new syntax goes into effect
(which I like by the way)? What can a resource do that an overloaded
pipeline element cannot?
I
From: Matthew Langham [mailto:[EMAIL PROTECTED]
We are investigating using Cocoon for our next generation
product. The
internationalization stuff,
OK we can handle with the I18n Transformer. But what about the
customization? I'd like to start a discussion
for ideas on how to extend
How about using something like the following pipeline matcher along with the
resource exists action
!-- assume that {1} is the customisation identifier, and the remainder is
the path --
map:match pattern=*/**.html
map:act type=resource-exists src=docs/{2}_{1}.html
-Original Message-
From: Geissel, Adrian [mailto:[EMAIL PROTECTED]
How about using something like the following pipeline matcher
along with the
resource exists action
[solution elided]
It also works well in for selecting stylesheets when combined with the
cocoon protocol in
Given something like [the reason if the generality is that it depends on
your site design]:
!-- re-inserted for completeness --
map:match pattern=*/**.html
map:act type=resource-exists src=docs/{2}_{1}.html
map:generate src=docs/{../2}_{../1}.html/
map:serialize
Le Mercredi, 28 mai 2003, à 09:28 Europe/Zurich, Mato Mira, Fernando a
écrit :
...There is a fallback mechanism whereby when the framework looks for
some
page foo the following search will be performed (say the user has
Spanish in
his preferences):
foo_hisproduct_sp.html
foo_hisproduct_en.html
Christian Haul wrote:
On 28.May.2003 -- 09:25 AM, Nicola Ken Barozzi wrote:
Marc Portier wrote, On 28/05/2003 8.38:
Miles Elam wrote:
...
What is the purpose of resources if this new syntax goes into effect
(which I like by the way)? What can a resource do that an overloaded
pipeline
On 28.May.2003 -- 12:51 PM, Marc Portier wrote:
Christian Haul wrote:
map:transformers
map:transformer logger=sitemap.transformer.encodeURL
name=encodeURL
src=org.apache.cocoon.transformation.EncodeURLTransformer/
map:transformer
I hit a redirection limit when I try to use your technique:
map:match pattern=*/**.html
map:act type=resource-exists src={2}_{1}.html
map:generate src={../2}_{../1}.html/
map:serialize type=xml/
/map:act
map:generate src={2}.html/
map:serialize
On Tuesday, May 27, 2003, at 07:21 PM, Stefano Mazzocchi wrote:
Resources were supposed to be reusable pipelines, but *complete* ones!
Later, they were implemented to be usable as pipeline fragments but,
IMO, they impose some readability problems in the sitemap. The above
aims to correct that.
In
Please ignore the previous post. Sorry.
--
Fernando D. Mato Mira [EMAIL PROTECTED]
-Original Message-
From: Mato Mira, Fernando [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 1:54 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Customization
I hit a redirection
+1 for the FOM as discussed for now.
Ok, this is a little bit OT, but I have to respond :)
Stefano Mazzocchi wrote:
map:serializer name=xhtml
map:transformer type=link-translation/
map:serializer type=xhtml/
map:serializer
map:match pattern=...
map:generate src=.../
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=20296.
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=20296.
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=20296.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
Unsure of the content of your login.xhtml file - check that it is well
formed.
On comment - I tend to use the 'defaulting' matcher in an internal-only
pipeline and always get it to return XML (ie map:serialize/@type='xml' ),
and then the puplic matcher has a generate/serialize pair, rather
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=20296.
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=20296.
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=20296.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Stefano Mazzocchi wrote:
Here is what I propose to move:
1) ImageReader
2) Paginator
3) JXTemplate*
+1
anything else?
Do we have any policy when to blast things from the scratchpad,
I mean, when something is in there for ages and noone maintains it
or uses it, it is pretty useless.
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=20296.
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=20296.
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=20297.
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=20297.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
-Original Message-
From: Geissel, Adrian [mailto:[EMAIL PROTECTED]
Unsure of the content of your login.xhtml file - check that it is well
formed.
It looks well-formed (see below).
What happens if you call-up content/login.xhtml from your
browser (ie. go
straight to the first
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=20298.
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=20298.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
From: Geissel, Adrian [mailto:[EMAIL PROTECTED]
On comment - I tend to use the 'defaulting' matcher in an
internal-only
pipeline and always get it to return XML (ie
map:serialize/@type='xml' ),
and then the puplic matcher has a generate/serialize pair,
rather than a
reader.
It works
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=20299.
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=20299.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
41 matches
Mail list logo
