We'll read up on this stuff. Thank you. but I have more comments in line.
Filip S. Adamsen wrote:
Defaults for Symbols are easy. Just contribute your defaults to
FactoryDefaults, and let the user override them in ApplicationDefaults:
http://tapestry.apache.org/tapestry5/tapestry-ioc/symbols.ht
Hi,
Defaults for Symbols are easy. Just contribute your defaults to
FactoryDefaults, and let the user override them in ApplicationDefaults:
http://tapestry.apache.org/tapestry5/tapestry-ioc/symbols.html
Configurations are different, and have caused quite a few people
problems. There's been ta
Em Fri, 03 Oct 2008 16:13:39 -0300, Fernando Padilla <[EMAIL PROTECTED]>
escreveu:
Seriously, we love tapestry. But this could totally tarnish my respect
of the project; such a short sighted decision to block overrides of
configuration settings!
Please do not stop loving something becaus
Seriously, we love tapestry. But this could totally tarnish my respect
of the project; such a short sighted decision to block overrides of
configuration settings!
And the idea that the ordering of loading up SubModules is ignored?
That's just not cool either.
So any ideas on how to fix this
Em Fri, 03 Oct 2008 15:20:38 -0300, Fernando Padilla <[EMAIL PROTECTED]>
escreveu:
> can you tell me why you want to change the contribution?
> why not set it only once?
Alright, so maybe my response below is a little rant/flame. But really,
are you truly saying that Tapestry doesn't all
> can you tell me why you want to change the contribution?
> why not set it only once?
Alright, so maybe my response below is a little rant/flame. But really,
are you truly saying that Tapestry doesn't allow libraries to properly
set defaults, then allow users of the library to override those
hi tom,
ordering is not possible because the service does not
use a ordered configuration. overriding of contributions
is also not supported. it worked accidentally in previous
versions :) the order in which the module classes are loaded
is not defined and usually not relevant.
can you tell
