No we can fix this properly. I'll fix it.. Thanks, ~Isuru
On Sat, Oct 22, 2011 at 9:58 PM, Muhammed Shariq <sha...@wso2.com> wrote: > Hi, > > When testing with the latest packs I noticed that all services may it be > jar-service, spring service, or mashups etc, the service type initially is > shown as *axis2* in the service listing page. Once the service is invoked > (actual service is loaded), and you refresh the service list, then its > displays the correct service type. > > Listing type as axis2 for GD services are misleading IMO, may be could > indicate as a GD service or else show the correct service type (as mashup, > jar, spring) ? > > > On Thu, Oct 13, 2011 at 12:57 PM, Afkham Azeez <az...@wso2.com> wrote: > >> >> >> On Thu, Oct 13, 2011 at 12:55 PM, Isuru Suriarachchi <is...@wso2.com>wrote: >> >>> I went through the implementation. But why do we load modules here and >>> there? I think if we get rid of module persistence overhead, that will be >>> enough to improve the tenant loading time. Without persistence, module >>> loading won't get much time. Isn't it? >>> >>> If we do this in the way it's currently done, there are many places where >>> we have to check whether the modules are loaded and load them if not already >>> done. Isn't it too much trouble for a very little gain? >>> >> >> To make this decision, you have to first do a perf comparison. >> >> 1. With module persistence >> 2. Without module persistence >> 3. Without persistence with a reasonable number of modules (~10) >> >> Need to compare the overhead for simple webapp cases. In the case of >> webapps, we don't need module loading. >> >> >>> >>> Thanks, >>> ~Isuru >>> >>> On Tue, Oct 11, 2011 at 8:50 AM, Amila Suriarachchi <am...@wso2.com>wrote: >>> >>>> >>>> >>>> On Mon, Oct 10, 2011 at 10:42 AM, Isuru Suriarachchi <is...@wso2.com>wrote: >>>> >>>>> Hi all, >>>>> >>>>> Looks like the recent module changes are causing a NPE when trying to >>>>> engage a module for a fresh service. I tried this on Stratos 1.5.2. >>>>> >>>>> How to reproduce.. >>>>> 1. Log into a tenant >>>>> 2. Upload a fresh service >>>>> 3. Try to engage a module (Throttling, Caching, Security etc.) from the >>>>> UI >>>>> >>>>> This doesn't happen if I try to do it after invoking the service once. >>>>> I think this is because the modules are only loaded into the AxisConfig >>>>> when >>>>> the first request comes in. Amila, can you please fix this? >>>>> >>>> >>>> yes there are some issues with the new improvement. >>>> >>>> We need to fix this with the service deployment. >>>> >>>> When a service get deployed for the first time, since we don't know the >>>> service details it has to load all the modules (if not loaded) and deploy >>>> the service at the Ghost deployer level. (service already may engaged those >>>> modules) see the MTMR to how to do that. >>>> >>>> Then need to persists the engaged module details and load the modules at >>>> the MTMR level if someone try to invoke the service at the second time. >>>> >>>> Then need to fix at the module management service level as well. If some >>>> one invokes the module management UI (like in service management UI) then >>>> again need to load all the modules. >>>> >>>> Can you please add those features? I am in the support week and need to >>>> prepare for an on site work. >>>> >>>> thanks, >>>> Amila. >>>> >>>>> >>>>> Thanks, >>>>> ~Isuru >>>>> >>>>> -- >>>>> Isuru Suriarachchi >>>>> Technical Lead & Product Manager, WSO2 Application Server >>>>> WSO2 Inc. http://wso2.com >>>>> email : is...@wso2.com >>>>> blog : http://isurues.wordpress.com/ >>>>> >>>>> lean . enterprise . middleware >>>>> >>>>> >>>> >>> >>> >>> -- >>> Isuru Suriarachchi >>> Technical Lead & Product Manager, WSO2 Application Server >>> WSO2 Inc. http://wso2.com >>> email : is...@wso2.com >>> blog : http://isurues.wordpress.com/ >>> >>> lean . enterprise . middleware >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> >> _______________________________________________ >> Stratos-dev mailing list >> stratos-...@wso2.org >> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev >> >> > > > -- > Thanks, > Shariq. > > -- Isuru Suriarachchi Technical Lead & Product Manager, WSO2 Application Server WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
