Actually, no .. I cannot just use "JavascriptSupport.addScript"
everywhere I used to use "AjaxResponseRenderer.addCallback"
In XHR cases I get: UnknownValueException - "No object of type
org.apache.tapestry5.services.javascript.JavaScriptSupport is available
from the Environment."
I wonder w
Turned out this was because I was adding the script via
"ajaxResponseRenderer.addCallback" which used to be the recommended
approach.
JavascriptSupport now handles partial renders via "partialMode" (if you
look at the source).
Perhaps "ajaxResponseRenderer.addCallback" should be deprecated n
Hi Ben, a really basic example. I'm assuming your trying to loop the zones,
I hope this helps.
${product}
${cardTypes}
@Property
private CardType cardType;
@Property
private String cardTypes;
@InjectComponent
private Zone cardTypeZone;
private String produc
Hi Ben!
I am using the tapestry-jquery mixin for this:
tml:
t:validate="required" value="yourValue"
t:mixins="jquery/bind" bind.context="${yourValue.pk}"
bind.event="yourSelectionChanged" bind.eventType="change"/>
page:
public Object onYourSelectionChanged(final long pk)
{
Syste
I have a component that includes a zone - the zone is periodically
refreshed using the ZoneRefresh mixin.
Is there any equivalent to @BeginRender that I can use to set up data to
support the zone re-rendering? @BeginRender methods are called when the
page renders, but they're not called when the
After a lot of Googling around I'm unable to find a solution to my problem. I
want to handle the change event from a Select Component. I'm creating a bunch
of these components in a loop:
And I've got the following handler declaration:
@OnEvent(component="type", value = "change")
pub
Unfortunately, the bug in tapestry-cometd means that context.getCount()
will always be 0. I will need to fix this bug.
This is executing your redirect logic in the push event which is then
failing.
I'll try to get you a fix over the weekend. I've detailed the bug fix quite
thoroughly in the issue
Unfortunately, the bug in tapestry-cometd means that context.getCount()
will always be 0. I will need to fix this bug.
This is executing your redirect logic in the push event which is then
failing.
I'll try to get you a fix over the weekend. I've detailed the bug fix quite
thoroughly in the issue
the activate is somthing like:
Object onActivate(context)
{
if(context.count()>0)
do somthing
else
redirect to other page
}
my onchat method is unchanged from your demo project.
I'm now trying to add an eventlink to the list of users to make 1v1 chat
possible by changing t
I've created an issue here
https://github.com/uklance/tapestry-cometd/issues/55
Do you do any redirecting in your onActivate? (eg do you return another
page under some conditions).
Can you show me the (simplified) code that's firing for your push?
I think I might have spotted a bug, tapestry-cometd will always pass
EMPTY_EVENT_CONTEXT as the page activation context for push
I found that the problem accurs in the onActivate() function.
Our pages give information between eachotter trought the activationcontext.
Since it's a fake request it doesn't have this context, and or pages are
made that they redirect when the context is empty.
removing this check is not realy a
12 matches
Mail list logo
