[ 
https://issues.apache.org/jira/browse/TAP5-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644608#action_12644608
 ] 

Fernando commented on TAP5-184:
-------------------------------

I know that your intention was to allow people to place a filter after the real 
RenderSupport and allow easy overriding that way, but it did not pan out that 
way for various reasons:

1) There was no way for me to turn off RenderSupport, in that i always did 
work, even if I took over much of the work for it.. ( it still called 'commit' 
and 'render' on the way out of the markupfilter..
2) The other markupfilters that depend on RenderSupport know about that ( 
before:RenderSupport, after:RenderSupport ), but do not know about my secondary 
overriding filter.. so it's unreliable to me to override it.. basically i would 
need a third option ( directly-after:RenderSupport, override:RenderSupport ), 
to make sure that my Filter went right after RenderSupport, but before anyone 
that was depending on it..

Because of these things, it still boils down to the configuration system is 
trying to hide too many things from people using it..  And I hold that not 
exposing a clean way to override or change configurations made by underlying 
libraries is a deficiency..  We can come up with work arounds and various other 
ideas, but I think we'll always come back to this. :)


> Improve error reporting when a javascript asset is intended to be included on 
> page which has no <body> element
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-184
>                 URL: https://issues.apache.org/jira/browse/TAP5-184
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.15
>            Reporter: Michael Lake
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>
> I know - silly of me to have a page with no <body></body> element. I spent an 
> entire day trying to figure out why the javascript wasn't getting included.
> It was my error, but I can see other people making the same mistake...a 
> little error-reporting would be nice.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to