Sadly, this was not the end of the story. I discovered that my fix posted
above did not work properly so I decided to bite the bullet and move to
shoreleave. This held the promise of using an edn reader.
A couple of things were tricky in making this migration, I'll list them
here for any future
Thanks for the support gents. Ever since Noir was deprecated I've been
planning to switch to compojure and shoreleave.
However I'm still in prototype mode and "it ain't broke" so I'm delaying
that work until I need the next level of stability.
Nice to know I'm on the right track though.
--
--
+1
fetch also has some bugs that will bite you sooner or later, it's not
maintained anymore (and I don't think anyone took over).
On Thursday, March 21, 2013 4:34:44 PM UTC+1, Paul deGrandis wrote:
>
> If you're up for the challenge, I'd encourage you to migrate from Noir to
> Compojure+Ring a
If you're up for the challenge, I'd encourage you to migrate from Noir to
Compojure+Ring and from Fetch to Shoreleave remotes.
I have much appreciation for Chris and his works,
but the recent additions of the EDN reader are in the latter stack
combination. You also get benefits like CSRF and XS
I found the solution and it's a bit of a noob mistake.
Because I'm using fetch, the server side of the RPC is defined in a noir
host page.
I added a :require of the view model ns to that page so that the classes
are loaded above read-string call in the stack.
This made it work immediately. Do
I'm building a single-page app ( started before Pedestal was announced
sadly ) and I'm using the fetch library to support RPC from client -> JVM
server.
I'm seeing a very strange behaviour. I've defined a view-model ns (full of
defrecords) for the client data. This has worked well - the client
