Genome annotation editor, with a Java servlet backend and a Javascript client that runs in a web browser as a JBrowse plugin
never mind . . I see that you do . . sorry.
@nathandunn is the "findAllOrganisms" web services endpoint available via web sockets? I've been trying this:
client.publish({
destination: '/app/AnnotationNotification',
body: JSON.stringify({ operation: 'find_all_organisms' }),
})but I get the message "Operation findAllOrganisms not found"
it won’t be at this point because only RequestHandlingService methods are available
we woul dhave to write an end-point.
@garrettjstevens that took a scope (organism) and an operation (find_all_organisms). However, that is one where there shouldn’t necessarily be a reason to do it that way unless we were pushing updates organisms. Not an operation that happens often. Typically we only supported real-time annotation editing. Right now only
getFeatures is a problem.
My goal today is to get a dev environment working with react and grails (spring) with authentication . .. we’ll see where I get
I’m fairly convinced that you can use react dev mode with a localhost proxy against grails and everything will work (today’s work). I don’t think with using the current security scheme with Apollo 2 / Spring you’ll be able to authenticate in a production environment across domains.
basically the websocket comes in and its not associated with any session . . . I need to redo the examples so that I am testing routes with a session . . . even when I was building it locally it wasn’t getting the session
maybe we can come back to it once I get that connected
@rbuels it would be worth reading through all of the comments, but this in particular: https://github.com/GMOD/Apollo/pull/2598#issuecomment-811445444
But I feel that we can probably get hot-reload working . . .
I think you simply add, "proxy":"http://localhost:8080/apollo”, and it seems to get the JSESSIONID properly when using http://localhost:3000/apollo (or whatever)
that's equivalent to having jb2 served by the apollo server the same way that jb1 is
and you get the cookie and things just work, etc
but even in the toy problems I need to go back and see what that minimal set is to make sure it gets a session
bound to a thread on the server-side
right now we only have a baseline for getting around CORS via a web socket
but its not connecting to the server in a useful way since it isn’t binding to the current user even with the JSESSIONID . .. I’m sure its pretty tractable, I just need to go back over the current codebase and figure out what I’m doing wrong. Then we can see where we can take it from there.
since I know it already works from dojo-land
@garrettjstevens this is ready: garrettjstevens/apollo-websocket-test#2 . . . it just has the ajax versus the websocket login and logout . . but I support both
with the newer server code
Also done with these fixes as well
though going to test another AJAX query once queried authenticated
you can push them as if you are good with them
@cross12tamu . . . I'm not sure I catch your drift. Do you want Apollo logos or a way to brand your Apollo differently from the apollo logos?