Sorry... In *.object.xml I've added this liens :
| supported-window-states
| window-statenormal/window-state
| window-stateminimized/window-state
| window-statemaximized/window-state
| window-statesolo/window-state
|
sorry like this
| layout
| nameEvosCalendar/name
| uri/layouts/EvosCalendar/index.jsp/uri
| uri state=maximized/layouts/EvosMaximized/index.jsp/uri
| regions
| region name=rg0/
| region name=rgb/
| /regions
| /layout
|
humm, I meant uri state=half-page/layouts/EvosHalfPage/index.jsp/uri
layout
| nameEvosCalendar/name
| uri/layouts/EvosCalendar/index.jsp/uri
| uri state=half-page/layouts/EvosHalfPage/index.jsp/uri
| regions
| region name=rg0/
| region
yes, this seems the right way, for what I know.
look at the jsr-168 for defining custom window states.
there is an example with 1/2 maximized state, if I remember well.
To make sure you have declared all that is needed for this state in other
places (portal description, etc...).
By the way,
Hello,
It seems more a pb of wiring.
did you look at the layout strategy source code ?
may be this feature has not been much tested (used ?), and there is a bug, when
routing to the proper jsp file.
as you can write your own, you may do one and see with logs what happen and why
it does not
Hi Antoine,
Sorry I can't help you as I only used Acegi to login but didn't do any
filtering and I haven't used it since. I am currently using the
LdapExtLoginModule to authenticate against my LDAP server which is sufficient
for the time being.
With regards to custom window states I have
