Hi Lukasz,
I have debugged through the code (version : 2.3.24.1) and
found the most time taking (marked in *red*) process ie at
DefaultConfiguration#reloadContainer class when loading provider called
convention.PackageProvider
// Then process any package providers from the plugins
Set<String> packageProviderNames =
container.getInstanceNames(PackageProvider.class);
for (String name : packageProviderNames) {
PackageProvider provider =
container.getInstance(PackageProvider.class, name);
provider.init(this);
*provider.loadPackages(); //Taking long time here*
packageProviders.add(provider);
}
for the first time page loads. The same issue is there in 2.5.2 as well. Is
it may be a default behavior to take time ?
On Thu, Jul 21, 2016 at 12:10 PM, Sreekanth S. Nair <
sreekanth.n...@egovernments.org> wrote:
> Sure Lukasz...
>
>
> On Thu, Jul 21, 2016 at 11:57 AM, Lukasz Lenart <lukaszlen...@apache.org>
> wrote:
>
>> 2016-07-21 8:22 GMT+02:00 Sreekanth S. Nair <
>> sreekanth.n...@egovernments.org>:
>> > May be... We are using strust2-spring-plugin. I'm not pretty sure about
>> > this plugin internal, need to investigate on this where its spending
>> time.
>>
>> This plugin replaces the Struts ObjectFactory with a Spring
>> ObjectFactory which simply delegates object instantiating to the
>> Spring, it would be good if you could share results of your
>> investigation.
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
>> For additional commands, e-mail: user-h...@struts.apache.org
>>
>>
>
