Hello,
For a project I work on I need ability to change all (or most) of XWiki
directories, basically I need to:
1. Move everything from /WEB-INF/ to /WEB-INF/xwiki
2. Move everything from / to /xwiki
3. Everything in /WEB-INF/classes and /WEB-INF/lib can obviously remain
where it is.
4. Merge two web.xml
5. Normally XWiki would have "/" directory on "/xwiki" context. What I
need is for it to have "/xwiki" directory on "/" context.
Why:
To be able to place XWiki on the same ServletContext as the main
project, while maintaining "separate" directory structure. I have to use
custom RightService and UserService which has to have access to main
project's data through the ServletContext, so both this project and
XWiki have to share the ServletContext, effectively being one web-app
from container's point of view.
How:
I was thinking about:
1. Modifying the default initialization so XWiki first tries to load
/WEB-INF/xwiki.cfg, then if it fails /WEB-INF/xwiki/xwiki.cfg.
2.1. Having the ability to specify each configuration file (like
hibernate.xml, velocity.properties) path in xwiki.cfg.
or
2.2. Doing the same for every configuration file, first trying to load
it from /WEB-INF/, then from /WEB-INF/xwiki/ (I think it's less prone
to errors)
3. Changing the top-level directories (like /templates/) paths from
xwiki.cfg
4. Changing the Struts paths (like /bin/)
Would such a functionality be welcome?
I think I can do much work on my own, but I'll probably need some
pointers now and then.
Greetings, Lilianne E. Blaze
Hello,
as the new admin/grunt/bofh for xwiki.com, i'll have soon to perform
some administrative stuff on a running xwiki installation. During past
experiences with such database intensive applications, i found out
that most of the downtimes can be avoided by simply putting the whole
server in read-only mode.
I've put up a topic with requirements and implementation notes here :
http://www.xwiki.org/xwiki/bin/view/Dev/ReadOnlyServer
let me know what are you thoughts.
I'm specifically looking for the best idea to appropriately explain
users they are running on a read-only server.
Thanks in advance,
Erwan
Hi developers !
Google has just given the tentative number of projects that XWiki will
have the chance to have sponsored under the program.
Currently I've ranked the proposals this way..
The 6 proposals that will very probably be accepted
1. A P2P XWiki
2. An Offline WYSIWYG Editor (Java) with code completion etc..
3. A Powerfull WYSIWYG Editor in DHTML or Flash
4. SVG Charting of XWiki Tables
5. Independent Query API for XWiki
6. An Agile Project Management Application
Then the following applications are rejected but I would love to have
them done. So we are thinking of making a mini-summer of code proposal
and proposing some bounties for it (not as much as Google):
1. SVG Realtime Whiteboard in Java + Mozilla SVG
2. AnyEdit: plugabble realtime editor in Java (text, image, drawing,
etc..)
3. Another P2P XWiki proposal
4. Integrate tagging and tag browsing into the XWiki environment
5. Survey and Reporting Tool (the reporting system would be generic)
6. Integrate Servoo with XWiki (OpenOffice and MS Office integration)
7. Google Maps Integration
8. A Contact Manager (PIM) application
9. A Test System for XWiki applications
Other nice stuff I've found interesting
1. MindMap Visualization of an XWiki site/set of pages (we have part
of it that has been done for a client)
2. Implement WebDAV with XWiki Basically the project
3. Wiki Syntax <-> XWiki Object Mapping
4. Easy Web Services Integration
5. Local Names implementation
We had some duplicates projects. Multiple people have proposed to
implement the Independent Query API and it would be great to have these
people as contributors for the low-level part of XWiki.
Let me know what you think and which applicaitons are the most valuable
? Are there any other applications we should provide bounties for ?
I've setup a page on XWiki.org if you want to propose additional
projects http://www.xwiki.org/xwiki/bin/view/Dev/SummerOfCodeStatus
Ludovic
--
Ludovic Dubost
XPertNet: http://www.xpertnet.fr/
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost AIM: nvludo Yahoo: ludovic
I have submitted a proposal for P2P XWiki to Google and am exploring the
current code base
so that I get a head-start incase the proposal gets accepted. I have
A) Downloaded XWiki source version 0.9.793
B) Looked at developer documentation from
http://www.xwiki.org/xwiki/bin/view/Doc/WebHome
By looking at overall architecture of XWiki, I think that an offline
XWiki will have a
different type of Store (centralized store) and a P2P XWiki will have
another store implementation
(P2P Store). At first glance, it appears that the centralized and P2P
store will
extend the interfaces XWikiStoreInterface. The interaction with these
stores *may* introduce new
APIs or use existing XML-RPC API without any changes. I am working on
understanding the overall architecture of the current XWiki and
identifying how a P2P XWiki can make the best use of
existing implementation.
I have the following questions:
a) I have downloaded the source code but don't see any documentation on
how I can run the XWiki completely
local to my machine. What are the requirements and steps for running a
local wiki from the source code?
b) To be sure, am I starting with the correct code base or is there any
other version of offline XWiki (may be not fully developed)?
Any other suggestions also welcome,
Thanks,
Bikash Agarwalla
Hello,
Today, while installing xwiki on my own box, i've found very tedious
having to edit a file in a tomcat working directory (webapps/xwiki,
for instance) to change the database parameters.
Having a datasource defined in the container will allow admins to
avoid having to learn the internals of the application, and this is
how it's done in other apps like jira or confluence.
For tomcat, I feel it would be better to :
- make sure hibernate.cfg.xml refers to a datasource named "jdbc/XWikiDS"
- define the said DataSource in $CATALINA_HOME/Catalina/localhost/xwiki.xml
- put the jdbc driver in $CATALINA_HOME/common/lib, now that the
container is responsible for opening the connection
I think it will also ease the packaging of a standalone xwiki server.
What do you think ?
I'm attaching the configuration that worked for me almost out of the box.
Erwan
Are there any plans to develop improved documentation for the 1.0 release?
In the initial wiki installation, it would be nice if there were a nice "Getting Started" guide for users that explains how to do basic wiki administration, etc.
One way to develop this might be to create a virtual wiki at something like home.xwiki.org where current Xwiki users could contribute to developing the initial home page that appears in a default installation. Thoughts?
Stephen
