[JBoss JIRA] (GTNPC-109) Modify EventResponse Interface to preserve window state changes accross multiple event invocations
by Adam Kovari (JIRA)
[ https://issues.jboss.org/browse/GTNPC-109?page=com.atlassian.jira.plugin.... ]
Adam Kovari updated GTNPC-109:
------------------------------
Git Pull Request: https://github.com/gatein/gatein-pc/pull/10
> Modify EventResponse Interface to preserve window state changes accross multiple event invocations
> --------------------------------------------------------------------------------------------------
>
> Key: GTNPC-109
> URL: https://issues.jboss.org/browse/GTNPC-109
> Project: GateIn Portlet Container
> Issue Type: Enhancement
> Components: API
> Affects Versions: 2.4.1.Final
> Reporter: Adam Kovari
> Priority: Minor
>
> If a portlet changes it's window state in the event processing phase, this state is not preserved as other portlets/events can be processed on the same page and then portal will override this changes.
> The spec says:
> PLT.12.4 EventResponse Interface
> ================================
> The EventResponse interface extends the StateAwareResponse interface and adds the additional method setRenderParameters(EventRequest request). One thing to note is that if a portlet receives multiple processEvent calls while processing one client request the new portlet mode or window state that the portlet may have set, may be not validated by the portal between these multiple processEvent calls. This means that even if the portlet container may not throw an exception when the portlet sets a new portlet mode or window state that the portal may still not approve this portlet mode or window state change and call the portlet render method with a different portlet mode or window state.
> So the window state change can be preserved even accross multiple events invocation. Seems to be fine by the spec as shown above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-3220) Show wrong message when uncheck show publication date in add/edit node
by Son Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3220?page=com.atlassian.jira.pl... ]
Son Tran commented on GTNPORTAL-3220:
-------------------------------------
It's also in Site Editor -> Add New Page:
- Check Show publication date
- Set Start Publication Date (02/25/2013 15:30:27) is greater than End Publication Date (02/24/2013 15:30:29)
- Uncheck visible
- Click Next
==> Show message alert :"The end date must be after the start date." -> NOK
> Show wrong message when uncheck show publication date in add/edit node
> ----------------------------------------------------------------------
>
> Key: GTNPORTAL-3220
> URL: https://issues.jboss.org/browse/GTNPORTAL-3220
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.1.Final
> Reporter: Son Tran
> Assignee: Son Tran
> Priority: Minor
>
> Add/edit a node
> In Page Node Setting tab:
> Check Show publication date
> Set Start Publication Date (02/25/2013 15:30:27) is greater than End Publication Date (02/24/2013 15:30:29)
> Uncheck show publication date
> Click Save
> => Show message alert :"The end date must be after the start date." -> NOK
> Expected output: The Publication date don't save after set publication date/time for node
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-3220) Show wrong message when uncheck show publication date in add/edit node
by Son Tran (JIRA)
Son Tran created GTNPORTAL-3220:
-----------------------------------
Summary: Show wrong message when uncheck show publication date in add/edit node
Key: GTNPORTAL-3220
URL: https://issues.jboss.org/browse/GTNPORTAL-3220
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.6.1.Final
Reporter: Son Tran
Assignee: Son Tran
Priority: Minor
Add/edit a node
In Page Node Setting tab:
Check Show publication date
Set Start Publication Date (02/25/2013 15:30:27) is greater than End Publication Date (02/24/2013 15:30:29)
Uncheck show publication date
Click Save
=> Show message alert :"The end date must be after the start date." -> NOK
Expected output: The Publication date don't save after set publication date/time for node
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-3218) The global chromattic session context doesn't close properly
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3218?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3218:
----------------------------------
Description:
The following unit testcase doesn't work, it fails in the second openning of the context :
{code}
public void testGlobalSessionClose() {
chromatticManager.beginRequest();
try {
test1LF.openContext();
// do something
test1LF.closeContext(false); // close without persisting changes to DB
//
test1LF.openContext();
test1LF.closeContext(true);
}
finally {
chromatticManager.endRequest(true);
}
}
{code}
it raises an exception of java.lang.IllegalStateException: A context is already opened
was:
The following unit testcase doesn't work, it fails in the second openning of the context :
{code}
public void testGlobalSessionClose() {
chromatticManager.beginRequest();
try {
test1LF.openContext();
// do something
test1LF.closeContext(true);
//
test1LF.openContext();
test1LF.closeContext(true);
}
finally {
chromatticManager.endRequest(true);
}
}
{code}
it raises an exception of java.lang.IllegalStateException: A context is already opened
> The global chromattic session context doesn't close properly
> ------------------------------------------------------------
>
> Key: GTNPORTAL-3218
> URL: https://issues.jboss.org/browse/GTNPORTAL-3218
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Trong Tran
> Labels: backlogs
> Fix For: 3.7.0.Final
>
>
> The following unit testcase doesn't work, it fails in the second openning of the context :
> {code}
> public void testGlobalSessionClose() {
> chromatticManager.beginRequest();
> try {
> test1LF.openContext();
> // do something
> test1LF.closeContext(false); // close without persisting changes to DB
> //
> test1LF.openContext();
> test1LF.closeContext(true);
> }
> finally {
> chromatticManager.endRequest(true);
> }
> }
> {code}
> it raises an exception of java.lang.IllegalStateException: A context is already opened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months