Trails

remove Tapernate

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.0
  • Fix Version/s: 1.1.0
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ken in nashua added a comment -

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).

Show
Ken in nashua added a comment - 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).
Hide
Permalink
Kalle Korhonen added a comment -

Tapernate also by-passes the persistence service which makes it impossible to apply view rules of owner instance-based security.

Show
Kalle Korhonen added a comment - Tapernate also by-passes the persistence service which makes it impossible to apply view rules of owner instance-based security.
Hide
Permalink
Ken in nashua added a comment -

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 ?

Show
Ken in nashua added a comment - 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 ?
Hide
Permalink
Alejandro Scandroli added a comment -

Tapernate removal is complete.
The work in new PersistenceStrategies will continue as part of TRAILS-63 work

Show
Alejandro Scandroli added a comment - Tapernate removal is complete. The work in new PersistenceStrategies will continue as part of TRAILS-63 work

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.