We cannot have repository/axis2Services, repository/axis2Modules. Those are
not based on deployers and the deployment is hard coded. When you specify
the axis2 repository, Axis2 automatically assumes a structure, and
automatically picks up directories such as lib under the repository. So,
like I mentioned earlier, my preference is,
repository/deployment/{services,modules,data-services etc.}

Azeez

On Wed, Feb 17, 2010 at 9:44 AM, Sanjiva Weerawarana <[email protected]>wrote:

> +1 to Ruwan's point .. repository/{axis2Services,axis2Modules,dataServices}
> etc.. Can we avoid camel casing? It looks weird for directory names ..
>
> While I understand Sameera's concern about familiarity with Axis2, I think
> given the breadth of the Carbon platform and given the different types of
> things we deal with, its fine to break the familiarity.
>
> Sanjiva.
>
> 2010/2/16 Ruwan Linton <[email protected]>
>
> Afkham Azeez wrote:
>> > +1 for removing artifacts dir, but I think we need to retain the axis2
>> > part.
>> Azeez, the problem with that model is, we need to add a synapse
>> directory into the repository as well, and may be an Ode directory.
>>
>> It is not logical to add mediators into a directory inside axis2, same
>> with bpel I guess.
>>
>> On a separate note, I have integrated a mediator deployer into carbon,
>> meaning you no longer have to go through the OSGi bundles to deploy a
>> mediator into the ESB, and it is being hot deployed.
>>
>> Thanks,
>> Ruwan
>> >
>> > Azeez
>> > On Tue, Feb 16, 2010 at 2:10 PM, Paul Fremantle <[email protected]
>> > <mailto:[email protected]>> wrote:
>> >
>> >     I know artifacts looks meaningful, but there is a completely
>> >     pointless extra directory - as you can see from the fact that
>> >     server only has artifacts in it.
>> >
>> >     Paul
>> >
>> >
>> >     On 16 February 2010 04:53, Sameera Jayasoma <[email protected]
>> >     <mailto:[email protected]>> wrote:
>> >
>> >
>> >
>> >         On Tue, Feb 16, 2010 at 10:13 AM, Isuru Suriarachchi
>> >         <[email protected] <mailto:[email protected]>> wrote:
>> >
>> >
>> >
>> >             On Tue, Feb 16, 2010 at 9:06 AM, Sumedha Rubasinghe
>> >             <[email protected] <mailto:[email protected]>> wrote:
>> >
>> >
>> >                 On Mon, Feb 15, 2010 at 4:09 PM, Afkham Azeez
>> >                 <[email protected] <mailto:[email protected]>> wrote:
>> >
>> >                     It should be
>> >
>> >                     repository
>> >                         |
>> >                         |- axis2
>> >                               |- server
>> >                                      |-artifacts
>> >                                            |- modules
>> >                                            |- services
>> >
>> >
>> >                 +1 .. This looks meaningful.
>> >
>> >                 Would it sound odd if we rename 'services' into
>> >                 'axis2services'?  Rationale is we will be having other
>> >                 deployer related folders (eg:
>> >                 dataservices,bpel,jsservice) here & 'services' along
>> >                 sound too abstract. (I know this was how we had before.)
>> >
>> >
>> >             'services' is the folder which is read by axis2 for .aar
>> >             services. Of course we can customize it using the
>> >             axis2.xml. But I think we have hard coded those folder
>> >             names inside our Carbon components. And also I think most
>> >             users (including axis2 users) are used to put .aars in
>> >             'services'. So I don't think it'll be a good idea to
>> >             rename it.
>> >
>> >
>> >         services is a familiar folder for Axis2 users. IMV, we better
>> >         keep the folder name as it is.
>> >
>> >         Sameera
>> >
>> >
>> >             Thanks,
>> >             ~Isuru
>> >
>> >
>> >
>> >                 /sumedha
>> >
>> >
>> >
>> >                     repository/axis2/server/repository looks weird so
>> >                     we decided to call
>> >                     it, repository/axis2/server/artifacts
>> >
>> >                     Azeez
>> >
>> >
>> >                     On Mon, Feb 15, 2010 at 3:27 PM, Isuru
>> >                     Suriarachchi <[email protected]
>> >                     <mailto:[email protected]>> wrote:
>> >
>> >
>> >
>> >                         On Mon, Feb 15, 2010 at 3:16 PM, Ruwan Linton
>> >                         <[email protected] <mailto:[email protected]>> wrote:
>> >
>> >                             Axis2 repo path is
>> >
>> >                             repository/axis2/service/artifacts
>> >
>> >
>> >                         I think this model was proposed during our
>> >                         discussion on refactoring Carbon folder
>> >                         structure (done by lahiru). "axis2" folder is
>> >                         to isolate axis2 related stuff as we have
>> >                         other OSGi stuff also in repository. "service"
>> >                         folder is to isolate the server side
>> >                         repository (however I think this should be
>> >                         'server' rather than 'service'). I think we
>> >                         have axis2/service and axis2/client. I'm not
>> >                         sure about what's the use of having the
>> >                         "artifacts" folder.
>> >
>> >                         Thanks,
>> >                         ~Isuru
>> >
>> >
>> >
>> >                             Why do we have service there??? :-(
>> >
>> >                             Thanks,
>> >                             Ruwan
>> >
>> >                             --
>> >                             Ruwan Linton
>> >                             Technical Lead & Product Manager; WSO2
>> >                             ESB; http://wso2.org/esb
>> >                             WSO2 <http://wso2.org/esb%0AWSO2> Inc.;
>> >                             http://wso2.org
>> >                             email: [email protected]
>> >                             <mailto:[email protected]>; cell: +94 77 341
>> 3097
>> >                             blog: http://blog.ruwan.org
>> >
>> >                             Lean . Enterprise . Middleware
>> >
>> >
>> >
>> _______________________________________________
>> >                             Carbon-dev mailing list
>> >                             [email protected]
>> >                             <mailto:[email protected]>
>> >
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>> >
>> >                         _______________________________________________
>> >                         Carbon-dev mailing list
>> >                         [email protected] <mailto:[email protected]
>> >
>> >
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>> >
>> >
>> >                     --
>> >                     --
>> >                     Afkham Azeez
>> >                     [email protected] <mailto:[email protected]>
>> >
>> >                     WSO2 Inc. http://wso2.com
>> >                     Blog: http://afkham.org
>> >
>> >                     _______________________________________________
>> >                     Carbon-dev mailing list
>> >                     [email protected] <mailto:[email protected]>
>> >
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>> >
>> >                 _______________________________________________
>> >                 Carbon-dev mailing list
>> >                 [email protected] <mailto:[email protected]>
>> >
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>> >
>> >             _______________________________________________
>> >             Carbon-dev mailing list
>> >             [email protected] <mailto:[email protected]>
>> >             https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>> >
>> >         _______________________________________________
>> >         Carbon-dev mailing list
>> >         [email protected] <mailto:[email protected]>
>> >         https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>> >
>> >
>> >     --
>> >     Paul Fremantle
>> >     CTO and Co-Founder, WSO2
>> >     OASIS WS-RX TC Co-chair, VP, Apache Synapse
>> >
>> >     Office: +44 844 484 8143
>> >     Cell: +44 798 447 4618
>> >
>> >     blog: http://pzf.fremantle.org
>> >     twitter.com/pzfreo <http://twitter.com/pzfreo>
>> >     [email protected] <mailto:[email protected]>
>> >
>> >     wso2.com <http://wso2.com> Lean Enterprise Middleware
>> >
>> >     _______________________________________________
>> >     Carbon-dev mailing list
>> >     [email protected] <mailto:[email protected]>
>> >     https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>> >
>> >
>> > --
>> > --
>> > Afkham Azeez
>> > [email protected] <mailto:[email protected]>
>> > WSO2 Inc. http://wso2.com
>> > Blog: http://afkham.org
>> > ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Carbon-dev mailing list
>> > [email protected]
>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>>
>>
>> --
>> Ruwan Linton
>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2 <http://wso2.org/esbWSO2> Inc.; http://wso2.org
>> email: [email protected]; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>>
>> Lean . Enterprise . Middleware
>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: [email protected]; phone: +1 408 754 7388 x51726; cell: +94 77 787
> 6880
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
--
Afkham Azeez
[email protected]
WSO2 Inc. http://wso2.com
Blog: http://afkham.org
_______________________________________________
Carbon-dev mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to