You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Norbert Sándor (JIRA)" <ta...@jakarta.apache.org> on 2005/07/10 18:11:12 UTC
[jira] Commented: (TAPESTRY-157) support for subclassing in DirectService
[ http://issues.apache.org/jira/browse/TAPESTRY-157?page=comments#action_12315442 ]
Norbert Sándor commented on TAPESTRY-157:
-----------------------------------------
I've similar problem in Tapestry 4:
- static methods in EngineMessages should be public to be usable from custom services
- In case of DirectService I want both triggering and response rendering to happen in db transaction. To make it possible without copy-paste, direct.trigger(cycle); should be in a separate method.
Br,
Norbi
> support for subclassing in DirectService
> ----------------------------------------
>
> Key: TAPESTRY-157
> URL: http://issues.apache.org/jira/browse/TAPESTRY-157
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 3.0
> Environment: Operating System: Other
> Platform: Other
> Reporter: Norbert P.
> Assignee: Tapestry Developer List
>
> I'd like to subclass DirectService by slightly modifying the behaviour of the
> service() method but leaving the getLink() method untouched. I have the
> following problems with this:
> - DirectService.STATEFUL_ON and DirectService.STATEFUL_OFF are private, so I
> cannot copy-paste the code from the original service() method to my subclass
> - Of course it would be much better to prevent copy-paste. For example the
> service() method should be cut into at least two separate methods: extracting
> parameters and executing service related tasks. This is necessary to execute
> the service without a RequestContext (for testing or internal invocation).
> - the above subclassing problem is true for all services
> All the above is irrelevant if default Tapestry services are not intended to be
> (easily) subclassed (but I think they should be).
> Thanks,
> Norbi
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org