[
https://issues.apache.org/jira/browse/TAP5-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-185.
-------------------------------------
Resolution: Invalid
Your example now works; Tapestry recognizes Object.class or your service
interface as representing the core service implementation. This represents a
previous change.
> aditional example for service decorators
> ----------------------------------------
>
> Key: TAP5-185
> URL: https://issues.apache.org/jira/browse/TAP5-185
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Reporter: Davor Hrg
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> documentation for decorating services should have an additional example
> somethig like this for situations where we are decorating a specific service,
> and not using some general decorator factory
> public static ComponentMessagesSource
> decorateComponentMessagesSource(Object delegate, Logger logger){
> return new ComponentMessagesSourceDecorator((ComponentMessagesSource)
> delegate,logger);
> }
> this should be documented because the decorator is ignored if above is
> chenged this way
> (this is somehow more logical than above but doesn't work)
> public static ComponentMessagesSource
> decorateComponentMessagesSource(ComponentMessagesSource delegate, Logger
> logger){
> return new ComponentMessagesSourceDecorator(delegate,logger);
> }
> I think that the second sample caused exceptions in earlier versions....
> (the exception was even more misleading)
> of course, if not too much trouble, tapestry ioc could be modified so that
> the second example works as well
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
