[
https://issues.jboss.org/browse/GTNPORTAL-2340?page=com.atlassian.jira.pl...
]
Marek Posolda commented on GTNPORTAL-2340:
------------------------------------------
Fixed by introduce abstract method getRequireLifeCycle on WebRequestHandler.
It returns false for: DefaultRequestHandler, StaticResourceRequestHandler,
DownloadHandler, UploadHandler (so these handlers does not require RequestLifeCycle)
It returns true for: PortalRequestHandler, LegacyRequestHandler (so these handlers
requires RequestLifeCycle)
WebAppController needs to start RequestLifeCycle for every processing
(including static resource processing)
------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2340
URL:
https://issues.jboss.org/browse/GTNPORTAL-2340
Project: GateIn Portal
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0-Beta01
Reporter: Marek Posolda
Assignee: Marek Posolda
Fix For: 3.2.0-CR01
Second thing is not so bad but a bit more tricky. The piece of code in WebAppController:
{code}
if (!started)
{
RequestLifeCycle.begin(ExoContainerContext.getCurrentContainer());
started = true;
}
.....
processed = handler.execute(new ControllerContext(this,
router, req, res, parameters));
.....
if (started)
{
RequestLifeCycle.end();
}
{code}
This means that we need to start RequestLifeCycle for processing of
every resource including static resource. And startup of some services
is quite expensive (like startup of OrganizationService requires startup
of Hibernate transaction). In other words, currently we are starting
Hibernate transaction for processing images and other static resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira