|Jan Kriesten||May 12, 2008 2:08 am|
|Martijn Dashorst||May 12, 2008 4:07 am|
|Jan Kriesten||May 12, 2008 5:28 am|
|Martijn Dashorst||May 12, 2008 5:34 am|
|Jan Kriesten||May 12, 2008 5:39 am|
|Igor Vaynberg||May 12, 2008 8:25 am|
|Johan Compagner||May 12, 2008 8:34 am|
|Jan Kriesten||May 12, 2008 9:14 am|
|Jan Kriesten||May 12, 2008 9:17 am|
|Igor Vaynberg||May 12, 2008 10:12 am|
|Jan Kriesten||May 12, 2008 10:25 am|
|Igor Vaynberg||May 12, 2008 10:31 am|
|Gerolf Seitz||May 12, 2008 3:00 pm|
|Johan Compagner||May 12, 2008 3:19 pm|
|jWeekend||May 12, 2008 4:59 pm|
|Jonathan Locke||May 12, 2008 6:24 pm|
|Jonathan Locke||May 12, 2008 6:36 pm|
|Eelco Hillenius||May 12, 2008 6:51 pm|
|Jan Kriesten||May 12, 2008 9:44 pm|
|Jonathan Locke||May 12, 2008 10:52 pm|
|Subject:||Re: encapsulation, extension and transparent resolvers|
|From:||Igor Vaynberg (igor...@gmail.com)|
|Date:||May 12, 2008 10:31:08 am|
too bad you did not maintain the jira issue properly. maybe now you have a taste of what its like, but try it for hundreds of issues.
On Mon, May 12, 2008 at 10:26 AM, Jan Kriesten <jan....@renitence.de> wrote:
so i am a little confused as to why we are talking about transparent resolvers, and why gerolf did not apply that code himself...
i tried to verify whether or not is related to the transparent resolver - it seems at last it's connected to them cause i couldn't produce a case where it happens without them. (though i can't claim it can't happen)
maybe gerolf didn't want to step into ground where others may have more insight - that's the reason i filed this to jira.
personally i do not like to change code if it "maybe" helps,
it helps, so it's not 'maybe' in this case.
especially if it is markup parsing code which is a pretty fragile area in wicket.
right, i very well understand - this has to be carefully reasoned. i didn't find any problems with this workaround with my code yet - a test on a second codebase would be helpful though.
if there are no objections i will ask gerolf to apply this patch (and remove it again should there be evidence that it breaks anything on another project).
hopefully there will be another way with 1.5 to cope with transparent resolvers so this only is a matter of time 'til wicket is more robust on those use cases.
best regards, --- jan.