Issue Details (XML | Word | Printable)

Key: TRAILS-37
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alejandro Scandroli
Reporter: Alejandro Scandroli
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Trails

remove Tapernate

Created: 02/May/07 05:52 AM   Updated: 30/Sep/07 06:45 PM
Component/s: None
Affects Version/s: 1.0.0
Fix Version/s: 1.1.0

Time Tracking:
Not Specified


 Description  « Hide
We are not getting any response from James and Tapernate isn't giving us too much benefits. So i propose to remove Tapernate and implement (again) our own Squeezer strategy and our own PropertyPersistenceStrategy.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Ken in nashua added a comment - 02/May/07 08:06 AM
Tapernate is missing some real-use extensions.

I think it might be less taxing (and have less impact) if we were to extend it.

Just a suggestion.

The priority also could be lowered too due to bugs that prevent apps from running and operating (which also impeded development of new features).


Kalle Korhonen added a comment - 05/Jun/07 10:45 AM
Tapernate also by-passes the persistence service which makes it impossible to apply view rules of owner instance-based security.

Ken in nashua added a comment - 08/Jun/07 03:16 PM
pre-checkin...

1. public interface ICallback extends Serializable

this seems ok for callbacks themselves.

2. public class CallbackStack
{

does not implement nor extend Serializable

But it is an ASO in hivemind with scope session...

<contribution configuration-id="tapestry.state.ApplicationObjects">
<state-object name="callbackStack" scope="session">
<create-instance class="org.trails.callback.CallbackStack"/>
</state-object>
</contribution>

which should suffice.

Did you try to add
public class CallbackStack implements Serializable ?


Alejandro Scandroli added a comment - 12/Jun/07 10:35 AM
Tapernate removal is complete.
The work in new PersistenceStrategies will continue as part of TRAILS-63 work