@propensive I'm using embedded Jetty as a web server for legacy reasons.
-
-
Replying to @cosmicvisitors
@propensive It uses a JAXB context with Jettison as the default JSON engine. I'd like to try a new engine if possible.1 reply 0 retweets 0 likes -
Replying to @cosmicvisitors
@cosmicvisitors Do you know what's involved in writing a "JSON engine"?1 reply 0 retweets 0 likes -
Replying to @propensive
@cosmicvisitors Is it a typeclass-like thing? It might be straightforward to wrap the Jettison one and provide a Rapture one, but note sure.1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive basically, it should be a JAXB provider. There are tutorials on how to do this for e.g. Moxy, but haven't found any for Rapture?1 reply 0 retweets 0 likes -
Replying to @cosmicvisitors
@cosmicvisitors Yeah, there won't be any... Is JAXB basically an interface? Just looking for a spec now...1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive wikipedia: Java Architecture for XML Binding (JAXB). It's basically a JDK mapper from POJO <-> XML/JSON/etc2 replies 0 retweets 0 likes -
-
Replying to @propensive
@propensive If Rapture could somehow register its interface with JAXB, it could replace other engines for JAXB serialisation2 replies 0 retweets 0 likes -
Replying to @cosmicvisitors
@cosmicvisitors I'm not sure Rapture needs to interact with JAXB - that's working at a lower level.1 reply 0 retweets 0 likes
@cosmicvisitors Put another way, whatever Jettison does with JAXB, Rapture needs to do exactly the same, plus those wrappers I sent before.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.