Hi Stuart,
> Setting aside the issue of whether DefaultInvocationRequest should
> really be a component, note that @Component by default defines
> a singleton component. You need to add:
instantiationStrategy = "per-lookup"
to get a new instance on every lookup, otherwise you'd always get the same
> instance which would be bad if two threads wanted to populate
> InvocationRequest at the same time.
That's a good hint....cause that would have caught me later with my idea
to make multiple threads running ...;-)
AFAIK InvocationRequest is just an abstraction to pass parameters, settings,
> environment etc. into the Invoker rather than
> something with identity/lifecycle.
Yes...but it would have made my life easier in my particular use
case...but this is no reason to change such a thing...which will work
only for a single use case.
Thanks a lot.
Kind regards
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
