The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.9.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
Final release of the XWiki Enterprise 1.9 version.
Main changes:
* UI improvements
** Quick Jump to any Page navigation
** Faster Save and Continue using AJAX
** Improved Full Screen editing
** New Live Table UI
** Improved comments UI and functionality
** Multiple attachment upload in one request
** New UI for the Class and Object editors
** Improved toolbar in the wiki editor
** Preliminary support for Autosave
* PDF export improvements
* JavaScript improvements
* Switched to UTF-8 as the default encoding
* Mailsender improvements
* New Office Importer feature: document splitting
* XWiki 2.0 Syntax is enabled by default
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise19
Thanks,
The XWiki dev team
Hi devs,
Since XWIKI-3652, the web.xml is no longer valid servlet-2.3, since the
2.3 spec doesn't allow filters and the request dispatcher to mix.
Given that currently 2.5 is the most implemented standard, I'd say that
we require from now on a 2.4-compliant container. This will leave out
only very old versions of the popular containers (tomcat <=4).
Any objections?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hello devs,
Sorry for probably unappropriate question, but I'm new here and I'm stuck..
I'm writing my own plugin for xwiki and I need it to use hibernate. By
the look of existing plugins (like ActivityStream plugin) it seems
that I should
somehow use XWiki hibernate configuration (after adding info about my
mapping of course). How should I organize my plugin?
Is there a way to create new hibernate sessions for my plugin using
XWiki SessionFactory?
Hi
Could everyone who has some time right now try 1.9 RC2 and test drive
it, looking for regressions?
Also could anyone knowing of any regression/blocking issue for 1.9
final please raise it now?
We're about to release 1.9 final at the end of the day so this is the
last chance to fix any blocking issue.
Thanks
-Vincent
Hello Dev,
I am relatively new with xwiki.Is it possible with xwiki that eash
wiki will have there
individual remote Database.we configure main wiki data base in
hibernet.cfg.xml file.
when we create a wiki it creates wiki schema within the main database
or same database engine.but what i want is when we create a wiki it
will create the database for that wiki in another remote database
server.not in the same file of main wiki database.and when we load the
wiki it will use the remote database not the main wiki database.please
let me know if it is possible.it would be greateful if you refer me
some links if exists.
BR,
Sayeem
Hi,
I'm having 2 problems with Plexus:
1) I tried to upgrade and it's not working. They've dropped the
ability to dynamically register a new component instance for an
existing role. Jason Van Zyl said he's ok to fix it but he's busy on
other stuff and it's been now 2 weeks since he said he'll fix it.
Generally speaking there are not many people working on Plexus core so
it's not moving much.
2) I tried using events (it was there in alpha-31 but seem to have
disappeared in recent versions - I may be wrong. However since there's
zero documentation I had to try to find it in the code and couldn't
find it) and couldn't. Even in alpha-31 it doesn't work (it works only
for components located in components.xml but since we're dynamically
registering components it doesn't work for us.
Thus I'm more and more tempted to drop support for Plexus and instead
use our Embedded component manager for now and start a xwiki-osgi
module that would implement our SPI for OSGi. I've read OSGi
documentation and it looks not too difficult to do.
I have all the code done for sending Component Manager events but it
won't work with Plexus so I'm proposing to use our Embedded CM for
now. In the meantime I'll try to talk to Jason to see what can be done
on the plexus side.
WDYT?
Note that our Embedded CM hasn't been tested for multithreading so
we'll need to verify it works in the 2.0 dev cycle and fix any
threading issue.
Thanks
-Vincent
vmassol (SVN) wrote:
> Author: vmassol
> Date: 2009-06-08 18:12:07 +0200 (Mon, 08 Jun 2009)
> New Revision: 20972
>
> Modified:
> platform/core/trunk/xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/parser/ParseException.java
> Log:
> Removed unused stuff since WikiModel doesn't generate exception on parsing. If it does it means the underlying grammar is buggy and needs to be fixed.
I would really like to have these working...
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Do we have any code in our RSS macro that handles exception?
If so all we need to have if a unit test with mocks that prove that
when there's an error in the RSS access layer (rome?) then we handle
it correctly.
Thanks
-Vincent
On Jun 8, 2009, at 12:14 PM, asiri (SVN) wrote:
> Author: asiri
> Date: 2009-06-08 12:14:00 +0200 (Mon, 08 Jun 2009)
> New Revision: 20958
>
> Modified:
> platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-
> rendering-macro-rss/src/test/java/org/xwiki/rendering/
> RssMacroFailureConditionsTest.java
> Log:
> [misc] Removed the "connection timeout exception" test. This test is
> non-deterministic.
>
> Modified: platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/
> xwiki-rendering-macro-rss/src/test/java/org/xwiki/rendering/
> RssMacroFailureConditionsTest.java
> ===================================================================
> --- platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-
> rendering-macro-rss/src/test/java/org/xwiki/rendering/
> RssMacroFailureConditionsTest.java 2009-06-08 08:43:44 UTC (rev 20957)
> +++ platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-
> rendering-macro-rss/src/test/java/org/xwiki/rendering/
> RssMacroFailureConditionsTest.java 2009-06-08 10:14:00 UTC (rev 20958)
> @@ -44,27 +44,7 @@
> } catch (MacroExecutionException expected) {
> assertTrue("The required 'feed' parameter is
> missing".equals(expected.getMessage()));
> }
> - }
> -
> - /**
> - * Tests the macro's behavior when the server hosting the feeds
> doesn't respond.
> - */
> - public void testConnectionTimeout() throws
> MacroParameterException
> - {
> - assertNotNull(macro);
> - assertNotNull(parameters);
> -
> - // We set the feed's URL to an unreachable address.
> - parameters.setFeed("http://22.22.22.22");
> -
> - try {
> - macro.execute(parameters, null, null);
> - fail("The macro should throw a 'Connection timeout
> exception'");
> - } catch (MacroExecutionException expected) {
> - String errorMessage = expected.getMessage();
> - assertTrue(errorMessage.startsWith("Connection timeout
> when trying to reach"));
> - }
> - }
> + }
>
> /**
> * Tests the macro's behavior when the server hosting the feeds
> doesn't respond.
Hi everyone,
Current situation
=============
Right now we have 2 mechanisms in place:
- hidden docs. These is done deep at the storage level and hidden docs
don't appear in any HQL queries. This is
- $blacklistedSpaces in xwikivars.vm which is used (or not!, that's
the problem) in some wiki pages (AllDocs, Search, Dashboard, etc)
Need
====
We have a need for blacklisted/hidden docs and spaces. This is
different than rights. This is just for presentation purpose.
The need I see is:
- guest and simple users should not see blacklisted/hidden docs and
spaces
- advanced users and admin should see them
(Note: I'm not sure we have a need to blacklist docs/spaces for
everyone including admins as it's currently done for hidden docs)
Issues
=====
1) In lots of spaces we don't exclude blacklisted spaces since at
every location you have to add specific code to do the exclude.
2) Hidden docs are a problem since there are cases we want to see
them all (like when creating a new wiki and you need to copy a
template wiki containing hidden docs)
Proposal
=======
* I believe we need to remove the filtering at the storage level. That
level should return all docs matching the queries
* We modify the default XWiki.searchDocument APIs so that they filter
on hidden docs and blacklisted spaces (using the velocity
$blacklistedSpaces variable). This would be changed later on when we
implement the new model and introduce the notion of space. When this
happen we'll be able to have hidden metadata to the Space object.
* We add a new XWiki.searchDocument API that doesn't do any filtering
WDYT?
Thanks
-Vincent