New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LPS-56372 Extend CommandAction framework to have better support for resourceURLs and renderURLs #27381
LPS-56372 Extend CommandAction framework to have better support for resourceURLs and renderURLs #27381
Conversation
…es because right now they are stored in a single one and they are overlapped. This means that it cannot be declared 2 different actions commands for the action phase and the resource phase.
… the resource phase it uses the new resourcecommandactions.
…javax.portlet.name value but also the parameter struts_action if it's present
…y similar we can abstract them out using generics
…k will invoke the renderPhase based on a parameter name strutsAction.
…getTemplate and getStructure.
…uld all use command.name for simplicity. Adapt some ActionCommand that should use ResourceCommand.
…ME is only for actionURLs
…ActionREsponse we should update the API accordingly. However, this API cannot be deprecated because before it was invoked for both actionURL and resourceURLs but now it's only invoked for actionURL so it's better to break the API to make the developers know that the behaviour change. I will add a not in BREAKING_CHANGES file.
Some tests FAILED!Build Time: 28 minutes 47 seconds See the following links for more information.
1 Failure.
|
Hey @rotty3000 @peterfellwock @marcellustavares @brunobasto @leoadb @juliocamarero @epgarcia @mhan810 I have extend the MVCPortlet framework regarding ActionCommand.java. Before we were using ActionCommand.java for both actionURL and resourceURL. I have splitted that in 2 different interfaces. Besides that, the ResourceCommand that will be used is based on resourceID and not based on ActionRequest.ACTION_NAME parameter. I have modified all the uses that I could find in your plugins, so when ActionCommand were used for resourceURLs I have updated that to use ResourceCommand classes. I have done all the changes and you guys shouldn't need to do anything, I'm just ccing you so you're aware of the changes and you can check them or ask any question you may have. @marcellustavares I have also done a fix for DDM in sergiogonzalez@ee5711e because that URL wasn't pointing to any resource handling logic Thanks |
ci:retest |
Thanks @sergiogonzalez, nice improvement :) Thanks for doing that |
Thank you, @sergiogonzalez!! |
cc/ @izaera @JorgeFerrer |
Good job @sergiogonzalez!
|
Hey @sergiogonzalez This is very good. Can you resend in separate pulls: First pull: 1.) Rename "action.command.name" to "mvc.command.name" I think it's easier to comprehend at the OSGi @component level if we prefix everything wth mvc.* 2.) Rename "ActionCommand" to "MVCActionCommand" in preparation for "MVCRenderCommand" etc. Second pull: Add Render and Resource specific things. Thx @sergiogonzalez |
No description provided.