Hi all,
I have a question regarding Dynamic component. I use it for keeping parts of
tml code in the database. It renders insertions used for functions calling such
us ${someFunc('someParam')} , but it does not render any tapestry tags
correctly. It just omits "t" prefix instead and adds xmlns
Do you have a stack trace? And you are sure you are just not deploying a
servlet api with you war? In the simplest (to correct) case we are using
some 3.0 features but off-hand I don't remember any and they are relatively
easily to code around. 3.0 api is already 5 years old but it might be worth
s
Hi Kalle, (& y'all)
I see your tapestry-security 0.6.0 has a dependency on the v3.0 servlet
spec.
I know 0.5.1 had it too, because I have an app running with it in a v3
servlet container that works fine and dandy.
I am trying to work tapestry-security 0.6.0 into another app that's in
production o
Brilliant at least we figured out the issue here :)
Any eta on the fix? I would be happy to test the fix :)
On Sun, Sep 14, 2014 at 11:49 PM, Lance Java
wrote:
> Yes, looks like a bug. I assumed the ArrayEventContext would it's
> TypeCoercer reference to do the type coercion. Seems I was wrong.
Yes, looks like a bug. I assumed the ArrayEventContext would it's
TypeCoercer reference to do the type coercion. Seems I was wrong.
The workaround for now is to convert from string yourself.
On 14 Sep 2014 22:17, "Boris Horvat" wrote:
> You are right, the implementation is different between the
You are right, the implementation is different between the two cases.
- eventContext =
{org.apache.tapestry5.internal.*URLEventContext*@10311}"EventContext:
null"
- valueEncoder = {$ContextValueEncoder_9660c5cdf431@10618}""
- values = {java.lang.String[1]@10619}
- values =
Hmm... Perhaps this is a bug in the way tapestry-cometd fires the
onActivate.
Can you fire up a debugger and inspect the EventContext object passed to
onActivate() in
1. the normal page render
2. the tapestry-cometd component
I think there's something preventing type coercion (which passes throug
True the form is not ajax, do you think it would help if it was?
But even if the PushTarget is triggered with the old data I dont get why
the exception is thrown. I would understand if it loads wrong object...but
not to get coercion exception, right?
What would be the best way to resolve this iss
When a PushTarget renders, it fires up a cometd connection to receive
updates. At this point it registers the page activation context.
serverside push events fire a component event. But before this, tapestry
first fires the onActivate with the push target's page activation context.
>From your ear
Yea, I didn't expect that this would mess with the event context to be
honest (and I am not sure how it does) but as I was excluding line by line
and managed to find the issue.
Indeed you are correct this belongs to the cometd.
What details are you interested in?
The use case is that a user uses
Ok, that's a bit of a bombshell you've just dropped there. For those
playing along at home it seems that you're using tapestry-cometd. Care to
share how you're using it?
On 13 Sep 2014 14:49, "Boris Horvat" wrote:
> Ok, so I was able to isolate the problem, but still not sure how to fix it
> :)
11 matches
Mail list logo
