le what if
UnclaimedField goes away.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Ioc-Ordering-Contraints-tp5716154p5716174.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscri
runtime, and the growth of the framework over time.
>
> On Mon, Sep 10, 2012 at 9:03 AM, trsvax wrote:
>> I'd try creating a dummy worker called beforeUnclaimedField and make it
>>
>> before:UnclaimedField
>>
>> then change yours to
>>
>> after:b
time, and the growth of the framework over time.
On Mon, Sep 10, 2012 at 9:03 AM, trsvax wrote:
> I'd try creating a dummy worker called beforeUnclaimedField and make it
>
> before:UnclaimedField
>
> then change yours to
>
> after:beforeUnclaimedField
>
>
&
I'd try creating a dummy worker called beforeUnclaimedField and make it
before:UnclaimedField
then change yours to
after:beforeUnclaimedField
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Ioc-Ordering-Contraints-tp5716154p5716171.html
Sent from the Tap
> I think you are looking for the "ultimate solution" here that doesn't exist.
Yeah, maybe. Sigh. :`(
I guess I was jus' hoping I'd overlooked something.
Nevermind, I'll live! :)
Cheers to all for the suggestions.
Steve.
On 10 September 2012 23:27, Lenny Primak wrote:
> Hey, Steve,
>
> I thi
Hey, Steve,
I think you are looking for the "ultimate solution" here that doesn't exist.
I don't think you can make it work in all cases and all configurations.
I think you need to find the last service that's really there and the one you
need to be after, and put that in the constraints.
Sin
Hi Robert,
I had previously tried "before:UnclaimedField", "after:*" - but
doesn't matter which way round the constraints go, I still get:
Unable to add 'ContextNotRequiredWorker' as a dependency of
'UnclaimedField', as that forms a dependency cycle ('UnclaimedField'
depends on itself via 'Contex
Hi Steve, have you tried specifying "after:*", "before:UnclaimedField"?
Robert
On Sep 9, 2012, at 9/99:33 PM , Steve Eynon wrote:
> Hi Michael,
>
>> just specify as many as are important to you.
>
> I kinda want mine to run last, because I need make sure no other
> workers (in T5 or other mod
be more specific ;)
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Ioc-Ordering-Contraints-tp5716154p5716159.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsub
*@Michael*
Constraints are very loose; after means 'somewhere after' rather than
> 'immediately after'
If that was the case, why did cause an issue if it was so loose ? Is this
one special case (i.e. after:***) ?
What's the advantage of having this behavior over having it strict as being
*immedi
Hi Michael,
> just specify as many as are important to you.
I kinda want mine to run last, because I need make sure no other
workers (in T5 or other modules) add a onActivate() method. The issue
here is that both my 'ContextNotRequiredWorker' and T5's
'UnclaimedField' want to run last - which isn
Apparently, the trick is to specify multiple constraints. Constraints are
very loose; after means 'somewhere after' rather than 'immediately after',
so just specify as many as are important to you.
Someone more informed can weigh in whether you can mix specific constraints
with wildcards. In the
Hi,
I have a transform worker which I want to run after everything else (it
checks for the existence of an onActive() method) so I have the
following Module method, note the "after:*"
@Contribute(ComponentClassTransformWorker2.class)
@Primary
public static void provideTransformWorkers(
Orde
13 matches
Mail list logo
