[jira] [Commented] (TAP5-1850) Impossible to override the ComponentMessagesSource service, by using the ServiceOverride service
[
https://issues.apache.org/jira/browse/TAP5-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228396#comment-13228396
]
Emmanuel DEMEY commented on TAP5-1850:
--
Thanks a lot Christian.
It works like a charm !! :d
Manu
> Impossible to override the ComponentMessagesSource service, by using the
> ServiceOverride service
>
>
> Key: TAP5-1850
> URL: https://issues.apache.org/jira/browse/TAP5-1850
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
>Affects Versions: 5.3
>Reporter: Emmanuel DEMEY
>Priority: Blocker
> Attachments: tapestry.zip
>
>
> I am working in the migration of one of our Components library : Tapestry
> 5.2.6 to 5.3, and I have a problem with the ServiceOverride service.
> I would like to override the default implementation of the
> ComponentMessagesSource service. So first, I added this new implementation
> by using the ServiceBinder :
> public static void bind(ServiceBinder binder) {
> binder.bind(ComponentMessagesSource.class,
> TestMessageSource.class).withId("test");
> }
> And after, I contributed to the ServiceOverride service, in order to specify
> the default implementation of the ComponentMessagesSource interface :
> public static void contributeServiceOverride(MappedConfiguration Object> configuration,
> @Local ComponentMessagesSource override) {
>
> configuration.add(ComponentMessagesSource.class, override);
>
> }
> But when I jetty:run my application, I have got this message error :
> Render queue error in BeginRender[core/PropertyEditBlocks:numberfield]:
> Failure reading parameter 'translate' of component
> core/PropertyEditBlocks:numberfield: Exception constructing service
> 'FieldTranslatorSource': Service interface
> org.apache.tapestry5.services.messages.ComponentMessagesSource is matched by
> 2 services: ComponentMessagesSource, Test. Automatic dependency resolution
> requires that exactly one service implement the interface.
> So, I also checked the implementation of the MasterObjectProviderImpl, and I
> think Tapestry do not find the right ObjectProvider for my interface.
> Here is the email sent to me by Howard :
> There is a definite bug here, and it is related to
> ComponentMessagesSource ... or, more specifically,
> ApplicationMessageCatalogObjectProvider (which is what allows services
> to inject a Messages instance and get a localized version of the
> application messages). ObjectProviders, contributed to the
> MasterObjectProvider service, are part of the general injection
> infrastructure, and thus have the be very tricky to prevent unintended
> dependency loops. Even so, it should be possible to fix this with a
> little recoding
> Thanks
> Manu
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1526) Tapestry5 plugin for roo
[ https://issues.apache.org/jira/browse/TAP5-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190947#comment-13190947 ] Emmanuel DEMEY commented on TAP5-1526: -- Hi I have just started a Spring Roo plugin for Tapestry, available on Github : https://github.com/Gillespie59/Tapestry-Roo. Right now, this plugin just create the basic Tapestry Structure. If you have some features you want to see in this kind of plugin, do not hesitate to contact me! Manu > Tapestry5 plugin for roo > > > Key: TAP5-1526 > URL: https://issues.apache.org/jira/browse/TAP5-1526 > Project: Tapestry 5 > Issue Type: Wish >Reporter: Toby > > There should be a Tapestry5 plugin for Roo (http://www.springsource.org/roo). > As probably every Tapestry5 developer is also using Spring, it would be good > if Tapestry5 and Roo joined forces > Things like: > - command line tools > - plugins (spring-security, selenium) > - eclipse tools > could be shared. > Both the pure Java approach and the Tapestry approach have their > advantages/disadvantages, depending on the scenerio. > So control interfaces or ajax/comet/atmosphere kind of application are often > better off to be developed using Roo+Vaadin - and as an alternative for web > applications where seo/urls and templates matter, > Roo+Tapestry5 is the best choice (e.g. when ready-made HTML templates are > delivered and need to be implemented). > Roo seems to focus more on the first approach, but a kind of plugin (e.g. for > Tapestry5), to offer the second approach to Roo developers would be extremely > helpful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1704) Localizing the "Today" and "None" labels in the core datefield component
[ https://issues.apache.org/jira/browse/TAP5-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140018#comment-13140018 ] Emmanuel DEMEY commented on TAP5-1704: -- But these 2 strings are hardcoded in the external datepicker.js. I think we can not change this behavior easily. > Localizing the "Today" and "None" labels in the core datefield component > > > Key: TAP5-1704 > URL: https://issues.apache.org/jira/browse/TAP5-1704 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.3 >Reporter: Patricia Arranz > > In de DateField Component the text of the buttons "Today" and "None" don´t > get translated. they are hardcoded in the javascript code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1338) Add informal parameters support to Form component
[ https://issues.apache.org/jira/browse/TAP5-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140011#comment-13140011 ] Emmanuel DEMEY commented on TAP5-1338: -- Hi This issue can be closed. resolved by Howard. Cf. https://issues.apache.org/jira/browse/TAP5-724 > Add informal parameters support to Form component > - > > Key: TAP5-1338 > URL: https://issues.apache.org/jira/browse/TAP5-1338 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.2 >Reporter: Anton N. Mezerny >Priority: Minor > > Add @SupportsInformalParameters annotation to the Form component. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
