On Sun, May 27, 2012 at 7:03 PM, Afkham Azeez <az...@wso2.com> wrote:
> This is because in one deployment cycle the CAR deployer extracts the > relevant artifacts, and in the 2nd cycle, the actual deployment happens. > This gives the perception of slowness when CApps are used, e.g. when you > are developing apps using DevStudio. Have we fixed this in the trunk so > that the artifact deployment also takes place in the first cycle itself. This is what we tried to address by directly calling particular deployers from the C-App deployer. But it didn't work for ESB artifacts due to the way ESB handles deployment. Please see the related thread on dev@. Therefore, I haven't committed that change in trunk. So still we are following the old deployment model in which the C-App deployer copies individual artifacts into particular hot directories. So always it will take two deployment cycles. First one for C-App and the second to individual artifacts. Thanks, ~Isuru > > > -- > *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* > > -- Isuru Suriarachchi Senior Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
