I checked the code of tapestry-jquery and I think it should be fine
without setting the ordering. tapestry-jquery checks the same header to
determine if it's a request from its file upload comp. Since I already
changed that header, tapestry-jquery won't process and read the reqeust
inputstream.
Thats purgeChildren(...) probably needs to be fixed too :)
On Sun, Sep 2, 2012 at 1:35 AM, Muhammad Gelbana wrote:
> I've been debugging the code too and found out that the method
> purgeChildren(element); looks up the element's children through
> element.childNodes which is always undefined. Wha
Thanks a lot for your help :)
On Sat, Sep 1, 2012 at 11:35 PM, Muhammad Gelbana wrote:
> I've been debugging the code too and found out that the method
> purgeChildren(element); looks up the element's children through
> element.childNodes which is always undefined. What's confusing me is that
> t
I've been debugging the code too and found out that the method
purgeChildren(element); looks up the element's children through
element.childNodes which is always undefined. What's confusing me is that
this case isn't so special and isn't hard to fix, so why is it still there
?!
On Sat, Sep 1, 2012
I created issue for this in tapestry5-jquery:
https://github.com/got5/tapestry5-jquery/issues/230
On Sun, Sep 2, 2012 at 1:26 AM, Dmitry Gusev wrote:
> This seems to be bug in tapestry5-jquery.
>
> In file t5-dom-jquery.js:
>
> /**
> * Removes all children form the elem
This seems to be bug in tapestry5-jquery.
In file t5-dom-jquery.js:
/**
* Removes all children form the element, properly purging
child elements
* of any listeners, etc.
* @param element to purge
*/
function removeChildre
Alerts rendering currently implemented entirely using client-side
javascript [1], so you can't change this.
But, you can add your own event handler which will be invoked right after
alerts get created in HTML DOM and add custom classes to them, like I did
for tapestry-bootstrap [2].
[1] tapestry5
I forgot to mention that one may also need to change the rendering tag. I'm
over that part but I like to identify all the solutions possible. In my
case I wanted to render the alerts in *h4* tags instead of *divs* with
specific css classes since the template I'm using has a style for that.
Frankly
https://issues.apache.org/jira/browse/TAP5-1996
Thats easy to implement, but it should be done in tapestry-core.
I will try to send a patch for this in a few days, hope it will get into
5.3.6
On Sat, Sep 1, 2012 at 10:11 PM, Muhammad Gelbana wrote:
> I'm wondering how can I add more alert types
It must be something wrong I'm doing because It's working fine in the same
environment for the tapestry's quickstart application !
What exactly happens is that after few alerts are generated from different
sources (event link and form submits), if I click "Dismiss all", all alerts
disappear and th
I'm wondering how can I add more alert types ? Precisely I'm trying to use
a new alert type as a "*Success*" indication in addition to the existing (*
Info*, *Warning* and *Error*) alerts. Thank you.
Oh thanks. Was this valid for long time ?
On Sat, Sep 1, 2012 at 8:01 PM, Christian Riedel wrote:
> No, that's ok, since they are tied with the component using @Component.
> You can configure components completely in your component class if you
> wish and only use t:id in the template…
>
>
>
> Am
No, that's ok, since they are tied with the component using @Component.
You can configure components completely in your component class if you wish and
only use t:id in the template…
Am 01.09.2012 um 16:50 schrieb Muhammad Gelbana:
> On this page:
> http://tapestry.apache.org/current/apidocs/o
I think that should work too but you have to ensure that your filter is before
the tapestry-jquery filter by using before:AjaxUploadFilter for ordering.
On Sep 1, 2012, at 8:56 PM, Rural Hunter wrote:
> How would that work? will it disable both filters? One way I figured out is:
> I changed the
How would that work? will it disable both filters? One way I figured out
is: I changed the filter name and the AJAX_UPLOAD_HEADER in your code. I
think it should work. am I right?
于 2012/9/1 18:19, Taha Siddiqi 写道:
One way to handle it would be to contribute an override for "AjaxUploadFilter"
On this page:
http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/corelib/components/EventLink.html
I found the following:
**${columnModel.label}
> **
>alt="${iconLabel}"/>
>
The tags are missing the t:type attribute.
One way to handle it would be to contribute an override for "AjaxUploadFilter"
to HttpServletRequestHandler with an empty implementation of
HttpServletRequestFilter
Some thing like
public static void contributeHttpServletRequestHandler(final
OrderedConfiguration configuration,
final AjaxU
So, is there any mean to log onto the real class when a logger in injected in
that class ?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715964.html
Sent from the Tapestry - User mailing list archi
I think I got It:
- when logger is @Inject'ed in my module and passed as my filter constructor
parameter, the messages are logged in the name of my module class
- when logger is automatically injected in my filter, the messages are
logged in the name of
"org.apache.tapestry5.services.TapestryModule
> With
"after:CheckForUpdates,before:URLRewriter" the behavior is the same.
You can't comma separate constraints in a single string like this. Use two
strings in the varargs method.
Try using system.out.println instead (or a debug breakpoint) but I doubt
that tapestry is logging at different log
Hi Taha,
I used your comp first. Then other memeber in the team introduced
tapestry-jquery later. besides, I do more like the appearance of your
comp than he one in tapestry-jquery.
于 2012/9/1 14:29, Taha Hafeez Siddiqi 写道:
If you are already using tapestry-jquery why not use it's own Ajaxup
It's an issue with log levels :
when logger is @Inject'ed in my module and used as new myRequestFilter()
parameter, it logs at trace level.
when logger is injected as a parameter (when I use addInstance), it logs at
"info" level ?!
--
View this message in context:
http://tapestry.1045711.n5.na
Thanks a lot; but, in fact, the issue is not with constraints; with
"after:CheckForUpdates,before:URLRewriter" the behavior is the same.
In fact, it has to do with parameter injection, as you supposed : with
addInstance, I see no log, but the code is executed.
--
View this message in context:
23 matches
Mail list logo
