Christophe FRAULE wrote:
> Hello,
>
>
>
> I'm a newbie with XWiki and I'm mostly experimenting with it so see if and
> how we could use it internally.
>
>
>
> I'm running XWiki 1.9.3.22597 on Tomcat6 with Fedora 11/MySQL 5.1.37 and had
> encountered no particular problem except that I have to launch and run the
> OpenOffice server externally on a regular account because it would not start
> when launched by XWiki. I suspect it's a memory access right issue because
> launching manually from the tomcat account I get this
>
>
>
> -sh-4.0$ /usr/bin/soffice -headless
> -accept=socket,host=127.0.0.1,port=8100;urp; -nofirststartwizard
>
> creation of executable memory area failed: Permission denied
>
> creation of executable memory area failed: Permission denied
>
> creation of executable memory area failed: Permission denied
>
> creation of executable memory area failed: Permission denied
>
> creation of executable memory area failed: Permission denied
>
> creation of executable memory area failed: Permission denied
>
> creation of executable memory area failed: Permission denied
>
>
>
> It's just the way the tomcat account is set I believe. (Seeing no xwiki
> user, I assume xwiki is using the tomcat account to launch soffice).
>
>
>
> I have 3 x questions regarding XWiki:
>
>
>
> 1) We want to use 'spaces' (no virtual XWiki) to create boundaries
> between what users can see. I have created Space A, User A and configured
> access rights so that User A can access Space A only. The problem is that
> when User A log into XWiki, XWiki returns and error message because User A
> tries to land on the main page =>
>
> a. Can we configure XWiki so that User A automatically lands on Space
> A when login ? If yes, how ?
You can write a little script instead of the default content of
Main.WebHome, one which computes the right space for the current user,
and redirects there. Something like:
#set($space = $context.user.substring($context.user.indexOf('.')))
#set($space = "${space.substring(1)}.WebHome")
$response.sendRedirect($xwiki.getURL($space))
> b. I assume also that performing a search User A will not be able to
> see anything out of his user space A. Right ?
It depends. The default search pages filter documents according to the
user rights, but a user can write his own query to retrieve all document
names, although he won't be able to access the content of those
documents. If document names should also be private, it can easily be
fixed by changing the Java code a bit (and actually it should).
>
> 2) I have made a quick Groovy/SQL test polling a rather large table out
> of an external database and displaying the result into HTML on XWiki.
> Scrolling down the dynamically generated XWiki HTML table, I suddenly got
> into a black hole or let's say the end of the XWiki web page =>
>
> a. What is the way in XWiki to control the maximum length/size (or
> maximum characters ?) of a Web page ?
The limit for the document content is a soft one: at least 200k
characters, which is rounded up to the equivalent database data type,
which for MySQL becomes mediumtext, large enough to hold 16M. Then,
there is the max packet size, which is configured on the server, and it
is not set by XWiki.
If you're talking about a skin issue, meaning that the page suddenly
ends, I think somebody else reported a similar problem a long time ago,
but I don't remember what was the cause, and whether it was fixed or
not. Can you be more specific about what's happening?
>
> 3) Is it possible to programmatically add pages into Xwiki based on the
> content of an external database. The idea here is to run a script (via Xwiki
> scheduler ?) to pull records out of an external database. For each (new)
> record, then a new XWiki page would be created which users could edit to
> bind their own additional pieces of information. When a database record is
> deleted, the corresponding XWiki pages would be move to the 'gone' space.
>
Yes, it is possible, but this requires more time to write. A few
pointers: there is an SQL plugin for XWiki which allows you to connect
to an external database, there is the task scheduler which allows you to
execute jobs at a given time/period, and the API allows you to
manipulate documents as you like: create, rename, change, delete, etc.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
users mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/users
