| /[Apache-SVN]/portals/jetspeed-2/portal/tags/JETSPEED-RELEASE-2.2.0/jetspeed-portal-resources/src/main/resources/assembly/ajax-layout.xml |
Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
tagging the 2.2.0 release
JS2-972: commons-logging unsuited for cross-context webapplication invocation usage - migrating to slf4j Fixing Velocity logging using slf4j. Turned out since Velocity 1.5 the log4j logger now needs to be specified as .logger instead of as previously .category ...
Applying JS-880-removeAjaxExport.patch and removing old and un-used psmls
JS2-972: commons-logging unsuited for cross-context webapplication invocation usage - migrating to slf4j See: http://issues.apache.org/jira/browse/JS2-972 Big bang migration to slf4j for both jetspeed-2 and j2-admin. This is not yet the complete migration as unit-test dependencies/requirements for a concrete logger (log4j) have not yet been identified which will need adding (where needed) a slf4j-log4j12 dependency (scope: test). I'll look into that shortly. Additionally, while with these changes the portal and j2-admin logging works fine again, Velocity logging (which used webapp-logging) doesn't seem to get enabled yet. Will look into that today as well.
JS2-938: Changes assembly configuration according to Ate's change on this issue. Now, it can be started with no error, but the actual rendering is not working yet.
One big *initial* commit for primarily JS2-938: Create flyweight PortletWindow instances for each request, the handle to access and store all portlet interaction data and drop the PortletEntityImpl usage See: http://issues.apache.org/jira/browse/JS2-938 WARNING: this commit (together with the shortly following second commit, see further below) will *NOT* bring the trunk back in runnable status yet but at least it will be compilable again. I have done zero testing yet and for one the Spring assembly definitely isn't completely updated yet. And, as an initial commit, there WILL be coding errors and oversights for sure, so all please help out reviewing and fixing as much as possible. This big bang commit delivers the following changes: - all Window cache handling has been removed, just as the WindowAccessor usage - For Thread managment and synchronization, now only two thread locals are used: - one to keep reference to the main (portal) request RequestContext - one for each render job thread PortletWindow - All PortletWindow related state, including the attributes are now stored and managed only through the PortletWindow - The CommonWorkerContext and all related conditional parallel rendering logic has now been removed (as being no longer needed) - PortletWindow now also implements *pluto* PortletEntity but that is a candidate for removal also IMO (I've added a String getEntityId() method on PortletWindow just in case) - PortletEntityImpl and its Broker are still there but nowhere used anymore except in the JetspeedSerializer and through the Ajax API (needs separate cleaning up) And, also, some further wiring of the Pluto container, specifically the PortletRequest/Response*Context implementations for JS2-871 See: http://issues.apache.org/jira/browse/JS2-871 Finally, a second commit will follow shortly (which also will bring the current trunk back to compilable status), concerning JS2-939: Portlet URL/Navigation State JSR-286 Portlet API 2.0 Support, and specifically the public render parameter handling. I've split off that part of my commit to allow easier review by Randy so that those changes don't get "lost" in this big bang commit...
Fixing and setting required svn:eol-style property to - native for extensions in: java|jsp|css|js|xml|sql|txt|properties|tld|psml|vm|html|htm|metadata|xsd|ajax|ldif - LF for extension in: sh This commit contains *no* real changes other than running dos2unix -a on each of the touched files
Creating a new branch for working on JS2-871: Upgrade Pluto container to version 2.0 for up-to-date JSR-168 support. This work is also very much tied to PLUTO-481: Pluto 2.0 Refactoring Initiative, which will be worked on (again) in coordination with JS2-871
At last (and now for real): promotion of the security-refactoring branch as the new trunk (copied). The old trunk is saved away as branch "trunk-before-swapped-with-security-refactoring-branch".
Renaming JetspeedPermissionManager (and Factory) back to old PermissionManager name. Also, several more fixes for new PermissionManager api and PermissionFactory usage
Branching of the JS2-869 for further and even bigger refactoring of the whole of the security component and API.
A temporary branch for working on JS2-869: New Preferences backend implementation for Registry, Entity and Security components
Finally: fully enabling the new Spring assembly filtering. The current configuration and partitioning of filter categories (loaded from WEB-INF/conf/spring-filter.properties) is still at the early stages, but it already enables the loading of a distinct configuration for running the JetspeedSerializerApplication (which will be committed shortly), using the filter categories set "serializer". Other categories sets will be added as needed in the next few weeks, with as primary goal merging all optional/alternate Spring configurations in the main assembly definitions and flag them with appriopiate categories to be able to switch them on/off through the spring-filter.properties configuration.
Formatted all Spring xml configuration files using default indent=2 *no* configuration changes
Bumping to latest Spring 2.5.2 and updating all assembly files replacing old Spring dtd with spring-beans-2.5.xsd, Coming up: dynamic Spring assembly filtering based on custom categories and bean meta data...
fixing reference to JetspeedSerializer
Another missed 2.1.3 synchronization
Moving assembly out of the webapp resources as they is needed for testcases, which the other webapp resources will be moved out to the new jetspeed web application
JS2-857: SVN restructuring to support separate lifecycle for other artifacts besides the portal itself, like j2-admin See: https://issues.apache.org/jira/browse/JS2-857 - step 2a: move trunk under new portal folder
JS2-770: Provide a new maven-2 (only) build environment and restructure the source tree according to the maven-2 conventions See: http://issues.apache.org/jira/browse/JS2-770 Moving templates and resources for the portal application itself and the database related schema and seed data to the new jetspeed-portal-resources sub project
While working with Mohan on Weblogic support + the secondary authentication method, discovered: * isUserInRole method was not implemented for secondary authentication (PortalFilter) * a few Ajax apis needed improved security behaviors
https://issues.apache.org/jira/browse/JS2-716 contribution from Vivek Kumar
added includeMenuDefs query parameter to getmenus ajax-api, which when set to true (i.e. includeMenuDefs=true) causes response to include entire menu definitions rather than just the menu names
https://issues.apache.org/jira/browse/JS2-685 documentation and additional security features contribution from Mikko Wuokko
https://issues.apache.org/jira/browse/JS2-685
JIRA issue JS2-659: Compliance with http://www.apache.org/legal/src-headers.html - (fixed) results of a first run of update-AL20.pl
https://issues.apache.org/jira/browse/JS2-306 Portal Site Manager improvements * move and copy of nodes in the site tree implemented * optional User Tree implemented (without search (ahem....)) contribution from Vivek Kumar
* refine portlet security checks during portlet selection * introduce abstraction to security checks with Security Access Controller component which delegates to either Permission or Constraint checks based on Spring config * make portlet security checks optional via new Security Access Controller component's Spring configuration * rework category portlet selector to properly work in /portal mode, tested with several differet users to test non-profiled paths to full page paths * added requestContext.locatePage functionality * cleanup on old code
ajax apis to support desktop edit mode for: * update fragment * add fragment * remove fragment
https://issues.apache.org/jira/browse/JS2-306 New implementation of Site Manager portlet
added getactions ajaxapi for retrieving the current set of valid actions (portlet modes and window states) for one or more portlet entities
return actions (window states, modes) in getpage ajax api
complete implementation of ajax "window" api: set window state and portlet mode
remove circular dependency in spring configuration not too happy with this solution, thought i could get it around it with a full setter DI, but no luck so instead Im making the DI during container factory set
Two new features: 1. Create User Pages from Roles on first login feature The CreatePageValve creates a new user's home page from the user's role pages 2. Ajax Multi-action - contribution from David Gurney Execute n ajax actions in one request
add ajax support for retrieving decorations, layouts in site portlet
JS2-574 permissions ajax action
To support client-side aggregation in desktop, the "sizes" property for a layout fragment will be retrieved from the layout-portlet init-parameters when it is not explicitly specified is the psml. This means that layout fragments in the GetPageAction psml response will contain a "sizes" property regardless of whether it is defined in the actual psml. from Steve Milek
* new PermissionManager API for updating a set of new granted/revoked roles useful for less chatter on UI updates * unit tests for PermissionManager new API * "permissions" AJAX API implemented * updated AJAX API docs with latest APIs
Adding Commons Logging support for Velocity, JS2-543 See: http://issues.apache.org/jira/browse/JS2-543
Fixing Velocity error on missing VM_global_library.vm file. See: http://issues.apache.org/jira/browse/JS2-462#action_12402321
JS2-523: Supporting custom PortletModes and WindowStates Separated out commit of changes related to current AJAX desktop implementation in progress. The Pluto PortalContextProvider isn't provided anymore, so it can't be used in the assembly either. See: http://issues.apache.org/jira/browse/JS2-523, especially 3.f) and the last remark. David, Steve: please validate!
Added PortalSite component generated menus to AJAX APIs, example request urls: http://localhost:8080/jetspeed/ajaxapi/default_page.psml?action=getmenus http://localhost:8080/jetspeed/ajaxapi/default_page.psml?action=getmenu&name=pages
a couple of commits here: 1. fix bug in remove portlet where it wasnt updated the fragment columns 2. add portlets was not checking for valid portlet names 3. add portlets was not checking for portlets that are allowed viewable for current user 4. the default security behavior was not the correct one 5. Portlet Mode and Window State changes support started still need to integrate this into the Portal URL 6. validate modes and states on setting Steve, please try testing with Desktop, as it will at least persist
ajax moved missing from map
http://issues.apache.org/jira/browse/JS2-514 support for move action (x,y,z,width,height)
Abstracted out PortletActionSecurityBehavior for specialized handling of creation of new pages when you don't have access to shared (role) pages on live edit
added ajax capabilities to customizer - getPages - getPage (this is still early in dev state)
implemented a few more ajax xml apis: * getPortlets (returns filtered (secure) list of portlets, supports filters) * getPage (returns full psml page as xml, should make this default pipeline action) * addPortlet (not yet complete) * removePortlet is broken, get that next
http://issues.apache.org/jira/browse/JS2-387 Had to rename "ajax" servlet path to pipeline enty point to "ajaxapi" since it conflicts with the Ajax Filter. Been testing the Portlet Placement APIs, you can call it from your browser as for ex: http://localhost:8080/jetspeed/ajaxapi?action=movedown&id=dp-3 Note: there is a glitch where I don't check the page access until after I update the page. Need to fix that and you can also use the profiler or specify a specific page: http://localhost:8080/jetspeed/ajaxapi/public/news.psml?action=movedown&id=dp-3 Current APIs implemented and tested and working (it updates the PSML file): moveup movedown moveleft moveright moveAbsolute Not tested addPortlet removePortlet TODO: setLayout (change from two to three column, for example) setDefPageDecorator setDefPortletDecorator setPortletDecorator setTitle ...
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |