I accompiished this by a service named ComponentMessagesOverride. The mapped
configuration of the service is used to contribute new paths for component
message catalogs. This service is used in an advise method to override the
result of ComponentMessagesSource#getMessages. This temporary hack is ok
Em Wed, 02 Dec 2009 20:54:09 -0200, Howard Lewis Ship
escreveu:
I think the entire approach needs to be a bit more pluggable (though
decorating the service is also an option).
Service decoration in Tapestry-IoC is very powerful. Once I was in a hurry
and needed to override a service imple
This is something I've been meaning to look at as well. I'd like to
check what I've done for my client to see what I had to hack to
accomplish this, to ensure that we don't go through a couple of cycles
of this. I'm working for that client tomorrow, so I'll document that's
needed then.
I think the
There's definitely a bit of conflict going on here. On the one hand,
Apache's central message is all about community, but at the same time
(for the sake of the legal umbrella and CLA's) we are embracing a tool
(SVN) specifically to act as a choke point preventing community
involvement.
As a side n
I had this problem before and I had to hack some internals services to make
it works.
I'm definitely OK to make this API public.
On Wed, Dec 2, 2009 at 9:59 PM, Igor Drobiazko wrote:
> I would like to fix TAP5-915 and have to make ComponentMessagesSource a
> part
> of the public API. I know we s
I would like to fix TAP5-915 and have to make ComponentMessagesSource a part
of the public API. I know we should be reluctant to move services from
internal packages but this feature is a must. Tapestry allows you to
override almost every part of the framework, but not the message catalog of
the co
I have provided a simple fix for TAP5-839, along with a test. Please consider
it for inclusion in 5.1.0.6. .
Cheers,
Peter
--
View this message in context:
http://old.nabble.com/issues-to-be-fixed-for-5.1.0.6-tp26423770p26616334.html
Sent from the Tapestry - Dev mailing list archive at Nabble.
On Wed, Dec 2, 2009 at 11:39 AM, Daniel Kulp wrote:
> On Mon November 30 2009 4:50:15 pm Howard Lewis Ship wrote:
>> The reality is that regardless of whether code comes in as patches in
>> JIRA or as Git pull requests on GitHub, there is still a committer
>> making the change and committing it to
On Mon November 30 2009 4:50:15 pm Howard Lewis Ship wrote:
> The reality is that regardless of whether code comes in as patches in
> JIRA or as Git pull requests on GitHub, there is still a committer
> making the change and committing it to the "master" repository. Using
> Git instead of SVN does
