Hi,

Instead of adding service.xml file to .car we are going to add the content
of services.xml to dataservices config itself and in the deployment time
use the existing code to parse that content as services meta data.

Thanks


On Fri, Aug 15, 2014 at 9:00 AM, Chanika Geeganage <[email protected]> wrote:

> Hi Shameera,
>
> As discussed offline, in this suggested method we are not going to have an
> archive format (like .aar or .war) for dataservice config file (.dbs) and
> services.xml file inside the .car file. As I said in my previous mail this
> is going to be the dependency tree structure.
>
>
> testCar-1.0.0
>  |-- artifacts.xml
>  |-- SampleDataService_1.0.0
>         |-- artifacts.xml
>         |-- SampleDataService-1.0.0.dbs
>         |-- servicesMetaFiles
>                 |-- SampleDataService_service.xml
>                 |-- artifacts.xml
>
> Will this be OK to go ahead?
>
> Thanks
>
>
> On Thu, Aug 14, 2014 at 3:46 PM, Shameera Rathnayaka <[email protected]>
> wrote:
>
>> Hi Chanika,
>>
>> In Axis2 .aar file we use META-INF directory to keep the services.xml
>> file and in tomcat .war file there is WEB-INF to keep web.xml file, By
>> looking at the consistency it is better to keep services.xml file in a
>> separate directory .  And make sure to use proper name for the above
>> subdirectory.
>>
>> Thanks,
>> Shameera.
>>
>>
>>
>> On Wed, Aug 13, 2014 at 4:45 PM, Chanika Geeganage <[email protected]>
>> wrote:
>>
>>> Hi,
>>>
>>> There is a requirement to deploy dataservice configuration (.dbs) file
>>> with its corresponding services.xml using Capp. According to the current
>>> implementation, DefaultAppDeployer[1] calls .dsb files deployer. As the
>>> artifacts in the Capp are extracted and copied to a temporary location
>>> before deploying the services, we thought of changing the dataservice
>>> deployer code to pick the services.xml as well. So I tried to add the
>>> services.xml file as below to the car file.
>>>
>>> SampleCar-1.0.0
>>>  |-- artifacts.xml
>>>  |-- SampleDataService_1.0.0
>>>         |-- artifacts.xml
>>>         |-- SampleDataService-1.0.0.dbs
>>>         |-- SampleDataService_service.xml
>>>
>>>
>>>  But it seems only one file is allowed to have per a dependency.
>>> (SampleDataService is a dependency for the root artifact). It gives the
>>> following error.
>>>
>>> ERROR {org.wso2.carbon.application.deployer.handler.DefaultAppDeployer}
>>> -  service/dataservice type must have a single file. But 2 files found.
>>>
>>> Then the idea is to use the following dependency tree.
>>> testCar-1.0.0
>>>  |-- artifacts.xml
>>>  |-- SampleDataService_1.0.0
>>>         |-- artifacts.xml
>>>         |-- SampleDataService-1.0.0.dbs
>>>         |-- servicesMetaFiles
>>>                 |-- SampleDataService_service.xml
>>>                 |-- artifacts.xml
>>>
>>> We may need to change the dataservice code to lookup for
>>> servicesMetaFiles folder for services.xml file.
>>>
>>> Will this be a correct way to fulfill the requirement?
>>>
>>> Anyway in the future we will move to a single archive format to archive
>>> both dataservice config and the services.xml file.
>>>
>>> [1]
>>> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/handler/DefaultAppDeployer.java
>>>
>>> --
>>> Best Regards..
>>>
>>> Chanika Geeganage
>>> Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>>
>>>
>>
>>
>> --
>> *Software Engineer - WSO2 Inc.*
>> *email: shameera AT wso2.com <[email protected]> , shameera AT apache.org
>> <[email protected]>*
>> *phone:  +9471 922 1454 <%2B9471%20922%201454>*
>>
>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
>> *Twitter     : *https://twitter.com/Shameera_R
>>
>
>
>
> --
> Best Regards..
>
> Chanika Geeganage
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
>


-- 
Best Regards..

Chanika Geeganage
Software Engineer
WSO2, Inc.; http://wso2.com
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to