cvs commit: cocoon-2.1/src/blocks/portal/conf actions.xmap

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 Authent

cvs commit: cocoon-2.1/src/blocks/portal/java/org/apache/cocoon/portal/profile/impl AuthenticationProfileManager.java

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 cocoon-2.1/src/blocks/portal/java/org/apache/

Re: Overloaded pipeline elements (Was Re: [RT] FOM)

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 u

Customization

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

RE: Customization

> 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 > w

Re: [RT] FOM

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 thi

cvs commit: cocoon-2.1 forrest.properties

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 ===

Re: Overloaded pipeline elements (Was Re: [RT] FOM)

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 rephra

Re: Overloaded pipeline elements (Was Re: [RT] FOM)

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 ca

RE: Customization

> 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

RE: Customization

How about using something like the following pipeline matcher along with the resource exists action I use this a lot, and it works quite well. It also works well in for selecting stylesheets when combined with the cocoon protocol in map:tran

RE: Customization

> -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 protoc

RE: Customization

Given something like [the reason if the generality is that it depends on your site design]: requesting http://my.server:8080/cocoon/apache/overview.html will first test whether the resource docs/apache/overview_cocoon.html exists,

Re: Customization (ResourceSelectorAction?)

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

Re: Overloaded pipeline elements (Was Re: [RT] FOM)

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 elemen

Re: Overloaded pipeline elements (Was Re: [RT] FOM)

On 28.May.2003 -- 12:51 PM, Marc Portier wrote: > Christian Haul wrote: > > > > > name="encodeURL" > > src="org.apache.cocoon.transformation.EncodeURLTransformer"/> > > > name="renderForBrowser" > > > > src

RE: Customization

I hit a redirection limit when I try to use your technique:

Re: [RT] FOM

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 f

RE: Customization

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 redir

RE: Customization

OK. The previous was bogus. But now I get a real error with: This doesn't work: It gives an XML Parsing Error: mismatched tag. Expected: when it reaches the tag of the file. The same file works here:

RE: [RT] FOM

+1 for the FOM as discussed for now. Ok, this is a little bit OT, but I have to respond :) Stefano Mazzocchi wrote: > > > > > > > > > > > > I think this is a very useful concept. Do you remember our discussion from two years ago about adding url rewriting to the html ser

DO NOT REPLY [Bug 20296] New: - [PATCH] Modularized DirectoryGenerator's

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20296] - [PATCH] Modularized DirectoryGenerator's

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20296] - [PATCH] Modularized DirectoryGenerator's

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Customization

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 th

DO NOT REPLY [Bug 20296] - [PATCH] Modularized DirectoryGenerator's

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20296] - [PATCH] Modularized DirectoryGenerator's

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20296] - [PATCH] Modularized DirectoryGenerator's

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: [proposal] move stuff from scratchpad into the trunk

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 usel

DO NOT REPLY [Bug 20296] - [PATCH] Modularized DirectoryGenerator's

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20296] - [PATCH] Modularized DirectoryGenerator's

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20297] New: - [PATCH] Added RequestURI in addition to SitemapURI to BaseLinkModule

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20297] - [PATCH] Added RequestURI in addition to SitemapURI to BaseLinkModule

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Customization

> -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 fir

DO NOT REPLY [Bug 20298] New: - [PATCH] ExtendedXLinkPipe support for multiple XLinks per element

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20298] - [PATCH] ExtendedXLinkPipe support for multiple XLinks per element

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Customization

> 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

DO NOT REPLY [Bug 20299] New: - [PATCH] text/javascript and text/vbscript for MimeUtils

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20299] - [PATCH] text/javascript and text/vbscript for MimeUtils

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20185] - [PATCH] TidySerializer

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: [proposal] move stuff from scratchpad into the trunk

FlowVelocityGenerator to replace VelocityGenerator Stefano Mazzocchi wrote: Here is what I propose to move: 1) ImageReader 2) Paginator 3) JXTemplate* anything else?

Re: [proposal] move stuff from scratchpad into the trunk

Christopher Oliver wrote: FlowVelocityGenerator to replace VelocityGenerator -1 to replacing: FlowVelocityGenerator introduces dependencies on org.apache.commons.jxpath and org.mozilla.javascript which where missing in original VelocityGenerator. Also, does it support functionality which is

RE: Customization

I am trying to set a session variable to the value of a match variable (the customization name) and I am finding some difficulties: 1. There's no way to set a session variable from the sitemap. So I use XSP instead of a raw XHTML to set the variable there. I now need to pass a parameter to the XS

cvs commit: cocoon-2.1/src/blocks/portal/java/org/apache/cocoon/portal/impl DefaultLinkService.java

cziegeler2003/05/28 06:47:30 Modified:src/blocks/portal/java/org/apache/cocoon/portal/event/aspect/impl FrameEventAspect.java RequestParameterEventAspect.java src/blocks/portal/java/org/apache/cocoon/portal/coplet/adapter

Re: [proposal] move stuff from scratchpad into the trunk

Vadim Gritsenko wrote: Christopher Oliver wrote: FlowVelocityGenerator to replace VelocityGenerator -1 to replacing: FlowVelocityGenerator introduces dependencies on org.apache.commons.jxpath and org.mozilla.javascript which where missing in original VelocityGenerator. Why is that a problem?