Perfect, this incremental work sounds much simpler. If we go with the approach
of servlets handling requests like an API backend, and the UI as client,
writing the Admin UI, or other UI's like a very minimalistic with only query
support, would be very simple.
>One especially I'd like is "reload" to reread the server setup and switchover
>live.
I think I've seen a few e-mails in the mailing list from users requesting it
too? Would it work even with reasoners? I think someone wanted to reload the
reasoner configuration without having to restart Jena.
Let me know what you want me to do with the existing PR. We can create a new
one if required. I'm just going to check the versions in package.json to see if
there's anything that can be updated.
Thanks Andy!
Bruno
On Tuesday, 9 February 2021, 1:55:41 am NZDT, Andy Seaborne
<[email protected]> wrote:
On 06/02/2021 07:04, Bruno P. Kinoshita wrote:
> Sounds good to me!
>
>
> Do you think we could consider the rewriting of the old Fuseki backbone.js
> UI? In a few days I will have confirmation about an extension of my current
> contract, working with Vue.js. If that is confirmed, I will have until at
> least June/2022 working with Vue.js, so I can easily dedicate some spare
> hours to maintain the new UI in case users find any issues or ask for
> improvements (unfortunately not using Jena at work, so not contributing a lot
> of Java code, sorry).
Good news about the contract!
We can do new UI incrementally - release the fuseki-ui module for use
with fuseki-main for the query/load-data. Leave the existing Fuseki/Full
webapp system in place for now then switch when ready.
This might be a good point to revisit the admin functions and create a a
new module for Fuseki/main. The admin API is looking a bit hodgepodge;
something slimmed down and focused; better expose the "loca config file"
which is in the network API not the UI.
It is not such a major task on the server side because the majority of
any new operations will be based on the components of the existing admin
controls.
One especially I'd like is "reload" to reread the server setup and
switchover live.
Andy
>
> Bruno
>
>
> On Saturday, 6 February 2021, 12:11:26 am NZDT, Andy Seaborne
><[email protected]> wrote:
>
> 3.17.0 was 2020-12-01
> so the usual timescale is end Feb - end March.
>
> Personally, I'd rather let it slip this time if there are any stability
> issues. That said, we've had a ticket reporting one bug due to clearup
> so some downstream is at least running with the latest code. (The
> version number in GIT and in JIRA isn't updated yet.)
>
> Jena4:
>
> * Java11 [done]
> the users@ feedback was this is enough to merit "jena4".
>
> * Rename default branch as "main"
>
> * Retire SDB
>
> * Retire jena-text-es
>
> * Deprecation cleanup [ongoing...]
>
> * IRIx abstraction
> (should this become package: org.apache.jena.iri?
> and rename the old one?)
> This may tighten up some illegal use of URIs (%XX -
> where XX is not hex).
>
> * jena-core: rename RDFReader as RDFReaderI
> and RDFWriter a RDFWriterI to avoid name clashes
>
> * Upgrades (except jetty 10/11 - wait until our Java11 move has gone OK)
>
> jena-elephas does not build on Java11.
>
> What else, especially things that are changes?
>
> As ever - contributions welcome!
>
> Andy
>
>
