[
https://jira.jboss.org/jira/browse/GTNPORTAL-202?page=com.atlassian.jira....
]
Minh Hoang TO resolved GTNPORTAL-202.
-------------------------------------
Resolution: Done
Deleting portlet is quite easy to handle as there is no nested portlet. For the
container, we have nested container, so it is a bit more complex ( especially the
difference between IDs in server-side and client-side prevent us from using Ajax in normal
way).
Consider a deleted component 'uiComp', i define two others
'topAncestor' and 'uiParent'
'topAncestor' : the most outer ancestor of 'uiComp', but under either
UIPage or UIPortal.
'uiParent' : the parent of 'uiComp'
Case 1: If 'topAncestor' has no child, then the whole block
'topAncestor' is removed
Case 2: If 'uiParent' has no child and 'topAncestor' does not equal
'uiParent', then 'uiParent' is removed from server-side. The whole block
'topAncestor' is updated
Otherwise: The block 'topAncestor' is entirely updated
Still show tab which was delete in tab container
-------------------------------------------------
Key: GTNPORTAL-202
URL:
https://jira.jboss.org/jira/browse/GTNPORTAL-202
Project: GateIn Portal
Issue Type: Bug
Affects Versions: 3.0.0-Beta02
Reporter: Hang Nguyen
Assignee: Minh Hoang TO
Priority: Minor
Fix For: 3.0.0-Beta03
Attachments: 3.jpg
Steps:
- Create new page --> at step 3: select container ( two or three tab) --> choose
one tab to delete --> Still show tab which was delete in tab container --> error.
See attach file
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira