Giacomo Pati wrote:
>
> On Thu, 3 Jan 2002, Carsten Ziegeler wrote:
>
> > John Morrison wrote:
> > >
> > > > -----Original Message-----
> > > > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
> > > > Sent: Thursday, 03 January 2002 12:32 pm
> > > > To: Cocoon-Dev
> > > > Subject: Allowed Sitemap Constructs
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I currently run into the problem that I created pipelines which I
> > > > thought were possible, but currently are not support by Cocoon:
> > > >
> > > > It is not possible to nest anything other than a map:part into
> > > > a map:aggregate, so the following doesn't work:
> > > > <map:aggregate>
> > > >   <map:select type="test">
> > > >     <map:when test="a">
> > > >       <map:part src="a"/>
> > > >     </map:when>
> > > >     <map:otherwise>
> > > >       <map:part src="b"/>
> > > >     </map:otherwise>
> > > >   </map:select>
> > > >   <map:part src="constant"/>
> > > > </map:aggregate>
> > > >
> > > > Is this a bug or is this by design?
> > > > My personal opinion is, that this should be possible.
> > > >
> > > > Another restriction we currently have is already entered as
> a bug with
> > > > the number 4357: An Action is not possible as a root element inside
> > > > a map:pipeline, only map:match can be a used as a root element.
> > > > So here again, is this by design?
> > >
> > > What would you expect the Action to do and when would you
> expect it to do
> > > it?
> > >
> > For example:
> > <map:pipeline>
> >   <map:act type="LogStatus"/>
> >
> >   <map:act type="ProtectAllResource">
> >
> >     <map:match pattern="docs/*">
> >      ..
> >     </map:match>
> >   </map:act>
> >
> > </map:pipeline>
> >
> > So the actions are invoked immediately at the start of the sitemap
> > processing,
> > for example for any debugging or authentication or initialization of the
> > object
> > model etc.
>
> You know I don't like "initialization of the object model" (as long as
> you mean the objectModel object ;)
>
Yes - sigh - I know! But fortunately it's still there to be used in this
way...
I really fear the day when it will be read only!

Carsten


> Giacomo
>
> >
> > Carsten
> >
> > > > I think we shouldn't make such restrictions. But at least if we make
> > > > these restrictions we should document them.
> > > >
> > > > Regards,
> > > > Carsten
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, email: [EMAIL PROTECTED]
> > > >
> > >
> > >
> > >
> =======================================================================
> > > Information in this email and any attachments are
> confidential, and may
> > > not be copied or used by anyone other than the addressee, nor
> disclosed
> > > to any third party without our permission.  There is no intention to
> > > create any legally binding contract or other commitment
> through the use
> > > of this email.
> > >
> > > Experian Limited (registration number 653331).
> > > Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, email: [EMAIL PROTECTED]
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to