Hi Ramith,
On Fri, Aug 23, 2013 at 11:43 AM, Ramith Jayasinghe <[email protected]> wrote: > Hi, > Our intention is to implement (get that running) a basic issue tracking > system very quickly in Java. > Am not sure how it can be done quickly in java rather than writing few scripts in js, however, > And I don't think it's our intention to write a fully-fledged issue > tracking system (e.g. Jira,redmine) > > Therefore from our point of view the REST API (and back end functionality > required) could be achieved via couple of DAOs and some nicely placed > JaxRs annotations. :) > DAO ??? do an SQL query (in jaggery) and get a json object; pass it to the browser and render it in html; simple as that. > and we will use caramel for the UI part. > Caramel/jaggery is not a UI framework, it runs in the server. its a serverside app development framework so if you are writing some part of it in java might as well write the rest in java too. But that's not the case, we are using jaggery for a reason. mainly for the ease of customization/skinning/packaging/deployment etc. above all to reduce the conversion of data back and forth. > If there are advantages of having the REST API in jaggery than our > approach lets go for it. > I do think for a web application like an "issue tracker" there is a massive advantage of going all in with jaggery. An issue tracker is not something limited to appfactory, it will be ultimately shipped with APIManager, Enterprise Store, Mobile MDM etc. where all those are written completely in jaggery. > Yea, Lets do a architecture review. > +1 Regards, /Nuwan > > > > > > On Thu, Aug 22, 2013 at 10:47 PM, Nuwan Bandara <[email protected]> wrote: > >> Hi All, >> >> Today I was looking at issue tracker code at [1] and found that all rest >> apis are written in JAX-RS. What is the reason to do this. IFAIK, you are >> implementing the tracker in jaggery, so why only the REST api in java ? I >> don't think this is consistent with our story. If you look at [2] there is >> a clear way of (of cause we can improve) writing a rest api completely in >> javascript. can we please have an architecture review on this, or was there >> a review and came to this conclusion (maybe I missed the mail) based on a >> specific reason ? >> >> Regards, >> /Nuwan >> >> [1] https://github.com/wso2/issue-tracker >> [2] >> https://github.com/wso2/enterprise-store/blob/master/modules/apps/publisher/apis/v1/asset_api_router.jag >> >> >> On Thu, Aug 22, 2013 at 5:08 PM, Manuranga Perera <[email protected]> wrote: >> >>> there shouldn't be two unique ways to identify a issue. >>> Issue ID itself should be a unique key (possible a String). >>> >>> >>> >>> On Thu, Aug 22, 2013 at 6:17 AM, Nihanth Joseph <[email protected]>wrote: >>> >>>> Hi Ramith, >>>> To process Issue details, are we going to pass issue id or unique key >>>> (String) of issue? >>>> if we are passing unique key then in-order to add/ get/ update/ delete >>>> comments we have to do two DB calls, first call to get issue id for unique >>>> key and second one is for real purpose (add/ delete/ edit/ delete comments) >>>> which one is better way? >>>> >>>> >>>> On Fri, Aug 16, 2013 at 10:25 AM, Ramith Jayasinghe <[email protected]>wrote: >>>> >>>>> Nope. >>>>> I don't think we required versioned url as of now. >>>>> >>>>> >>>>> >>>>> On Fri, Aug 16, 2013 at 12:46 AM, Shameera Rathnayaka < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Ramith, >>>>>> >>>>>> Is this REST url schema has versioning support? >>>>>> >>>>>> Thanks, >>>>>> Shameera. >>>>>> >>>>>> >>>>>> On Wed, Aug 14, 2013 at 6:42 PM, Ramith Jayasinghe >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> Hi, >>>>>>> This is what we propose as the URL scheme for issue tracking >>>>>>> component we are writing. >>>>>>> >>>>>>> GET /issue/<id> -- Returns information about an issue. >>>>>>> POST /issue/<id>/ -- modifies an existing issue. >>>>>>> >>>>>>> POST /issue/<id>/comment -- adds new comment to an issue >>>>>>> POST /issue/<id>/comment/<id> -- modifies an existing comment >>>>>>> >>>>>>> DELETE /issue/<id>/comment/<id> -- deletes a existing comment >>>>>>> >>>>>>> >>>>>>> GET /project -- returns a list of projects for the organization >>>>>>> GET /project/<id> --- gets information about project >>>>>>> >>>>>>> >>>>>>> POST /project/ -- adds a new project >>>>>>> POST /project/<id> -- edits information of an exiting project >>>>>>> >>>>>>> GET /project/<id>/version -- list of versions of the project >>>>>>> GET /project/<id>/issue -- list of issues of the project >>>>>>> >>>>>>> >>>>>>> POST /project/<id>/issue/ -- add a new issue to an project. >>>>>>> >>>>>>> >>>>>>> These are only the basic operations we might need (we will devise >>>>>>> URL as we go along for other use cases). >>>>>>> Note that above URLs don't have organization Id included. >>>>>>> >>>>>>> WDYT? >>>>>>> >>>>>>> >>>>>>> >>>>>>> regards >>>>>>> Ramith >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Software Engineer - WSO2 Inc.* >>>>>> *email: shameera AT wso2.com <[email protected]> , shameera AT >>>>>> apache.org <[email protected]>* >>>>>> *phone: +9471 922 1454* >>>>>> * >>>>>> * >>>>>> *Linked in : * >>>>>> http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>>>>> *Twitter : *https://twitter.com/Shameera_R >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Ramith Jayasinghe >>>>> Technical Lead >>>>> WSO2 Inc., http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> E: [email protected] >>>>> P: +94 776715671 >>>>> >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nihanth Joseph >>>> Senior Software Engineer >>>> Mob: +94719187136 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> With regards, >>> *Manu*ranga Perera. >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Thanks & Regards, >> >> Nuwan Bandara >> Technical Lead; **WSO2 Inc. * >> *lean . enterprise . middleware | http://wso2.com * >> *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 >> 9629 >> * >> <http://www.nuwanbando.com/> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Ramith Jayasinghe > Technical Lead > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > E: [email protected] > P: +94 776715671 > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Thanks & Regards, Nuwan Bandara Technical Lead; **WSO2 Inc. * *lean . enterprise . middleware | http://wso2.com * *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 9629 * <http://www.nuwanbando.com/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
