With a request-object we have to pass only one object instead of a lot of
arguments.
This makes it a lot easier to maintain, because the method signature will
never change.
It's no problem to add new fields to the request.
The same counts for response-objects, when used.
Most request-object f
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
On 19 Feb 2013, at 18:08, Karl Heinz Marbaise wrote:
> Hi Robert,
> Hi Stuart,
>
> > InvocationRequest is not a Component, it is just an interface for
>> DefaultInvocationRequest.
>
> oh my lord... ;-(
>
> Thanks for enlighten me...
>
> Which means in other words to make the InvocationRequest
Hi Robert,
Hi Stuart,
> InvocationRequest is not a Component, it is just an interface for
DefaultInvocationRequest.
oh my lord... ;-(
Thanks for enlighten me...
Which means in other words to make the InvocationRequest being a
component it's missing simply this:
@Component( role = Invocati
On 19 Feb 2013, at 17:39, Karl Heinz Marbaise wrote:
> Hi,
>
> currently I'm working on a plugin which works so far so good...but now i
> stumbled over a problem which i didn't understand...
>
> I have a dependency to maven-invoker artifact:
>
>
>org.apache.maven.shared
>
InvocationRequest is not a Component, it is just an interface for
DefaultInvocationRequest.
Just use:
InvocationRequest request = new DefaultInvocationRequest();
Robert
Op Tue, 19 Feb 2013 18:39:45 +0100 schreef Karl Heinz Marbaise
:
Hi,
currently I'm working on a plugin which works so
Hi,
currently I'm working on a plugin which works so far so good...but now i
stumbled over a problem which i didn't understand...
I have a dependency to maven-invoker artifact:
org.apache.maven.shared
maven-invoker
2.1.1
I have the following annotations
