This repository has been archived by the owner on Apr 8, 2019. It is now read-only.
Initial work on GTNWSRP-286 and GTNWSRP-287 #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-via-properties-experiment branch). - Added ExtensionAccessor to allow client code to set / retrieve extensions. Early work. - InteractionParams, EventParams, MarkupParams, ResourceParams can now accept client-set extensions.
…implementation to a DefaultExtensionAccessor subclass that can access more classes.
…to process the invocation before it is sent to the producer and the response before it enters the portal lifecycle.
… consumer package. - Renamed methods for better clarity.
…nvocation as parameter to be able to access the session.
- Fixed initialization and registration code for DefaultConsumerExtensionAccessor.
…and retrieval methods to new ExtensionAccess class to prepare for addition of producer-side class.
- Now ignoring extensions we can't unmarshall.
…ss the invocation before it is sent to the portlet and the response before it is sent back to the consumer on the producer-side.
…it is sent to the consumer.
…dded DefaultProducerExtensionAccessor. - Set up ProducerExtensionAccessor in WSRPProducerImpl
…evel up in the hiearchy.
…we deal with top-level responses (like MarkupResponse or ResourceResponse) instead of UpdateResponse or MimeResponse.
- Added documentation for ProducerExtensionAccessor.
…testing. Might still require more work. * remotes/origin/deactivate-url-rewriting-clean: - Re-created branch to cleanly record work done on adding ability to deactivate URL rewriting on the producer. (cherry picked from commit 0b97cdc)
… extensions to client code. * extensions-accessor: (22 commits) - Fixed ConsumerExtensionAccessor documentation. - Added documentation for ProducerExtensionAccessor. - Fixed handling of response extensions on the consumer-side so that we deal with top-level responses (like MarkupResponse or ResourceResponse) instead of UpdateResponse or MimeResponse. - Moved ConsumerExtensionAccessor and ProducerExtensionAccessor one level up in the hiearchy. - Added documentation. - Added AbstractExtensionAccessor to factor out common behavior and added DefaultProducerExtensionAccessor. - Set up ProducerExtensionAccessor in WSRPProducerImpl - Added capability to add extensions to the producer response before it is sent to the consumer. - Forgot to process extensions on NavigationalStateUpdatingHandler. - Added hooks for delegate to give customers the opportunity to process the invocation before it is sent to the portlet and the response before it is sent back to the consumer on the producer-side. - Modified InvocationHandlerDelegate to also provide a producer-side delegate. - Moved InvocationHandlerDelegate outside of consumer package. - Factor out common code so that it's easier to add handler for exception processing. - Added initial support for producer-side extension processing. - Now ignoring extensions we can't unmarshall. - Made ConsumerExtensionAccessor an interface and moved registration and retrieval methods to new ExtensionAccess class to prepare for addition of producer-side class. - Moved ServletAccess to API module to allow access by users. - Fixed initialization and registration code for DefaultConsumerExtensionAccessor. - Made processInvocationResponse method take the originating PortletInvocation as parameter to be able to access the session. - Fixed typo. - Renamed ExtensionAccessor to ConsumerExtensionAccessor and moved to consumer package. - Renamed methods for better clarity. - Added possibility for customers to define a consumer-side delegate to process the invocation before it is sent to the producer and the response before it enters the portal lifecycle. - Added extension creation from name and value. - Fixed documentation since we're using types after all. ...
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.