I can only think about 2 different requests after reading your question but
I really think this can be done using one event. I suggest you fire a third
event that triggers your 2 existing event handlers as normal java methods.
I assume only one of the existing methods could be returning something.
I want to use tapestry-service-cache (
https://github.com/ciaranw/tapestry-service-cache ) ,but it has a bug
with tapestry 5.3.*
In tapestry 5.3.* ,ServiceResources. getImplementationClass(), just return
null;
but in class
com.ciaranwood.tapestry.cache.services.advice.CacheMethodDecoratorImpl ,is
I get ComponentException and InternalOperationException. I deem possible
reason for such a matter may be found in trigerring two events, and Tap is
confused which one should deal with first, so is there anything that could
prevent or direct such behavior? What should I do?
--
View this message i
It would be nice just to have some documented "markers". I usually just look
at the TapestryModule class to figure out what to do, but having some
documented phases would probably solve most issues. It would also solve the
problem workers changing between releases. For example what if
UnclaimedFiel
Would be nice it we could get a printout of services within their constrains
somehow. Is there any way to do that presently?
On Sep 10, 2012, at 4:09 PM, Howard Lewis Ship wrote:
> One thing I have considered in the past is to be able to define
> "phases" for an ordered configuration, and pla
One thing I have considered in the past is to be able to define
"phases" for an ordered configuration, and place contributions within
a phase, but also ordered relative to other contributions in that
phase. Thus the service author would define (and document) a few
phases, and contributions would g
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 Tapestry - User
> 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
should have been
cell text
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Dynamically-Writing-Raw-to-Grid-Cells-tp5716164p5716169.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
I think you could create a "raw" datatype. Then in your bean
@Datatype("raw")
private String rawData;
Then create a property display block
but it seems like what you really want is
CellText
If that's the case I'd add a mixin to GridGell and write out the span tag.
GridCell has acce
You could always attach a custom mixin to the DataTable which decorates the
DOM.
http://tapestry.apache.org/component-mixins.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Dynamically-Writing-Raw-to-Grid-Cells-tp5716164p5716167.html
Sent from the Tapestry - User mai
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
Hello,
I've had a search around and yet to find a potential solution to this.
Beginning to think it may be impossible currently!
The problem:
I'm using a variation of a Grid (specifically, Tapestry5 jQuery's DataTable
which springboards off AbstractTable and DataTables.net for client-side).
I'm
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
I tried that sample. It's working. Thanks lot
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Using-a-own-component-in-different-places-and-using-a-specific-data-in-that-component-tp5716161p5716163.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
--
Pass a boolean component parameter
http://tapestry.apache.org/component-parameters.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Using-a-own-component-in-different-places-and-using-a-specific-data-in-that-component-tp5716161p5716162.html
Sent from the Tapestry - Us
Hi,
I have my own component called header.
I have designed that component with right side combo drop down and left side
logo.
I am invoke that header component in two tml pages(A,B). I want to display
both logo and drop down in page A and i want to display only logo without
combo drop down in
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
Tapestry's ordered constraints need to be like this to allow distributed
configuration. If two contributions specify "after:X", tapestry will make
sure that they both occur after X. Since it's impossible to order both
directly after X, tapestry will (pseudo randomly) decide an ordering which
is not
This should be possible but you won't be able @Symbol and you will need to
reference specific symbol providers (by name or annotation).
eg:
// FactoryDefaults are resolved before application defaults
public void contributeFactoryDefaults(MappedConfiguration
config) {
config.add("mySymbol1", "f
20 matches
Mail list logo
