> > > Context is one per application, Configuration and Parameters
> > > are one per
> > > Source type (in your case - one configuration per all instances of
> > > MailSource).
> > Just to get this clear though - if my Source was a
> Generator instead,
> could
> > I pass parameters to it on a per-pipeline basis, just by
> implementing
> > Parameterizable?
>
> Yes.
>
> Vadim
OK. But why CAN'T I do this with a Source? [Thinking aloud] The Generator is
the container for my Source isn't it? Presumably the Generator should
Parameterize my Source when it resolves it (or Reparameterize it), so
couldn't my Source access the parameters passed to the Generator, in the
example below? Perhaps the parameter names should be "mail:username" and
"mail:password" so they don't clash with parameters the Generator might be
expecting.
> > e.g.
> >
> > <map:match pattern="mail/*/*/*">
> > <map:generate type="mail" src="{1}">
> > <map:parameter name="username" value="{2}">
> > <map:parameter name="password" value="{3}">
> > </map:generate>
> > etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
