You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/05/18 18:03:16 UTC
[jira] Created: (TAPESTRY-1479) Open up a pipeline between the
MasterDispatcher and the ActionLinkHandler and PageLinkHandler to allow
application-global interception of requests
Open up a pipeline between the MasterDispatcher and the ActionLinkHandler and PageLinkHandler to allow application-global interception of requests
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: TAPESTRY-1479
URL: https://issues.apache.org/jira/browse/TAPESTRY-1479
Project: Tapestry
Issue Type: Improvement
Components: tapestry-core
Reporter: Howard M. Lewis Ship
Priority: Minor
Fix For: 5.0.5
It would be very useful to have a pipeline step between the point where the type of request is known and that information is executed. Something like:
interface RequestPipeline {
void handleAction(String logicalPageName, String nestedComponentId,
String eventType, String[] context, String[] activationContext);
void handleRender(String logicalPageName, String[] context, PageRenderer renderer);
}
interface RequestPipelineFilter {
void handleAction(String logicalPageName, String nestedComponentId,
String eventType, String[] context, String[] activationContext, RequestPipeline pipeline);
void handleRender(String logicalPageName, String[] context, PageRenderer renderer, RequestPipeline pipeline);
}
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1479) It would be nice to have a pipeline
between the Dispatchers and the RequestHandlers (for component action
requests and for page render requests).
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1479:
-------------------------------------------
Summary: It would be nice to have a pipeline between the Dispatchers and the RequestHandlers (for component action requests and for page render requests). (was: Open up a pipeline between the MasterDispatcher and the ActionLinkHandler and PageLinkHandler to allow application-global interception of requests)
... it's also now necessary to support setting the request encoding after the page has been identified.
> It would be nice to have a pipeline between the Dispatchers and the RequestHandlers (for component action requests and for page render requests).
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1479
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1479
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> It would be very useful to have a pipeline step between the point where the type of request is known and that information is executed. Something like:
> interface RequestPipeline {
> void handleAction(String logicalPageName, String nestedComponentId,
> String eventType, String[] context, String[] activationContext);
> void handleRender(String logicalPageName, String[] context, PageRenderer renderer);
> }
> interface RequestPipelineFilter {
> void handleAction(String logicalPageName, String nestedComponentId,
> String eventType, String[] context, String[] activationContext, RequestPipeline pipeline);
> void handleRender(String logicalPageName, String[] context, PageRenderer renderer, RequestPipeline pipeline);
> }
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1479) It would be nice to have a pipeline
between the Dispatchers and the RequestHandlers (for component action
requests and for page render requests)
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1479:
-------------------------------------------
Summary: It would be nice to have a pipeline between the Dispatchers and the RequestHandlers (for component action requests and for page render requests) (was: It would be nice to have a pipeline between the Dispatchers and the RequestHandlers (for component action requests and for page render requests).)
> It would be nice to have a pipeline between the Dispatchers and the RequestHandlers (for component action requests and for page render requests)
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1479
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1479
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> It would be very useful to have a pipeline step between the point where the type of request is known and that information is executed. Something like:
> interface RequestPipeline {
> void handleAction(String logicalPageName, String nestedComponentId,
> String eventType, String[] context, String[] activationContext);
> void handleRender(String logicalPageName, String[] context, PageRenderer renderer);
> }
> interface RequestPipelineFilter {
> void handleAction(String logicalPageName, String nestedComponentId,
> String eventType, String[] context, String[] activationContext, RequestPipeline pipeline);
> void handleRender(String logicalPageName, String[] context, PageRenderer renderer, RequestPipeline pipeline);
> }
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-1479) It would be nice to have a pipeline
between the Dispatchers and the RequestHandlers (for component action
requests and for page render requests)
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1479.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.5
The names and such have changed a bit from when the issue was first added, and its two separate handler interfaces and matching filter interfaces.
For TAPESTRY-1294, this pipeline was necessary so that the request encoding could be properly set.
> It would be nice to have a pipeline between the Dispatchers and the RequestHandlers (for component action requests and for page render requests)
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1479
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1479
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.5
>
>
> It would be very useful to have a pipeline step between the point where the type of request is known and that information is executed. Something like:
> interface RequestPipeline {
> void handleAction(String logicalPageName, String nestedComponentId,
> String eventType, String[] context, String[] activationContext);
> void handleRender(String logicalPageName, String[] context, PageRenderer renderer);
> }
> interface RequestPipelineFilter {
> void handleAction(String logicalPageName, String nestedComponentId,
> String eventType, String[] context, String[] activationContext, RequestPipeline pipeline);
> void handleRender(String logicalPageName, String[] context, PageRenderer renderer, RequestPipeline pipeline);
> }
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1479) Open up a pipeline between the
MasterDispatcher and the ActionLinkHandler and PageLinkHandler to allow
application-global interception of requests
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1479:
-------------------------------------------
Fix Version/s: (was: 5.0.5)
Affects Version/s: 5.0
> Open up a pipeline between the MasterDispatcher and the ActionLinkHandler and PageLinkHandler to allow application-global interception of requests
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1479
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1479
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Priority: Minor
>
> It would be very useful to have a pipeline step between the point where the type of request is known and that information is executed. Something like:
> interface RequestPipeline {
> void handleAction(String logicalPageName, String nestedComponentId,
> String eventType, String[] context, String[] activationContext);
> void handleRender(String logicalPageName, String[] context, PageRenderer renderer);
> }
> interface RequestPipelineFilter {
> void handleAction(String logicalPageName, String nestedComponentId,
> String eventType, String[] context, String[] activationContext, RequestPipeline pipeline);
> void handleRender(String logicalPageName, String[] context, PageRenderer renderer, RequestPipeline pipeline);
> }
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-1479) Open up a pipeline between the
MasterDispatcher and the ActionLinkHandler and PageLinkHandler to allow
application-global interception of requests
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-1479:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> Open up a pipeline between the MasterDispatcher and the ActionLinkHandler and PageLinkHandler to allow application-global interception of requests
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1479
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1479
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> It would be very useful to have a pipeline step between the point where the type of request is known and that information is executed. Something like:
> interface RequestPipeline {
> void handleAction(String logicalPageName, String nestedComponentId,
> String eventType, String[] context, String[] activationContext);
> void handleRender(String logicalPageName, String[] context, PageRenderer renderer);
> }
> interface RequestPipelineFilter {
> void handleAction(String logicalPageName, String nestedComponentId,
> String eventType, String[] context, String[] activationContext, RequestPipeline pipeline);
> void handleRender(String logicalPageName, String[] context, PageRenderer renderer, RequestPipeline pipeline);
> }
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org