Hi Jayanga, I wonder this approach would help us. There could be lot of issues.
Why not thinking of introducing a meta file which represents basic set of information that you require in order to generate these assets? Then the relevant components would need to configure this meta file, if it wants to be registered as an asset. On Tue, Feb 4, 2014 at 10:17 PM, Jayanga Dissanayake <[email protected]>wrote: > Hi Udara, > > Agreed with your point. > Its not just enough to have a file having the name 'services.xml' to > create a service assert. > > We have to read the file and get the service name and other information > from the file. > As Axis2 support <serviceGroup>, A single 'services.xml' file sometimes > may contain information about several services, hence several service > assert instances may have to be created. > > Thanks, > > *Jayanga Dissanayake* > Senior Software Engineer > WSO2 Inc. - http://wso2.com/ > lean . enterprise . middleware > email: [email protected] > mobile: +94772207259 > > > On Tue, Feb 4, 2014 at 8:43 PM, Udara Liyanage <[email protected]> wrote: > >> Let's say a service.XML is found but without any service definition. Is >> it still a axis2 service? >> >> Touched, not typed. Erroneous words are a feature, not a typo. >> > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Thanks & regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
