[Architecture] how to ship a Jaggery app as a feature?

Sun Mar 18 11:05:54 PDT 2012

Hi Nuwan,

Hold on, we don't need a new deployer for what I was suggesting. Right now,
how do you deploy a Jaggery application in GS? I assume you copy the *.jag
files to some location right? If so, nothing new is required. The feature
is only going to be a container that holds the *.jag files, when the
feature gets installed it will simply extract the *.jag files into the
relevant location by itself, so nothing additional is required.

Provided my assumptions about Jaggery applications today is correct, I can
very easily explain the structure of this "generic" feature that you can
use to bundle any Jaggery application on a whiteboard.

Thanks,
Senaka.

On Sun, Mar 18, 2012 at 4:34 PM, Nuwan Bandara <nuwan at wso2.com> wrote:

>
>
> On Sun, Mar 18, 2012 at 4:26 PM, Ruchira Wageesha <ruchira at wso2.com>wrote:
>
>> I think people might need to customize their UIs according to their
>> preferences. i.e. We will need to have something like exploded mode or if
>> it doesn't matter then, we can ask them to edit styles, *.jag files within
>> the jar??
>>
>> Other thing is, considering the API Store, we have custom hostobjects
>> written just for the app which aren't shipped with Jaggery core. If it is
>> the case, then we will also need to install relevant HO jars along with the
>> jaggery app.
>>
>
> Yes for sure to run a jaggery file, you will need to install the Jaggery
> features, what I meant is we wont have to write a new deployer or some
> sort.
>
> Regards,
> /Nuwan
>
>
>>
>> /Ruchira
>>
>>
>> On Sun, Mar 18, 2012 at 3:09 PM, Nuwan Bandara <nuwan at wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I guess there is a simpler solution, but need to try this out and see. :)
>>>
>>> Right now we have something called a JaggeryServlet (Like Jasper) what
>>> we are doing is that we register this servlet to any jaggery app via the
>>> Jaggery deployer. So we can do that same for carbon.
>>>
>>> Now since carbon is a web app we can easily register JaggeryServlet to
>>> carbon. and when the APIStore feature is installed using the feature
>>> manager, lets say APIstore bundle has a jaggery page called apistore.jag.
>>>
>>> the url for the file will be something like
>>>
>>> /carbon/apistore/apistore.jag
>>>
>>> So now since the sevlet is registered for /Carbon context this page will
>>> be picked up by the JaggeryServlet and will be rendered. So basically we
>>> can have jaggery files in our OSGi Bundle just like we have .jsp files.
>>>
>>> You dont need a special deployer for this.
>>>
>>> The down side is you dont have the benefits such as editing the jaggery
>>> file then and there like its deployed in a jaggery server (benifits of the
>>> directory based deployment).
>>>
>>> Regards,
>>> /Nuwan
>>>
>>> On Sun, Mar 18, 2012 at 11:17 AM, Sanjiva Weerawarana <sanjiva at wso2.com>wrote:
>>>
>>>> Yeah the issue is not about CAR file .. suppose I want the "API Store"
>>>> feature on G-Reg; how do you install that via the feature manager?
>>>>
>>>> Sanjiva.
>>>>
>>>>
>>>> On Sun, Mar 18, 2012 at 11:07 AM, Senaka Fernando <senaka at wso2.com>wrote:
>>>>
>>>>> Hi Sumedha,
>>>>>
>>>>> This makes it possible for us to package a Jaggery application and
>>>>> host it on P2 repository, and additionally that feature can require any
>>>>> number of feature (P2 I mean) dependencies. Thereby, you can even install
>>>>> that feature on a system that did not ship Jaggery OOTB. Nothing else
>>>>> changes, and the same can be done for .CAR files.
>>>>>
>>>>> Also, there is no involvement of deployer, media type and registry in
>>>>> this. It is the equivalent of someone just copying the required Jaggery app
>>>>> into the right location of the filesystem and starting a server like GS
>>>>> which already ships with the Jaggery features.
>>>>>
>>>>> Also, the problem is generic but much more related to a Jaggery
>>>>> application, because most products does not ship the Jaggery feature OOTB,
>>>>> and there is no one-step deployment option as in a .car file (or any
>>>>> other). Also, Jaggery applications tend to have BE OSGi bundles and or
>>>>> feature-dependencies unlike other deployable artifacts.
>>>>>
>>>>> Thanks,
>>>>> Senaka.
>>>>>
>>>>> On Sun, Mar 18, 2012 at 10:50 AM, Sumedha Rubasinghe <sumedha at wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Why are we not talking about CAR here?
>>>>>> And isn't this a generic problem applicable for war, service,
>>>>>> workflow, gadget, etc.
>>>>>>
>>>>>> On 3/18/12, Sanjiva Weerawarana <sanjiva at wso2.com> wrote:
>>>>>> > I can't get my head around this yet .. how would $subject work?
>>>>>> Would we
>>>>>> > need a new deployer that takes the app's files and copies it into
>>>>>> > jaggeryapps/ after pre-req'ing the Jaggery feature to the server?
>>>>>> Or would
>>>>>> > we write a new deployer than runs the pages directly from the
>>>>>> bundle?
>>>>>> >
>>>>>> > We need to be able to ship Jaggery apps as features. For example,
>>>>>> in the
>>>>>> > API Management stuff we want to have 3 features: store, provider,
>>>>>> manager
>>>>>> > apps.
>>>>>> >
>>>>>> > Sanjiva.
>>>>>> > --
>>>>>> > Sanjiva Weerawarana, Ph.D.
>>>>>> > Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>>>>>> > email: sanjiva at wso2.com; phone: +94 11 763 9614; cell: +94 77 787
>>>>>> 6880 | +1
>>>>>> > 650 265 8311
>>>>>> > blog: http://sanjiva.weerawarana.org/
>>>>>> >
>>>>>> > Lean . Enterprise . Middleware
>>>>>> >
>>>>>>
>>>>>> --
>>>>>> Sent from my mobile device
>>>>>>
>>>>>> /sumedha
>>>>>> +94 773017743
>>>>>> _______________________________________________
>>>>>> Architecture mailing list
>>>>>> Architecture at wso2.org
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Senaka Fernando*
>>>>>
>>>>> Product Manager - WSO2 Governance Registry;
>>>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com
>>>>> *
>>>>> Member; Apache Software Foundation; http://apache.org
>>>>>
>>>>> E-mail: senaka AT wso2.com
>>>>> *
>>>>> *P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>>>> Linked-In: http://linkedin.com/in/senakafernando
>>>>>
>>>>> *
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> Architecture at wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Sanjiva Weerawarana, Ph.D.
>>>> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>>>> email: sanjiva at wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880| +1
>>>> 650 265 8311
>>>> blog: http://sanjiva.weerawarana.org/
>>>>
>>>> Lean . Enterprise . Middleware
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> Architecture at wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> *Thanks & Regards,
>>>
>>> Nuwan Bandara
>>> Senior Software Engineer
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> http://nuwan.bandara.co
>>> *
>>> <http://www.nuwanbando.com/>
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> Architecture at wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Ruchira Wageesha
>> Software Engineer - WSO2 Inc. www.wso2.com
>>
>> Email: ruchira at wso2.com Blog: ruchirawageesha at blogspot.com
>> Mobile: +94775493444
>>
>>
>> Lean . Enterprise . Middleware
>>
>> _______________________________________________
>> Architecture mailing list
>> Architecture at wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> http://nuwan.bandara.co
> *
> <http://www.nuwanbando.com/>
>
> _______________________________________________
> Architecture mailing list
> Architecture at wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>

-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/architecture/attachments/20120318/5c99206c/attachment-0001.html>