Date: 2007.04.24, 11:00 - 12:30
Author: Philipp Bracher
Members: Magnolia Ltd
Oliver & Chris are Commiters
- svn users created
- are assignable in JIRA
Filters / Security
- CMS Filter split (handle, content security, aggregator, renderer)
- Filters are created by using content2bean
- Filters are bypassable
- General extendable security filter
- URI security
Forum
- first rendering of content
- How to implement the actions?
- pages
- other framework
- ...
- New scheduling and resource planing needed
- Mid of may is to optimistic
3.1 M1
- end of this week we release m1
- philipp and sameer commit/merge there changes
Portlets Support (JSR-168)
- Customers are asking how to integrating third party applications
- they search for JSR-168 or WSRP support
- magnolias portlet bridge is not a solution since it supports
getting rendered magnolias content as a portlet
- Possible solutions are:
a) create a WSRP consumer paragraph
- use a WSRP library
- is there a final open source library?
- additionally a WSRP provider could be implemented to provide
content to any portlet containers
b) magnolia is a portlet container itself
- implement portlet API
- seams to be an never ending story
c) magnolia bundles optionally a protlet container
- lifray for example
- special paragraph uses the container to render protlets
- a) and b) are both possible solutions but we tend to a)
- this could be part of magnolia 3.2 (replacing WebDav implementation)
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
