On Mon, Mar 26, 2012 at 11:48 AM, Yumani Ranaweera <yum...@wso2.com> wrote:
> > > On Sat, Mar 24, 2012 at 12:01 PM, Kasun Gajasinghe <kas...@wso2.com>wrote: > >> >> >> On Sat, Mar 24, 2012 at 9:43 AM, Shammi Jayasinghe <sha...@wso2.com>wrote: >> >>> Hi MS RMs, >>> >>> Could you please have a look in to the MS test failures. >>> >> >> I will help MS RMs to overcome this issue. >> >> I have few questions. >> How does web services like sessionTest.js are treated within Carbon? Is >> that also treated as an AxisService, as same as proxy services, jax-ws >> services, and real axis2 services are treated? This is a jaggery app, >> right? If so, what would be the differences of jaggery apps compared to >> other web service types? Does sessionisTest.js is a jaggery app? If >> > > MS doesn't have jaggery apps. The .js extension is for JavaScript web > services. > > >> >> Further, I see that the names of these test web services are like >> - admin/upgradeChecker. What does "/" denote? >> Why these are deployed >> inside repository/deployment/server/jsservices/admin/ instead >> of repository/deployment/server/jsservices/ ? >> This is where the services are deployed - >> wso2ms-2.3.0-SNAPSHOT/repository/deployment/server/jsservices/admin/sessionTest.js >> > > AFAIU, MS deploys services based on their owners and that's why you get > admin/sessionTest.js. > Thanks Yumani. Just what I needed to hear. Current implementation isn't flexible to handle cases like this where services are persisted in separate folders of owners. There can be same service between multiple users too that need to be handled properly, right? So, as a solution, I'm thinking of persisting these contents by creating separate folders for owners inside servicesmetafiles. ex. wso2ms-2.3.0-SNAPSHOT/repository/deployment/server/* servicemetafiles/admin*/sessionTest.js For that I need to understand the logic behind how the location is calculated. Please share if you can point to relevant code segment. Thanks, --KasunG > > > >> I know it's a lot of questions, but those will help to understand the >> IOExceptions in integration tests. >> >> Thanks, >> --KasunG >> >> >>> Thanks >>> >>> Shammi >>> >>> On Sat, Mar 24, 2012 at 9:23 AM, Bamboo <cbuil...@wso2.org> wrote: >>> >>>> [image: Failed] WSO2 >>>> Carbon<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON/>› WSO2 >>>> MS <http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-MS/> › >>>> #12 <http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-MS-12/> >>>> failed >>>> >>>> This build was manually triggered by >>>> BambooBuilder<http://builder4.us1.wso2.org:8888/bamboo/browse/user/bamboo_builder> >>>> . >>>> >>>> No failed tests found, a possible compilation error. >>>> Failing >>>> Jobs<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-MS-12/> >>>> Job >>>> Duration Tests [image: Failed] Default >>>> Job<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-MS-JOB1-12/> >>>> (Default >>>> Stage) 9 minutes No tests found >>>> Logs<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-MS-JOB1-12/log>| >>>> Artifacts<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-MS-JOB1-12/artifact> >>>> View >>>> Online<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-MS-12> >>>> | Add >>>> Comments<http://builder4.us1.wso2.org:8888/bamboo/browse/WSO2CARBON-MS-12?commentMode=true> >>>> >>>> This message was sent by Atlassian >>>> Bamboo<http://builder4.us1.wso2.org:8888/bamboo> >>>> . >>>> >>>> If you wish to stop receiving these emails edit your user >>>> profile<http://builder4.us1.wso2.org:8888/bamboo/profile/userNotifications.action>or >>>> notify >>>> your >>>> administrator<http://builder4.us1.wso2.org:8888/bamboo/viewAdministrators.action> >>>> . >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Best Regards,* >>> >>> Shammi Jayasinghe* >>> Senior Software Engineer; WSO2, Inc.; http://wso2.com, >>> mobile: +94 71 4493085 >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Kasun Gajasinghe* >> Software Engineer; WSO2 Inc.; http://wso2.com >> >> , >> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* >> *linked-in: *http://lk.linkedin.com/in/gajasinghe* >> * >> *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org> >> >> * >> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> >> >> * >> * >> >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Yumani Ranaweera > Associate Technical Lead - QA > WSO2, Inc. - http://wso2.org > > Email : yum...@wso2.com > Cell : +94 077 7795242 > Blog : http://yumani.blogspot.com/ > > -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org> * twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> * *
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
