Hi,
Just to let you know I'm going to branch the Lucene plugin. I need
that since in the patch I'm writing for ThreadLocal I need to have it
depend on core 1.5.
This means Trunk will be Lucene plugin 1.3 (depending on core 1.5)
while the branch will be 1.2 (depending on core 1.4).
Ok with everyone?
I'll create that later today.
Thanks
-Vincent
Hi,
Since Maven 2.0.9 is now released and it works with our build we
should standardize on it rather than using a"non-official" 2.1
snapshot version.
I'm thus proposing to move the maven version we use for Continuum on
Maven 2.0.9 and to change the Building page to remove our snapshot
version and change the text to say that to build XWiki you need Maven
2.0.9 or greater.
WDYT?
Thanks
-Vincent
Hi everyone,
A few months ago we had discussed the possibility of offering a free
community-managed farm for non-business critical projects.
See http://tinyurl.com/69blgy
In short the ideas are:
1) No support guarantee. All support done on the xwiki.org user
mailing list by the community.
2) No stability guarantee. We would always install the latest Platform/
XE/XEM version on it and it would serve as a stability test for the
xwiki development team. Obviously the community will always try to
make it as stable as possible but that's not guaranteed. It's also
possible that the farm will be down a few days now and then. We'll try
to reduce this but no warranties.
3) There will be several members of the community who'll have admin
access on the farm.
4) It will be open to anyone. However the target users will be
technical people who can support themselves to some extent. We won't
control that but it'll be mentioned on the registration page. In any
case points 1) and 2) make it obvious that it shouldn't be used for
any business-critical wiki.
We're now announcing the myxwiki.org community farm at http://myxwiki.org
Note that the machine was donated by the XPertNet company (http://xwiki.com
). Thanks XPertNet! :)
Right now the following persons are admin on this farm:
* ThomasMortagne
* Marta
* Sergiu
* GuillaumeLerouge
* amelentev (Artem)
* Jerome Velociter
* jvdrean (Jean-Vincent)
* VincentMassol
Please note that all these people are doing this in their free time
and thus we're looking for more admins. If you're interested in
helping us manage this farm (and we hope there'll be plenty of you
interested) then please register a user and let me know and I'll make
you admin.
Here's what admins should do:
* work on improving the community farm content in general
* work on improving the way information is presented and navigation
* watch the recent changes and undo graffitis where needed
* create wikis for people who request them (there's a HTML form to
fill) - we'll need to decide if we want to make that self service or
not. Right now I suggest that people interested in getting a wiki
there send an email to the xwiki users list explaining what they want
to do with their new wiki and then one admin creates it for them.
* watch out for security holes
* suggest ideas to improve the farm
What everyone can do:
* edit and improve content for the non admins parts of the farm
* spread the word, blog about it, etc
Thanks
-Vincent on behalf of the XWiki community
Hi,
Using xwiki class editor we can create classes and package them as
application. Classes can also have an entity relationship among themselves.
I have few question on how can we relate classes in xwiki. Let me start by
posting a simple example:
Say our application has two classes Product and Review. Relationship between
them is a product can have multiple reviews.
Now I can relate these classes in following way:
1. Create a product document and add the product object to it. All the
reviews for that product are also added to that product document as review
objects. Thus I have grouped reviews to a product.
2. Create a product document and add the product object to it. For each
review for that product created a review document and add review object to
that review document and make review document child of product document.
Thus I have arranged reviews as children of a product.
3. In the review class add a db list field, which refers to objects of
product class. While creating a review object choose the right product name
from the list. Thus reviews are associated to a product.
Thus you can see that in each of the three ways I have related two classes.
Only difference is different ways of storing them. (again presentation still
can be same and I am here interested in optimal storage strategy only).
So I would like to know which of the above three is the best way of relating
classes. Are there any more ways of achieving the relationship I talked
initially?
I would like to know from people who have been developing complex
applications involving relationship between several xwiki classes as what
would be the best way of arranging the use case just described.
Thanks
Sachin
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/Relating-classes-in-xwiki-tp16851540p16851540.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi XWikiers
There are open question about the new skinx plugin, I'd like to
discuss about the first one :
http://dev.xwiki.org/xwiki/bin/view/Design/SkinExtensions#HUsage
"Should $xwiki.jsx.useFile("filename.js") work for files located on
the disk? This allows the same pull process to be used with files
located in the skin, without requiring SX documents and objects. I'd
say yes. Then, what should the URL look like?
/xwiki/bin/jsx/skins/albatross/somestyle.css is OK?"
We definitely need this to be able to load some libraries
condditionaly, for example usersandgroups.js or lightbox.js.
I don't see the need for some special URLs, would it be a problem that
useFile() adds the result of a xwiki.getSkinFile() to the header ?
Thanks,
--
Jean-Vincent Drean
Hi,
On Apr 30, 2008, at 1:05 AM, Fabrizio Lamari (TeleJob - WebMaster)
wrote:
> Hello
>
> I was using the XWiki for our company and since yesterday evening it
> doesn’t work anymore.
> I haven’t changed anything on the settings yesterday.
> When I want to go on the XWiki (www.telejob.ch/wiki.html) I get this
> error:
[snip]
> Caused by: java.sql.SQLException: General error:
> java.lang.OutOfMemoryError: Java heap space
> at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
> at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
> at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
> at org.hsqldb.jdbcDriver.connect(Unknown Source)
> at
> org
> .apache
> .commons
> .dbcp
> .DriverConnectionFactory
> .createConnection(DriverConnectionFactory.java:37)
> at
> org
> .apache
> .commons
> .dbcp
> .PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:
> 290)
> at
> org
> .apache
> .commons
> .dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:
> 877)
> at
> org
> .apache
> .commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:
> 851)
[snip]
As you can see your JVM has no more memory. I don't know why this
happened (it can a lot of reasons) but the way to solve it for now is
just to restart the JVM (i.e. the servlet container).
Thanks
-Vincent
Hi,
I'd like that we review our objectives for 1.4 vs what we've done:
* Bug fixes
o Go from 240 in JIRA for Core down to 180 on XE 1.4
release date
Right now the bug count is at 227. Even though it's lower than 240
it's still a far cry from the 180 target...
* Better performance
o Run XE with a profiler and find bottlenecks
Not done
o Reduce number of database calls
Not done
o Improved page loading (JV)
Not done
o Make Stats usable on xwiki.org (ThomasM)
Done!
* More automated tests
o More selenium tests
We can consider this done although we always need more. We need to
continue adding and even spending some time just adding tests even if
we don't have code at all.
o Add tests on Tomcat 6.x as part of the CI build
Not done
o Add tests on Windows and with IE6 and IE7 as part of the
CI build
Not done
Conclusions:
==========
* We're not too good. I think this is principally due to me, since I
focused on the new rendering component and have delegated XE day to
day management/coaching to JV. Thus JV has not been able to work on
the performance improvements as planned. We really need to get that
going in 1.5 now.
* We have 1 more week to fix as many bugs as possible.
WDYT?
Thanks
-Vincent
Hi,
I've started the page at http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap
but let's discuss it here first.
So what are the tasks we want to solve for 1.5. Here's my take:
* More bug fixes
* Better performance
o Run XE with a profiler and find bottlenecks
o Reduce number of database calls
o Improved page loading
* More automated tests
o More selenium tests
o Add tests on Tomcat 6.x as part of the CI build
o Add tests on Windows and with IE6 and IE7 as part of the
CI build
* Overhaul of the Administration
So basically more stability and more usability.
In term of dates, I think 2 milestones followed by a RC works pretty
well. In total that's about 3 weeks for each milestone and then 1 week
for each RC. If we imagine we need 2, then that's 8 weeks, i.e. 2
months, which sounds good to me.
WDYT?
I'll let JV propose precise dates.
Thanks
-Vincent
I downloaded 1.3.1 XWiki Enterprise from xwiki.org which doesn't include
the source, I then downloaded what I thought was the matching source
from the source repository, however, I've missed something somewhere
along the lines. xWiki was running fine until I rebuilt the project,
now it's whacked. I'm planning on deleting what I have and installing
1.3.2, is there any downloads that include both the compiled and source
necessary to run XWiki Enterprise?
Cheers,
Jeff