Hi Nisala and Kasun,

Great. This will help us to include AS6 as a jaggery runtime in AppCloud.

thank you.

On Mon, Jul 4, 2016 at 3:04 PM, KasunG Gajasinghe <kas...@wso2.com> wrote:

>
>
> On Mon, Jul 4, 2016 at 1:48 PM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi Manjula,
>>
>> Yes.Jaggery support will be inbuilt into the server with the release of
>> AS-6.0.0 next milestone. This email and documentation is provided to inform
>> the procedure of running jaggery apps in a pure tomcat server, not in the
>> AS-6.0.0. I will update the finalized documentation and configuration
>> details for AS-6.0.0 in a separate mail thread, once we finished the
>> fine-tuning process.
>>
>> Thanks,
>> Nisala
>>
>> On Mon, Jul 4, 2016 at 1:39 PM, Manjula Rathnayake <manju...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> IIUC, when we release the next AS-6.0.0 milestone, jaggery support is
>>> inbuilt into the server. And users do not need to follow above instructions
>>> to copy jars etc. Please correct If it is not.
>>>
>>
> Yes, that's the case. So, we need separate documentation on how to deploy
> Jaggery apps in AS6 as well.
>
>
>>
>>> thank you.
>>>
>>> On Mon, Jul 4, 2016 at 12:42 PM, Sinthuja Ragendran <sinth...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Anyhow ultimately when all the carbon products move to AS 6.0 based
>>>> platform, we can merge all those into one.
>>>>
>>>> Thanks,
>>>> Sinthuja.
>>>>
>>>> On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara <nis...@wso2.com>
>>>> 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 <kas...@wso2.com>
>>>>> 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 <nis...@wso2.com>
>>>>>> 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
>>>>>>> Dev@wso2.org
>>>>>>> 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
>>>>> Dev@wso2.org
>>>>> 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
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> architect...@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Manjula Rathnayaka
>>> Associate Technical Lead
>>> WSO2, Inc.
>>> Mobile:+94 77 743 1987
>>>
>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile:(+94)717600022
>> WSO2 Inc., http://wso2.com/
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org
>> 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
>
>
>



-- 
Manjula Rathnayaka
Associate Technical Lead
WSO2, Inc.
Mobile:+94 77 743 1987
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to