*@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
2. The only other option is for the upload library to set a more specific
the content type based on the file extension. Even in this case you would
need to formally identify the file server-side, since there is no guarantee
that this type is correct.
3. You'll have to provide more details, such
Dear Taha, Tapestry users,
I checked out the Ajax upload for tapestry, that Taha thankfully made it from
the file upload component.
http://tawus.wordpress.com/2011/06/25/ajax-upload-for-tapestry/
I have some problems with the component if anyone can help:
1. I have changed the code to fi
