Date: 2007.06.13, 14:00 - 15:00
Author: Philipp Bracher
Members: Philipp, Sameer, Gregory, Pascal, Boris
Portlets
- WSRP
- wsrp.dev.java.net released (but highly depending on portlets)
- Liferay
- WSRP4J (what is happening there?)
FCKEditor
- solving the page renaming / activating to other paths is not that
simple
- we need to store the uuid of the node and resolve the paths
- most of the code / tests are done
Documentation
- we keep Developer, Editor, Admin sections
Image Cropping
- we finish till the end of this week
- multiple settings done
- support other formats
- preview (simple solution --> remove preview after changing the
cropping)
- revering to dms is postponed
Clustering / Save / Lock:
- could be that we will see again IllegalItemStateExceptions when
we use clustering
- our lock is a memory lock (only seen by the VM)
- should we implement a forced save?
- how works a jcr lock in clustered environment?
- Sameer checks that / does an evaluation of the possible solutions
i18n (using a virtual hierarchy manager):
- The solution of many problems could be found by using a virtual
hierarchy manager
- the hm would be able to combine data (default pages, language
specific entries)
- a special accessmanager could handle security in the magnolia way
- saving would store in a 'special' structure
- editing and rendering would be very easy
Reverting API changes:
- we should keep the new interfaces HierarchyManager, Content,
NodeData in there original core package
- keeping them in the same package would facilitate updating a lot
- since we plan other changes in the api we should not make an
extra tour for three classes now!
- ${actpage}
- Compatibility Filter adding Wrapper Object --> writing
warnings! and delegating to the new methods
Updateing:
- Meeting Thursday 11:00
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
