You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Eric Scott <er...@att.net> on 2011/12/28 19:41:09 UTC
Fuseki directory structure
I'm playing with Fuseki, and I have a question about the purpose of the
./pages-publish directory.
It would seem that one can invoke fuseki-server, and the server will
automatically serve content held in the ./pages-update directory. Many
of the pages contained in that directory by default also have namesakes
in ./pages-publish, but editing ./pages-publish has no effect on what
the server provides as far as I can tell.
So what purpose, if any, does ./pages-publish serve?
Also, is the location of html/jsp/etc content referenced by the server
configurable? If so, how?
Thanks,
Re: Fuseki directory structure
Posted by Andy Seaborne <an...@apache.org>.
Eric,
Some checking reveals that Fuseki always uses the pages-publish/
directory currently. This is crude kludge to mean a configuration file
of a mix of read-only and updateable datasets will work (and then only
if it uses the right service names).
The generation of pages needs rewriting so it works with the config
file. The kludge made something work at the time ... then the release
work started and this got elbowed out.
It's
https://issues.apache.org/jira/browse/JENA-113
Andy
PS the current development version, used with TDB, is properly
transactional.
On 29/12/11 21:12, Eric Scott wrote:
> Fuseki: VERSION: 0.2.1-SNAPSHOT
> Fuseki: BUILD_DATE: 2011-09-15T08:18:13+0100
>
> Right now my command line is just: fuseki-server --mem /dataset
>
> If I understand you correctly calling it without the --update option
> should reference the ./pages-publish directory?
>
> In fact, the only edits that get rendered are in the ./pages-update
> directory, even when I invoke without the --update option.
>
>
> On 12/29/2011 10:40 AM, Andy Seaborne wrote:
>> On 28/12/11 18:41, Eric Scott wrote:
>>> I'm playing with Fuseki, and I have a question about the purpose of the
>>> ./pages-publish directory.
>>>
>>> It would seem that one can invoke fuseki-server, and the server will
>>> automatically serve content held in the ./pages-update directory. Many
>>> of the pages contained in that directory by default also have namesakes
>>> in ./pages-publish, but editing ./pages-publish has no effect on what
>>> the server provides as far as I can tell.
>>>
>>> So what purpose, if any, does ./pages-publish serve?
>>>
>>> Also, is the location of html/jsp/etc content referenced by the server
>>> configurable? If so, how?
>>>
>>> Thanks,
>>>
>>
>> Eric,
>>
>> This may depend on the version you're running.
>>
>> Before configuration-by-file was added, the server had two modes:
>> "publishing" (read-only) and "update" (read-write). When publishing
>> all update possibilities were turned off.
>>
>> The pages-publish/ are supposed to be the web pages for publishing
>> more and pages-update/ for when the server is running with update.
>>
>> When using a configuration file, there are more possible setups and
>> the server does not distinguish which set of pages to use.
>>
>> How are you running the server and which version? (use "-version" to
>> tell you).
>>
>> Andy
>>
>
Re: Fuseki directory structure
Posted by Eric Scott <er...@att.net>.
Fuseki: VERSION: 0.2.1-SNAPSHOT
Fuseki: BUILD_DATE: 2011-09-15T08:18:13+0100
Right now my command line is just: fuseki-server --mem /dataset
If I understand you correctly calling it without the --update option
should reference the ./pages-publish directory?
In fact, the only edits that get rendered are in the ./pages-update
directory, even when I invoke without the --update option.
On 12/29/2011 10:40 AM, Andy Seaborne wrote:
> On 28/12/11 18:41, Eric Scott wrote:
>> I'm playing with Fuseki, and I have a question about the purpose of the
>> ./pages-publish directory.
>>
>> It would seem that one can invoke fuseki-server, and the server will
>> automatically serve content held in the ./pages-update directory. Many
>> of the pages contained in that directory by default also have namesakes
>> in ./pages-publish, but editing ./pages-publish has no effect on what
>> the server provides as far as I can tell.
>>
>> So what purpose, if any, does ./pages-publish serve?
>>
>> Also, is the location of html/jsp/etc content referenced by the server
>> configurable? If so, how?
>>
>> Thanks,
>>
>
> Eric,
>
> This may depend on the version you're running.
>
> Before configuration-by-file was added, the server had two modes:
> "publishing" (read-only) and "update" (read-write). When publishing
> all update possibilities were turned off.
>
> The pages-publish/ are supposed to be the web pages for publishing
> more and pages-update/ for when the server is running with update.
>
> When using a configuration file, there are more possible setups and
> the server does not distinguish which set of pages to use.
>
> How are you running the server and which version? (use "-version" to
> tell you).
>
> Andy
>
Re: Fuseki directory structure
Posted by Andy Seaborne <an...@apache.org>.
On 28/12/11 18:41, Eric Scott wrote:
> I'm playing with Fuseki, and I have a question about the purpose of the
> ./pages-publish directory.
>
> It would seem that one can invoke fuseki-server, and the server will
> automatically serve content held in the ./pages-update directory. Many
> of the pages contained in that directory by default also have namesakes
> in ./pages-publish, but editing ./pages-publish has no effect on what
> the server provides as far as I can tell.
>
> So what purpose, if any, does ./pages-publish serve?
>
> Also, is the location of html/jsp/etc content referenced by the server
> configurable? If so, how?
>
> Thanks,
>
Eric,
This may depend on the version you're running.
Before configuration-by-file was added, the server had two modes:
"publishing" (read-only) and "update" (read-write). When publishing all
update possibilities were turned off.
The pages-publish/ are supposed to be the web pages for publishing more
and pages-update/ for when the server is running with update.
When using a configuration file, there are more possible setups and the
server does not distinguish which set of pages to use.
How are you running the server and which version? (use "-version" to
tell you).
Andy