It doesn't look like it to me.
FYI - one workaround that I've used for this is to stick an Action right before the
serializer. The action gets passed the objectModel (which contains the request
object) and can therefore do the work you want.
e.g.:
DR
At 11:00 AM 12/12/01 +0100, you
ake a deeper look, will
do it tomorrwor.
Wait for More
Max
> -Original Message-
> From: Stephan Michels [mailto:[EMAIL PROTECTED]]
> Sent: Mittwoch, 12. Dezember 2001 12:02
> To: [EMAIL PROTECTED]
> Subject: RE: [Serializer] Get request and parameters?
>
>
>
>
&g
EMAIL PROTECTED]]
> > Sent: Mittwoch, 12. Dezember 2001 11:01
> > To: [EMAIL PROTECTED]
> > Subject: [Serializer] Get request and parameters?
> >
> >
> > Hi,
> > exists a way to get the request and the request parameters in a
> > serialzier? AbstractGen
( Constants.REQUEST_OBJECT ) );
response = (Response)(objectModel.get( Constants.RESPONSE_OBJECT ) );
}
> -Original Message-
> From: Stephan Michels [mailto:[EMAIL PROTECTED]]
> Sent: Mittwoch, 12. Dezember 2001 11:01
> To: [EMAIL PROTECTED]
> Subject: [Serializer] Get request
Hi,
exists a way to get the request and the request parameters in a
serialzier? AbstractGenerator and AbstractTransformer implements
the interface SitemapModelComponent. If I implement SitemapModelComponent
in my serializer it will ignored.
And SitemapOutputComponent doesn't implement a method li
