Sylvain Wallez wrote:
_Silently_ whistling? You'll have to teach me this
interesting technique ;-)
No problem, I can tell you how to do it after the fifth (or so) beer at
the next gt.
Hey folks, look at who went in the way of my refactoring:
Sylvain Wallez wrote:
Carsten,
I noticed you added support for sitemap language versionning
in the TreeProcessor a few weeks ago. What's the purpose of this?
Actually, it's a feature we wanted to use for 2.1 already... A long time
ago, we agreed that if we change the sitemap syntax, we
Carsten Ziegeler wrote:
A long time
ago, we agreed that if we change the sitemap syntax, we will
change the
version number of the sitemap namespace.
Is it really necessary to change the xml namespace? How does this help
developers?
If it's just a matter of being able to identify the version
I want to start the implementation of the virtual sitemap components
in the next weeks; but before, we should discuss how they will look like :)
The first point - and imho most important point is, of which components
a virtual sitemap component (VSC) can be assembled.
My understand is that a VSC
Carsten Ziegeler dijo:
I want to start the implementation of the virtual sitemap components
in the next weeks; but before, we should discuss how they will look like
:)
The first point - and imho most important point is, of which components
a virtual sitemap component (VSC) can be assembled.
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Carsten,
I noticed you added support for sitemap language versionning
in the TreeProcessor a few weeks ago. What's the purpose of this?
Actually, it's a feature we wanted to use for 2.1 already... A long time
ago, we agreed that if we change
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Carsten,
I noticed you added support for sitemap language versionning in the
TreeProcessor a few weeks ago. What's the purpose of this?
Actually, it's a feature we wanted to use for 2.1 already... A
Carsten Ziegeler wrote:
There were some mentions in the past, that a VSC can contain any sitemap
component, so even actions, matchers and selectors are allowed in
the definition of the VSC.
So, first question is: do we want this?
(I would say: no)
I am inclined to agree with you, even if I didn't
Carsten Ziegeler wrote:
I want to start the implementation of the virtual sitemap components
in the next weeks; but before, we should discuss how they will look like :)
The first point - and imho most important point is, of which components
a virtual sitemap component (VSC) can be assembled.
My
Ugo Cei wrote:
Carsten Ziegeler wrote:
There were some mentions in the past, that a VSC can contain any
sitemap component, so even actions, matchers and selectors
are allowed
in the definition of the VSC.
So, first question is: do we want this?
(I would say: no)
I am
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Carsten,
I noticed you added support for sitemap language versionning in the
TreeProcessor a few weeks ago. What's the purpose of this?
Actually, it's a feature we wanted to use for
Carsten Ziegeler wrote:
I want to start the implementation of the virtual sitemap components
in the next weeks; but before, we should discuss how they will look like :)
The first point - and imho most important point is, of which components
a virtual sitemap component (VSC) can be assembled.
My
Sylvain Wallez wrote:
Well, it would have been easy for us to allow it, simply by
defining builtin default values for map:pipes. I can't
remember of any other needed modifications.
We removed/deprecated a redirect to resources I think as well.
SNIP
Okay. So we should decide on how
Andreas Hartmann wrote:
Carsten Ziegeler wrote:
I want to start the implementation of the virtual sitemap components
in the next weeks; but before, we should discuss how they will look
like :)
The first point - and imho most important point is, of which components
a virtual sitemap component
Carsten Ziegeler [EMAIL PROTECTED] writes:
I want to start the implementation of the virtual sitemap components
in the next weeks; but before, we should discuss how they will look like :)
The first point - and imho most important point is, of which components
a virtual sitemap component
Colin Paul Adams wrote:
But when I try the various mirrors at
http://excalibur.apache.org/download.cgi,
none of them seem to have the source to the excalibur-sourceresolve
product (or anything else, it seems).
Can anyone suggest anything, please?
Ugo == Ugo Cei [EMAIL PROTECTED] writes:
Ugo Colin Paul Adams wrote:
But when I try the various mirrors at
http://excalibur.apache.org/download.cgi, none of them seem to
have the source to the excalibur-sourceresolve product (or
anything else, it seems). Can anyone
Colin Paul Adams wrote:
Ugo == Ugo Cei [EMAIL PROTECTED] writes:
Ugo Colin Paul Adams wrote:
But when I try the various mirrors at
http://excalibur.apache.org/download.cgi, none of them seem to
have the source to the excalibur-sourceresolve product (or
anything else, it
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
There were some mentions in the past, that a VSC can contain any sitemap
component, so even actions, matchers and selectors are allowed in
the definition of the VSC.
So, first question is: do we want this?
(I would say: no)
I would say yes!
There were some mentions in the past, that a VSC can contain any sitemap
component, so even actions, matchers and selectors are allowed in
the definition of the VSC.
So, first question is: do we want this?
(I would say: no)
I would say yes! Forbidding control structures in virtual components
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30148.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Carsten Ziegeler wrote:
Ok. So I'll continue that way, which means removing your configuration merging stuff in favor of separate config files. Note that the size of these files has been largely reduced since they no more contain role definitions.
Go ahead.
Done!
The TreeBuilder is now a
Ralph Goers wrote:
I must admit, I am completely confused. The question was posed
earlier as to what the difference between virtual sitemap components
and resources are, to which I haven't seen an answer.
It would seem that they are close enough conceptually that having both
of them is just
Sylvain Wallez wrote:
Ralph Goers wrote:
I must admit, I am completely confused. The question was posed
earlier as to what the difference between virtual sitemap components
and resources are, to which I haven't seen an answer.
It would seem that they are close enough conceptually that having
Marc Portier wrote:
Sylvain Wallez wrote:
Ralph Goers wrote:
I must admit, I am completely confused. The question was posed
earlier as to what the difference between virtual sitemap components
and resources are, to which I haven't seen an answer.
It would seem that they are close enough
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
I want to start the implementation of the virtual sitemap components
in the next weeks; but before, we should discuss how they will look
like :)
The first point - and imho most important point is, of which components
a virtual sitemap component (VSC)
I would say yes! Forbidding control structures in virtual components
would greatly reduce their usefulness.
i agree with you, but do you think it makes sense to use everything? I
would say that just selection and action would be useful, but matching
and redirection would be harmful.
thoughts?
Stefano Mazzocchi [EMAIL PROTECTED] writes:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
I want to start the implementation of the virtual sitemap
components
in the next weeks; but before, we should discuss how they
will look
like :)
The first point - and imho most
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
There were some mentions in the past, that a VSC can contain any
sitemap
component, so even actions, matchers and selectors are allowed in
the definition of the VSC.
So, first question is: do we want this?
(I would say: no)
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
I want to start the implementation of the virtual sitemap components
in the next weeks; but before, we should discuss how they will look
like :)
The first point - and imho most important point is, of which components
a
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
snip /
There were some mentions in the past, that a VSC can contain any
sitemap
component, so even actions, matchers and selectors are allowed in
the definition of the VSC.
So, first question is: do we
Sylvain Wallez wrote:
So, to sum up:
+1 for map:match, map:select and map:call resource
-1 for map:act, map:redirect-to and map:call function and
map:call continuation
makes sense, +1
We also have to define how views behave with virtual components, and I
admit not to have a clear idea on this
32 matches
Mail list logo
