I see the underlying issue as an architectural one. Deploying in tomcat
or etc is deploying in the middle tier of application stack (in old
fashioned 3-tier language). Middle tier business logic is ideally
stateless code, using a DB or some bus to manage it's application state.
Fuseki is a database server; state (the database) is shared across
requests. It behaves like the database layer in that respect.
The configuration is startup state - getting that into a WAR file is, in
general, hard to make generic.
Rob found a useful looking approach for a generic WAR file. Building
your own WAR with the local config in it is also a possibility for now
Andy
On 04/05/12 21:43, Zhe Wu wrote:
Hi Rob,
Thanks for the speedy response!
BTW, congratulations to the whole Jena dev team for achieving a top
level apache project status!!!
Jena APIs are very important to Oracle's Database Semantic Technologies
product.
Zhe
Oracle
On 5/4/2012 1:33 PM, Robert Vesse wrote:
Hi Zhe
No there is not, as it stands Fuseki is not deployable as a WAR artifact.
There is an open issue JENA-201 [1] for this but there has not been
much progress lately. It is certainly doable but would require a
certain amount of work on the code. Contributions in this area are
always welcome.
Rob
[1] https://issues.apache.org/jira/browse/JENA-201
________________________________________
From: Zhe Wu [[email protected]]
Sent: 04 May 2012 13:24
To: [email protected]
Subject: is there a best practice document on deploying Fuseki in
Tomcat or WebLogic Server?
Hi,
I am wondering if there is a best practice document on deploying
Fuseki in Tomcat or WebLogic Server?
Thanks,
Zhe Wu
Oracle
