namedgraph commented on issue #2775: URL: https://github.com/apache/jena/issues/2775#issuecomment-2419413966
I like the modules idea but once again I would encourage to consider basing Fuseki on [JAX-RS](https://www.oracle.com/technical-resources/articles/java/jax-rs.html) which is a REST abstraction layer above the raw servlet API. I am familiar and quite satisfied with the [Jersey](https://eclipse-ee4j.github.io/jersey/) implementation. Tedious operations such as content negotiation would be supported by the framework out-of-the-box. Format (de)serializers would be easily pluggable in using providers and shared between the server- and the client-side. There's is definitely a larger number of users that would be familiar with JAX-RS as the HTTP framework than Jena's custom HTTP classes. Looks like classes such as this one would lend themselves well to a JAX-RS based refactoring: https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/servlets/ServletBase.java -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
