Hi XWiki committers,
We're moving to a new SVN server on the 2nd of October 2007 (afternoon).
I'll make the OW SVN read only on the 2nd morning. This means that
you'll need to check out again once the move is done.
If you have uncommitted files you can simply copy them (without
the .svn directories of course) over the new checkout and that'll
work fine.
Let me know if you have any issues with this move.
The benefits of this move:
- newer SVN server version (1.4*) (compared to 0.8 on OW I think).
This means less bugs, perf improvements, support for "new" features
like annotations.
- more availability for those working in the wee hours or in the US
(the OW SVN server is down for a few hours every night)
- ability to quickly move to newer version (when 1.5 is out, we'll
want to move to it to support the new SVN merge tracking feature for
example)
- HTTP/HTTPS protocol support. This will make it VERY easy to use (SVN
+SSH is always difficult) and will allow us to have a single trunks
for our svn:externals
- ability to host other XWiki-friend projects (like WikiModel,
Curriki, etc). For curriki this will mean having its own repository,
separate from XWiki, which makes sense IMO.
- more?
Thanks
-Vincent
Yes, I have gone through the page you mentioned and I tried creating a
simple form.
But I faced problems :
[1.] How do I remove a property which I do not want while editing a class ?
[2.] From where do I get information about the various class property
types such as Database List class, Database tree list class, etc ?
[3.] How do I communicate with my database ?
regards,
V. Harikrishnan Nair
|| Lokah Samastah sukhino bhavantu ||
Hi all...
I am a first time wiki user.
I would like to create a form in one page which enters data into a MySQL
database and retrieve the data from the database into another page. How do
I do that.
I have done the necessary installations and I want to try customizing it.
regards,
V. Harikrishnan Nair
Hi xwiki committers,
Multiwiki plugin will be released very soon with XEM. As I
architecture this plugin, it can now live out of XEM as a application
with his plugin+attached XAR.
In place of "multiwiki" I'd like to propose to name the application
and the plugin "wiki-manager" as it sounds better to me as the goal is
to create, delete, edit properties of wikis and template wikis, in
other word to manage wikis. So why wikis-manager ?
Plus it is more coherent with the new application-manager XAR+plugin
that will be released very soon too.
So lets fight :)
Here my +1 for "wiki-manager".
--
Thomas Mortagne
The recent TC errors were not real errors. They were due to disk
space issue on the machine. That machine had a small disk space for /
tmp and this is where the jetty container was putting its tmp files.
I've modified the default config so that jetty now puts its tmp files
in the work/ dir.
-Vincent
On Sep 25, 2007, at 12:00 PM, teamcity(a)xwiki.org wrote:
> Build XWiki Enterprise::Trunk #516 failed (tests failed: 1 (1 new),
> passed: 0)
> Agent: Default agent
> Build results: http://teamcity.xwiki.org/viewLog.html?
> buildId=3733&buildTypeId=bt7
>
> Newly failed tests (1 test)
> ==================================================================
> com.xpn.xwiki.it.xmlrpc.AllTests.junit.framework.TestSuite@1f4cbee
> =================
> java.lang.RuntimeException: Failed to start XWiki in [60] seconds
> at com.xpn.xwiki.test.XWikiTestSetup.waitForXWikiToLoad
> (XWikiTestSetup.java:137)
> at com.xpn.xwiki.test.XWikiTestSetup.setUp(XWikiTestSetup.java:73)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.junit.JUnitTestSet.execute
> (JUnitTestSet.java:213)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTest
> Set(AbstractDirectoryTestSuite.java:138)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute
> (AbstractDirectoryTestSuite.java:125)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess
> (SurefireBooter.java:290)
> at org.apache.maven.surefire.booter.SurefireBooter.main
> (SurefireBooter.java:818)
> at org.apache.maven.surefire.booter.SurefireBooter.main
> (SurefireBooter.java:818)
>
>
>
> ======================================================================
> ======
> Configure email notifications: http://teamcity.xwiki.org/
> profile.html?init=1#notifications
> _______________________________________________
> notifications mailing list
> notifications(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/notifications
Hi everyone,
We need to start defining the content of XE 1.2 and the time frame.
Looking at http://www.xwiki.org/xwiki/bin/view/Idea/FeaturesFor11 we
can see that there are a lot of leftovers.
Content
=======
I propose the following content for 1.2:
* Priority 1: bug fixing. We have even more bugs in jira than before
we started 1.1 (unless I'm mistaken). In platform only we have about
171 bugs listed. There were 108 when we started 1.1.
* Priority 2: Cleaning up
- cleaning up skins
- cleaning up XE into separate applications (Blogs, Search, etc)
- cleaning up resource files (and implementing the mechanism defined
on the list for application resources)
- cleaning up JS libraries
* Priority 2: New rights UI
* Priority 3: Other features
- Scheduler plugin to finish (note that now that this plugin is
outside XE it can be worked on in a different lifecycle)
- Notification and mail plugins (same comment as for the scheduler
plugin)
- Anything that helps navigation and usability of XE
Note: We already have important changes in 1.2 trunk (recycle bin,
new history table, etc) which alone would warrant a release so we
don't need to add many more features. This is also why I think we
should focus on making these work properly with nice UIs and fix
existing bugs rather than try to cram more features. The only
exception is the new Rights UI which we badly need. We also badly
need Mail/Notification plugin.
Milestones
=========
I propose to release a 1.2 final version before Javapolis, which
starts on the 10th of December. We'll be present there so I think it
would be very good if we came with a new version ready.
Thus I propose the following schedule:
1.2M1: 1st of October
1.2M2: 15th of October
1.2M3: 29th of October
1.2RC1: 12th of November
1.2RC2: 19th of November
1.2 final: 26th of November
This gives us an error margin of about 15 working days (more with
week ends ;)) for making it to Javapolis, which I think is good
enough. We just need to be careful to do time boxing properly and
release the milestones on agreed dates.
WDYT?
Thanks
-Vincent
Hello,
In order to implement the Rights Management desired improvements, we concluded that there is need to write an api to help retrieve:
- the local / global users
- the local / global groups
- the inherited rights for users / groups
So after I spoke with Ludovic and Thomas, here is the list of things to be implemented in this api:
XWikiUser
============
We have:
-> user (string)
-> main (boolean)
--> setUser, getUser
--> isMain, setMain
----------------------------
We will need to do:
--> add methods:
* getAllActiveUsers [ will read xwiki settings to know what to return, global or local active users; Thomas and I understood that 'active' user means the user after being registered and confirmed the registration through email maybe, following a link to activate or something like this ]
* getAllGlobalUsers
* getAllLocalUsers
* getAllUsers
* getMatchingActiveUsers(string MatchText, XWikiContext)
* a method to get details for a user, other than the ones returned by getAllUsers (which will return something like Xwiki.LudovicDubost); we might need firstname, lastname, pagename etc. maybe we can use a parameter for the getAllUsers method, called 'withDetails'(boolean)
XWikiGroupService (interface)
=============================
We have
--> listGroupsForUser
--> addUserToGroup
--> listMemberForGroup
--> listAllGroups
-------------------------
We will need to do:
--> add methods:
* getAllActiveGroups
* getAllGlobalGroups
* getAllLocalGroups [ this is currently done by 'listAllGroups' ]
* listMatchingActiveGroups(string MatchText, XWikiContext) [ this will help me for the ajax-suggest feature; will return the groups with the name matching a certain string ]
XWikiRightService (interface)
==============================
We have:
--> checkAccess
--> hasAccessLevel
--> hasProgrammingRights (2 methods)
--> hasAdminRights
--> listAllLevels
-------------------------------
We will need to do:
--> add methods:
* to find inherited rights
* and maybe other things, I'm not very sure yet
I hope I understood right. Thomas will try to draw some schemes and I'll clarify some of the questions that are left, then.
Ps. I posted this mail yesterday but only today I found out that devs list moved to xwiki.org. Sorry about the delay.
Hi,
Since this is an API I'm sending a vote.
I'd like to modify the following:
public List search(String wheresql) throws XWikiException
{
if (hasProgrammingRights())
return xwiki.search(wheresql, getXWikiContext());
return null;
}
To:
public List search(String wheresql) throws XWikiException
{
if (hasProgrammingRights())
return xwiki.search(wheresql, getXWikiContext());
return Collections.EMPTY_LIST;
}
Rationale:
* A method that returns a List (or a Collection in general) should
never return null but always an empty collection instead (or throw an
exception).
I also propose to modify the other methods to return empty
collections instead of null. Those include:
* public List getDeletedDocuments(String fullname, String lang)
throws XWikiException
* public List search(String wheresql, int nb, int start) throws
XWikiException
* public List searchDocuments(String wheresql, int nb, int start,
String selectColumns)
Here's my +1
Thanks
-Vincent
Should have hit the reply-to-all button :)
---------- Forwarded message ----------
From: Asiri Rathnayake <asiri.rathnayake(a)gmail.com>
Date: Sep 14, 2007 9:21 AM
Subject: Re: New date for XEclipse 10.M2?
To: Vincent Massol <vincent(a)massol.net>
Hi Vincent,
On 9/14/07, Vincent Massol <vincent(a)massol.net> wrote:
>
> Hi Asiri/Tharindu,
>
> I'd like to set a new target date for the XEclipse 1.0M2 release so
> that we have an objective.
>
> Could you please tell me what date would be reasonable, taking into
> account your studies and such?
Will 8th of October be enough ?
Thanks.
- Asiri
Thanks
> -Vincent
>
>