On Mon, Jul 4, 2016 at 12:42 PM, Sinthuja Ragendran <[email protected]> wrote:
> Hi, > > Anyhow ultimately when all the carbon products move to AS 6.0 based > platform, we can merge all those into one. > Since, Carbon products will still be OSGi based using the embedded Tomcat, Jaggery needs to support that as well. As I understood, the deployment part differs mainly. ie. for AS6, you are using a LifecycleListener; for Carbon, you have the JaggeryDeployer. The rest can stay the same to a great extent. So, it's better if these two can be merged into a single branch. Thanks, KasunG > Thanks, > Sinthuja. > > On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara <[email protected]> > wrote: > >> Hi Kasun, >> >> Yes.We can do a performance round. Currently we manage the Tomcat >> Jaggery/ AS6 support code base under a new branch [1] in our jaggery >> repository. Current jaggery is based on tomcat version 7 and Tomcat Jaggery >> implementation is based on tomcat version 8. So there are some api changes >> in the jaggery level. So it is difficult to manage these codebases in same >> place. >> >> Thanks, >> Nisala >> >> On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe <[email protected]> >> wrote: >> >>> >>> Good work Nisala. >>> >>> Can we also do a performance round to see whether there are any perf >>> gains when running Jaggery apps in vanilla Tomcat/AS6? >>> >>> How are you going to manage the codebase for Carbon vs Tomcat Jaggery >>> support? Better if we can maintain it in the same place. >>> >>> On Sat, Jul 2, 2016 at 12:51 PM, Nisala Nanayakkara <[email protected]> >>> wrote: >>> >>>> Hi all, >>>> >>>> This is an update regarding the feature 'Provide Support to run Jaggery >>>> apps in Tomcat Server'. >>>> >>>> At present Jaggery scripts can only be executed in a jaggery server. >>>> Because Jaggery Server which is powered by WSO2 carbon OSGi Runtime, is the >>>> Runtime Environment that hosts Jaggery applications. The goal of this >>>> feature is to provide support to run jaggery apps in a pure tomcat server >>>> without any modifications to the jaggery apps.This will enable developers >>>> to write Jaggery scripts and directly deploy them in apache tomcat server. >>>> So this will improve the flexibility of the jaggery apps. >>>> >>>> This is an extension for the Apache tomcat 8 to run the jaggery app >>>> without modifying it. Although this is implemented as a requirement of WSO2 >>>> Application Server 6, Users who want to run jaggery apps without jaggery >>>> server, can use this feature to run their jaggery apps in Apache tomcat >>>> server. >>>> >>>> I have attached the documentation and sample jaggery with this email. >>>> Please find these attachments and relevant jaggery branch here[1]. Please >>>> feel free to ask any questions. >>>> >>>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery >>>> >>>> Thanks, >>>> Nisala >>>> >>>> -- >>>> *Nisala Niroshana Nanayakkara,* >>>> Software Engineer >>>> Mobile:(+94)717600022 >>>> WSO2 Inc., http://wso2.com/ >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> >>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. >>> email: kasung AT spamfree wso2.com >>> linked-in: http://lk.linkedin.com/in/gajasinghe >>> blog: http://kasunbg.org >>> >>> >>> >> >> >> >> -- >> *Nisala Niroshana Nanayakkara,* >> Software Engineer >> Mobile:(+94)717600022 >> WSO2 Inc., http://wso2.com/ >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Sinthuja Rajendran* > Technical Lead > WSO2, Inc.:http://wso2.com > > Blog: http://sinthu-rajan.blogspot.com/ > Mobile: +94774273955 > > > -- *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
