atom feed20 messages in org.apache.wicket.usersRe: encapsulation, extension and tran...
FromSent OnAttachments
Jan KriestenMay 12, 2008 2:08 am 
Martijn DashorstMay 12, 2008 4:07 am 
Jan KriestenMay 12, 2008 5:28 am 
Martijn DashorstMay 12, 2008 5:34 am 
Jan KriestenMay 12, 2008 5:39 am 
Igor VaynbergMay 12, 2008 8:25 am 
Johan CompagnerMay 12, 2008 8:34 am 
Jan KriestenMay 12, 2008 9:14 am 
Jan KriestenMay 12, 2008 9:17 am 
Igor VaynbergMay 12, 2008 10:12 am 
Jan KriestenMay 12, 2008 10:25 am 
Igor VaynbergMay 12, 2008 10:31 am 
Gerolf SeitzMay 12, 2008 3:00 pm 
Johan CompagnerMay 12, 2008 3:19 pm 
jWeekendMay 12, 2008 4:59 pm 
Jonathan LockeMay 12, 2008 6:24 pm 
Jonathan LockeMay 12, 2008 6:36 pm 
Eelco HilleniusMay 12, 2008 6:51 pm 
Jan KriestenMay 12, 2008 9:44 pm 
Jonathan LockeMay 12, 2008 10:52 pm 
Subject:Re: encapsulation, extension and transparent resolvers
From:Eelco Hillenius (eelc@gmail.com)
Date:May 12, 2008 6:51:59 pm
List:org.apache.wicket.users

I know transparent resolvers are currently a major issue and can't be really handled in a proper way due to the hierarchy concept. But if things can be fixed with a workaround (until a new transparent resolver model is established) and which has no impact on the overall functionality - why can't that make it into wicket? The 'We wont support this' dogma isn't really proper argumentation.

Sorry you're feeling frustrated. However, the "we won't support this" is directly related to our limited time. Even workarounds have to be evaluated, and evaluating patched typically takes (me at least) between an hour up to a whole evening. It won't be the first time a workaround opens up a can of worms no-one imagined before implementing it. In fact, as far as *I* am concerned, those resolvers are very workaround-ish, and opened up the door for more requests we didn't intend.

In the end, we are the little dictators of our project, and sometimes (unfortunately for you in this case) that means that we just say no to stuff, even if it seems unreasonable. :-) In the end, if you really feel it is important, you can patch a project yourself - which once upon a time wasn't crazy at all -, and you can leave the JIRA issue open in case someone at some point gets inspiration to work on it.

Cheers,

Eelco