[
https://issues.jboss.org/browse/GTNPORTAL-3159?page=com.atlassian.jira.pl...
]
Vu Viet Phuong commented on GTNPORTAL-3159:
-------------------------------------------
portal's dependencies list declared in PortalContainerDefinitionPlugin are use to :
1. Arrange the order of portal container config owner (use last win strategy). Any
extension webapp contexts that is NOT in the dependency list will be compared by using
it's name.
--> The dependency list is just a configuration and it doesn't depends on webapp
deployment. And as I know, we don't support to remove dependency if a webapp is
undeployed. I'm not sure we should check those dependenies existent. May be a solution
is: Warning if any container config owner (extension webapp) that is not in the dependency
list
2. See if a webapp context belong to particular portal container (valid scope)
--> if ignoreUnregisteredWebapp is set to TRUE, and a webapp context is not in the dep
list, it will not be considered valid in that portal container scope --> not allow to
add portal init task from that webapp. So we can add a warning to
PortalContainerConfig#getPortalContainerNames and
PortalContainerConfig#getPortalContainerName method
So we should create a jira on Kernel project for this
Warn when a PortalContainerDef contains a non-existent dependency.
------------------------------------------------------------------
Key: GTNPORTAL-3159
URL:
https://issues.jboss.org/browse/GTNPORTAL-3159
Project: GateIn Portal
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Peter Palaga
Assignee: Vu Viet Phuong
Original Estimate: 4 hours
Remaining Estimate: 4 hours
This is important in a situation when a developer works on a Portal Extension or custom
portal and he includes a non-existent dependency in the configuration of
{{org.exoplatform.container.definition.PortalContainerDefinitionPlugin}} in
{{configuration.xml}} file.
Currently, the portal does not complain at all, the resource loading does not work as
expected by the developer but he has little chance to track down the problem quickly and
effectively. The portal should definitely warn when {{PortalContainerDefinition}} contains
a non-existent dependency.
--
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