<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div> patternfly for the UI?<br><br><div><span style="background-color: rgba(255, 255, 255, 0);">Thanks,</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Brad Davis</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Director of FSI Solutions, Red Hat</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Email: <a href="mailto:bdavis@redhat.com" target="_blank">bdavis@redhat.com</a> | c: <a dir="ltr" href="tel:980.226.7865" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="0/2">980.226.7865</a> | <a href="http://www.redhat.com/" target="_blank">http://www.redhat.com</a> </span></div></div><div><br>On Jul 1, 2016, at 9:45 PM, Ondrej Zizka <<a href="mailto:ozizka@redhat.com">ozizka@redhat.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span>+1 to getting this straight before getting deep into Windup 3.</span><br><span></span><br><span>To those 4 approaches in the document, I would suggest one more.</span><br><span>Kind of a hybrid.</span><br><span></span><br><span>The point of this, I assume, is to reduce the repetitive patterns in the </span><br><span>chain: graph -> Java Model -> Java service -> DTO -> REST -> JSON -> TS </span><br><span>service -> JS model -> Angular 2.</span><br><span>So we should reuse the information already contained somewhere.</span><br><span></span><br><span>The most frequent scenarios I can forsee are:</span><br><span></span><br><span>1) Query by property, get the resulting objects, optionally with some </span><br><span>nested objects.</span><br><span>2) Start with a set of objects, query some other objects in some </span><br><span>relation to those.</span><br><span>3) Start with one object and get a tree starting with that object, based </span><br><span>on some recursive relation.</span><br><span>4) More complex queries.</span><br><span></span><br><span>I suggest to stick with something simple, so for 4), we could have </span><br><span>custom services.</span><br><span></span><br><span>For 1) 2) 3), we could have a simple "URL to objects" schema, not trying </span><br><span>to be a generic query tool.</span><br><span>It could reuse the Models.</span><br><span>Examples (made up):</span><br><span>1) /graph/File{path=...}!out:fileToProject,getClassifications,:... </span><br><span>-- File objects with given properties with objects from relations </span><br><span>defined behind ! attached to it.</span><br><span>2) /graph/Project/id=[1,2,3]/out:projectToFile/{path=...}</span><br><span>3a) /graph/Project/id=1//in:parent!out:fileToProject -- will query </span><br><span>what's under that relation</span><br><span>3b) /graph/Project/id=1//in:parent!getProjects -- will use the method </span><br><span>to attach the objects.</span><br><span></span><br><span>Maybe it's quite similar to what's proposed in the doc under 4, only a </span><br><span>bit more type oriented, and also more use-case oriented and less generic.</span><br><span></span><br><span>my2c.</span><br><span>Ondra</span><br><span></span><br><span></span><br><span>On 1.7.2016 23:28, Jess Sightler wrote:</span><br><blockquote type="cite"><span>I don't think we ever discussed this in the Thursday meeting. My mic</span><br></blockquote><blockquote type="cite"><span>problems probably didn't help with that (sorry about that). I have</span><br></blockquote><blockquote type="cite"><span>started a document to discuss a few different approaches to building</span><br></blockquote><blockquote type="cite"><span>REST services for the web application.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Keep in mind the following high level requirements:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> - Support querying of data easily for both the global configuration</span><br></blockquote><blockquote type="cite"><span>graph (eg, projects, groups etc) as well as for the individual graphs</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> - Support persisting new data to the graph for the configuration graph</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> - Support easy marshalling to/from ECMAScript objects</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I have added these to the document as well:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span><a href="https://docs.google.com/document/d/1jJz-NuTI00A7VcP7K58Gv6sWGyC8CuMsc5MVldRrc6Y/edit#heading=h.9hob5uguvtqc">https://docs.google.com/document/d/1jJz-NuTI00A7VcP7K58Gv6sWGyC8CuMsc5MVldRrc6Y/edit#heading=h.9hob5uguvtqc</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Feel free to add your thoughts as well.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Thanks,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Jess</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On 06/26/2016 07:26 PM, Ondrej Zizka wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>Hi devs,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>How about creating a layer that would query the graph based on a REST URL?</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I.e. instead of creating a REST endpoint for each service, we could do</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>something like</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>localhost//windup/rest/graph/ProjectModel/id-48984/out-projectTofile/with-...</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Or some subset of Gremlin perhaps...</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Just an idea.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Ondra</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>_______________________________________________</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>windup-dev mailing list</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="https://lists.jboss.org/mailman/listinfo/windup-dev">https://lists.jboss.org/mailman/listinfo/windup-dev</a></span><br></blockquote></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>windup-dev mailing list</span><br></blockquote><blockquote type="cite"><span><a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a></span><br></blockquote><blockquote type="cite"><span><a href="https://lists.jboss.org/mailman/listinfo/windup-dev">https://lists.jboss.org/mailman/listinfo/windup-dev</a></span><br></blockquote><span></span><br><span>_______________________________________________</span><br><span>windup-dev mailing list</span><br><span><a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/windup-dev">https://lists.jboss.org/mailman/listinfo/windup-dev</a></span><br></div></blockquote></body></html>