Hi,
i have this error since yesterday and all i did is trying to add a excel plugin
so i followed the tutorial , i added the jxl jar in lib directory and i putted the line
in xwiki.cfg but after having this error i rolled back all my changes i deleted the jar and restored
the xwiki.cfg to the same old state but still have the error:
HTTP ERROR: 500
Error number 3 in 0: Could not initialize main XWiki context
Wrapped Exception: Error number 3001 in 3: Cannot load class com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from param xwiki.store.migration.manager.class
Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
Wrapped Exception: invalid configuration
RequestURI=/xwiki/bin/view/Main/
Powered by Jetty://
what should i do, my work is lost?
help on this one please thank you very much
--
View this message in context: http://n2.nabble.com/Error-number-3-in-0-tp2642272p2642272.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
In the rendering code we have several places where we've had to create
generic string manipulation classes/methods (for example a method to
remove a single NL at start and end of string).
I think it would be better to create one or several components for
these string manipulation methods (same as we have xwiki-xml for xml
manipulation).
The idea is that we should use existing framework as much as possible
(StringUtils from commons lang for ex) but when we cannot find an
existing framework to manipulate text then we would put it in xwiki-
text.
WDYT?
Thanks
-Vincent
On Apr 16, 2009, at 12:56 PM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2009-04-16 12:56:05 +0200 (Thu, 16 Apr 2009)
> New Revision: 18727
>
> Added:
> enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/
> xpn/xwiki/it/selenium/SimpleAdvancedTest.java
> Modified:
> enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/
> xpn/xwiki/it/selenium/AllTests.java
> Log:
> XAADMINISTRATION-35: Administrative users get their own setting on
> usertype, and not the setting for the user whose profile they're
> viewing
> Added test.
> Patch submitted by Arun Reddy Nelakurthi, applied with codestyle
> changes
>
>
> Modified: enterprise/trunk/distribution-test/selenium-tests/src/test/
> it/com/xpn/xwiki/it/selenium/AllTests.java
> ===================================================================
> --- enterprise/trunk/distribution-test/selenium-tests/src/test/it/
> com/xpn/xwiki/it/selenium/AllTests.java 2009-04-16 10:54:34 UTC (rev
> 18726)
> +++ enterprise/trunk/distribution-test/selenium-tests/src/test/it/
> com/xpn/xwiki/it/selenium/AllTests.java 2009-04-16 10:56:05 UTC (rev
> 18727)
> @@ -79,6 +79,7 @@
> addTestCase(suite, DocExtraTest.class);
> addTestCase(suite, PanelsTest.class);
> addTestCase(suite, SectionTest.class);
> + addTestCase(suite, SimpleAdvancedTest.class);
Shouldn't this go in the existing UserProfileTest.class instead?
There seems to be some duplication too to create a user.
Thanks
-Vincent
> return new XWikiSeleniumTestSetup(new XWikiTestSetup(suite));
> }
>
> Added: enterprise/trunk/distribution-test/selenium-tests/src/test/it/
> com/xpn/xwiki/it/selenium/SimpleAdvancedTest.java
> ===================================================================
> --- enterprise/trunk/distribution-test/selenium-tests/src/test/it/
> com/xpn/xwiki/it/selenium/
> SimpleAdvancedTest.java (rev 0)
> +++ enterprise/trunk/distribution-test/selenium-tests/src/test/it/
> com/xpn/xwiki/it/selenium/SimpleAdvancedTest.java 2009-04-16
> 10:56:05 UTC (rev 18727)
> @@ -0,0 +1,98 @@
> +/*
> + * See the NOTICE file distributed with this work for additional
> + * information regarding copyright ownership.
> + *
> + * This is free software; you can redistribute it and/or modify it
> + * under the terms of the GNU Lesser General Public License as
> + * published by the Free Software Foundation; either version 2.1 of
> + * the License, or (at your option) any later version.
> + *
> + * This software is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + * Lesser General Public License for more details.
> + *
> + * You should have received a copy of the GNU Lesser General Public
> + * License along with this software; if not, write to the Free
> + * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
> + * 02110-1301 USA, or see the FSF site: http://www.fsf.org.
> + */
> +package com.xpn.xwiki.it.selenium;
> +
> +import com.xpn.xwiki.it.selenium.framework.AbstractXWikiTestCase;
> +import com.xpn.xwiki.it.selenium.framework.AlbatrossSkinExecutor;
> +import com.xpn.xwiki.it.selenium.framework.XWikiTestSuite;
> +
> +import junit.framework.Test;
> +
> +/**
> + * Verify Advanced and Simple User type settings.
> + *
> + * @version $Id$
> + */
> +public class SimpleAdvancedTest extends AbstractXWikiTestCase
> +{
> + public static Test suite()
> + {
> + XWikiTestSuite suite = new XWikiTestSuite("Verify Advanced
> and Simple User type settings.");
> + suite.addTestSuite(SimpleAdvancedTest.class,
> AlbatrossSkinExecutor.class);
> + return suite;
> + }
> +
> + protected void setUp() throws Exception
> + {
> + super.setUp();
> + open("Main", "WebHome");
> + }
> +
> + public void testSimpleAdvancedUsertype()
> + {
> + // Remove "JohnSmith" user if already exists
> + loginAsAdmin();
> + deletePage("XWiki", "JohnSmith");
> + getSelenium().waitForPageToLoad("30000");
> + // Ensure that the user isn't logged in
> + logout();
> +
> + // Register new user "JohnSmith"
> + getSelenium().click("headerregister");
> + getSelenium().waitForPageToLoad("30000");
> + getSelenium().type("register_first_name", "John");
> + getSelenium().type("register_last_name", "Smith");
> + getSelenium().type("xwikiname", "JohnSmith");
> + getSelenium().type("register_password", "JohnSmith");
> + getSelenium().type("register2_password", "JohnSmith");
> + getSelenium().type("register_email",
> "JohnSmith(a)example.com");
> + getSelenium().click("//input[@value='Register']");
> + getSelenium().waitForPageToLoad("30000");
> +
> + // Login as "JohnSmith" and chech for the user type. Verify
> whether the Usertype Switch Link works.
> + login("JohnSmith", "JohnSmith", false);
> + getSelenium().waitForPageToLoad("30000");
> + open("XWiki", "JohnSmith");
> + assertTextPresent("Switch to Advanced edit mode");
> + getSelenium().click("link=Switch to Advanced edit mode");
> + getSelenium().waitForPageToLoad("30000");
> + getSelenium().click("link=Switch to Simple edit mode");
> + getSelenium().waitForPageToLoad("30000");
> + assertTextPresent("Switch to Advanced edit mode");
> + logout();
> +
> + // Login as "Admin" and Verify whether usertype of
> "JohnSmith" is Simple.
> + loginAsAdmin();
> + open("XWiki", "JohnSmith");
> + assertTextPresent("Switch to Advanced edit mode");
> +
> + // Switch Usertype of "JohnSmith" to Advanced.
> + getSelenium().click("link=Switch to Advanced edit mode");
> + getSelenium().waitForPageToLoad("30000");
> + assertTextPresent("Switch to Simple edit mode");
> + logout();
> +
> + // Login as "JohnSmith" and verify whether the usertype is
> Advanced.
> + login("JohnSmith", "JohnSmith", false);
> + open("XWiki", "JohnSmith");
> + assertTextPresent("Switch to Simple edit mode");
> + logout();
> + }
> +}
Hi devs,
based on feedback from our system administrator & project managers, I'd like
to suggest the following improvements to the Office Importer application
(those improveents were initially suggested in 2 JIRA issues):
*
Administration - XAOFFICE-13
*
- Ability to set the server path in xwiki.cfg or xwiki.properties
(already done)
- Ability to overwrite the server path in a field on
.../xwiki/bin/admin/XWiki/XWikiPreferences?editor=globaladmin§ion=XWiki.OfficeImporterAdmin
- Provide an option to set the OOo server to start automatically when
XWiki gets started
- Ability to define this setting in xwiki.cfg or xwiki.properties
- Ability to overwrite this setting on
.../xwiki/bin/admin/XWiki/XWikiPreferences?editor=globaladmin§ion=XWiki.OfficeImporterAdmin
Ideally, we should also allow *remote access to the OOo server*, so that the
same OOo server can be used by more than 1 wiki and be located on another
machine. Asiri tells me that this is not possible with the current version
of JOD converter. However this feature is going to be oft requested. *Is
there any other way to make it work?*
*User Experience - XAOFFICE-14*
Right now, the link to the Office Importer is located in the action bar,
under the "Actions" menu. The action bar is meant to let users interact with
the current page (context actions), thus the "Import Office Document" link
shouldn't be located there.
- Move the "Import Office Document" link from the action bar to the Quick
Links panel and rename it to "Office Import".
- That's what we do with current default applications (Blog) and what we
used to do with the Photo album and the calendar. Since the Office Import is
a default application as well, I don't see why it should be trated
differently. Additionally, it would make it easier for admins to remove the
link if needed, by editing the panel (right now the link cannot be removed
from the interface, which is annoying if the admin doesn't want to setup an
OOo server and rather hide the feature).
On the XWiki/OfficeImporter page, the import feature is displayed even if
the OOo server is not currently running. Only after the user first tries to
import a file is the "Open Office Server not available" message displayed.
- If the OOo server isn't running when the user accesses the
XWiki/OfficeImporter page, a message should be displayed saying that:
- "You cannot import an Office document since the conversion server
has not been started. Please ask an administrator to get it started."
- If the current user is an admin, the message should read:
- "You cannot import an Office document since the conversion server
has not been started. You can start the OpenOffice server and
manage it from
this page (link to the OOo server administration page)."
On the XWiki/OfficeImporer page, the user is expected to know the name of
the space he will import the file into. This is not very user friendly.
- Provide a select box displaying a list of spaces before the input
field. If no space is selected (select box left empty), the value in the
input field is used. If the input field is empty as well, a warning asking
the user to choose a space is returned.
- Change the text to read: "Please select a space: [space select box] or
create a new one [create space input field]"
If the user tries to import an Office Document on a page that already
exists, an error message is dislayed but no "next step" is suggested.
- Ideally, when the user types the name of the page he wants to create, a
live JS validator should tell him whether the page already exists or not
- If the JS solution isn't possible: the message should be improved to
read:
- "The target document Main.WebHome already exists. Please try again
(link to the XWiki/OfficeImporter page) and choose another page name."
The XWiki/OfficeImporter page offers little explanations as to its purpose
and how it works.
- An additional line should be added at the top, between the title and
the import field, reading:
- "This page allows you to import Office Documents into your wiki. It
will turn the Office document you uploaded into a wiki page."
- "Document" should be renamed to "Select a document to import" next to
the input field
I'm aware there's a lot of data in here, I'll create a separate thread to
discuss a specific point if one of them turns out to be controversial.
Thanks for your feedback,
Guillaume
--
Guillaume Lerouge
Product Manager - XWiki
Skype ID : wikibc
http://guillaumelerouge.com/
Hi everyone,
We've just found that XE 1.8.1 is having some GWT service
initialization issue in multiwiki mode. All applications using the
XWiki GWT service fail on XE 1.8.1 (in multiwiki mode only).
More specifically this will affects users in multiki mode and using
the new WYSIWYG editor or XWiki Watch (both using GWT Services).
For those users we recommend to wait for XE 1.8.2 which is planned for
early next week (week of the 20th of April).
Sorry for the inconvenience.
-Vincent on behalf of the XWiki dev team
In http://groups.google.com/group/simile-widgets on Tue, Apr 14, 2009 at
11:08 PM, David Huynh <dfhuynh(a)alum.mit.edu> wrote:
I've updated the trunk to fix #1
http://trunk.simile-widgets.org/timeline/examples/compact-painter/compact-p…
Let me know how it feels.
This is a great improvement! I liked the new interface enough that I wanted
to try it out in Xwiki:
example:
http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/test
code:
http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/test?raw=1http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/StyleSheet?raw=1http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/DataJson?raw=1
Niels
http://nielsmayer.com
>
> Larry, if you have some time, I'd be grateful for some help on
> implementing your #2 point. It's been a while since I touch all the
> settings in Timeline and don't remember how they propagate. After that,
> maybe we should consider a 2.4 release.
>
> David
>
> David Huynh wrote:
> > OK, sounds like we have consensus... I'll implement them when I get a
> > chance.
> >
> > David
> >
> > John Callahan wrote:
> >
> >> I totally agree with both of Larry's cents. Items 1) and 2) as Larry
> >> described them would work very well for my applications.
> >>
> >> - John
> >>
> >>
> >>
> >> Larry Kluger wrote:
> >>
> >>
> >>> Hi,
> >>>
> >>> I like David's slim scrollbar, I think it's more attractive than the
> >>> usual windows toolbar.
> >>> I also agree with David's point that a standard window toolbar may
> >>> influence people away from realizing that they can scroll a Timeline
> >>> along the time axis.
> >>>
> >>> My 2 cents on the issue are:
> >>> 1) The scrollbar should always be visible if there are more events
> >>> than can be shown on the available tracks. It should be usable as a
> >>> handle for moving the Timeline since its affordance is to act as a
> handle.
> >>> (Affordance is a UI term. An object's affordance is the behavior that
> >>> we expect from an object, given its appearance and context.)
> >>>
> >>> 2) I think the bouncing off the top and bottom of the band effect is
> >>> great for when the touch gesture is used on an iPhone, iTouch, or some
> >>> of the newer Macs. But having it occur as the result of a
> >>> mouse-interaction doesn't feel right to me. I'd appreciate some way to
> >>> turn that behavior off and I don't recommend it as a default (except
> >>> when the browser has a touch interface).
> >>>
> >>> Note that Timeline works pretty well out of the box on the iTouch.
> >>> Enabling the Timeline to be scrolled vertically really solves one of
> >>> the few problems with Timeline on an iPhone etc. The only other issue
> >>> is to change the bubbles' show/hide UI when used with an iPhone.
> >>> That's on my list.
> >>>
> >>> Regards,
> >>>
> >>> Larry
> >>>
> >>>
> ------------------------------------------------------------------------
> >>> *From:* David Huynh <dfhuynh(a)alum.mit.edu>
> >>> *To:* simile-widgets(a)googlegroups.com
> >>> *Sent:* Wednesday, March 25, 2009 12:17:24 AM
> >>> *Subject:* Re: dragging vertically in timelines
> >>>
> >>>
> >>> David Karger wrote:
> >>>
> >>>
> >>>> you mean use a native vertical scrollbar? That would seem to create a
> >>>> "mixed metaphor" ui;
> >>>>
> >>>>
> >>> That was one of the reasons I didn't want to use a native vertical
> >>> scrollbar.
> >>>
> >>>
> >>>
> >>>> i am guessing you can come up with a better
> >>>> consistent metaphor. It took me quite a while to notice the vertical
> >>>> scrollbar, and I'm puzzled why it is "read only".
> >>>>
> >>>>
> >>>>
> >>> The intention is that it's only an indicator, and the body of the band
> >>> is the interactor.
> >>>
> >>> I think people ain't used to scrolling horizontally as much, so if
> >>> vertical scrolling were any more emphasized than it is, then that might
> >>> totally inhibit any hint that horizontal scrolling is possible. (A
> >>> native vertical scrollbar would really emphasize vertical scrolling.)
> >>> But I could be wrong.
> >>>
> >>>
> >>>
> >>>> farfetched, but what if you made the timeline into a "barrel" that
> >>>> rolled away at the top and bottom (images shrinking) to indicate there
> >>>> is more present?
> >>>>
> >>>>
> >>>>
> >>> "Barrel" like this?
> >>> http://z.about.com/d/ipod/1/0/e/3/-/-/iphone_gallery_10.jpg
> >>> I can add some gradients.
> >>>
> >>> David
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> > >
> >
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "SIMILE Widgets" group.
> To post to this group, send email to simile-widgets(a)googlegroups.com
> To unsubscribe from this group, send email to
> simile-widgets+unsubscribe(a)googlegroups.com<simile-widgets%2Bunsubscribe(a)googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/simile-widgets?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
Hi
I`m trying to figure a way to check if a user is a member of one group.
I`m looking for something like:
a) retrieve the groups membership of an user in velocity
or
b) check if a user is a member of a specify group.
Thanks in advance
Regards,
Bruno
walid.kharroubi(a)hraccess.com :
> but do you think it's possible to implement a streaming service in xwiki
> using groovy class with importing a streaming api(the streaming server will
> be vlc for example)?
>
Xwiki is better suited as a framework for creating and presenting streaming
applications but not for the actual streaming implementation. It is correct
to look at implementations specifically designed for streaming (e.g. VLC,
Darwin <http://developer.apple.com/opensource/server/streaming/index.html>,
etc) rather than trying to tame performance issues such as object/thread
overhead,. out-of-memory and running out of threads -- common issues when
many long-running streaming downloads occur in a servlet environment..
On the client end, Xwiki creates the HTML/CSS/javascript scaffolding, with
streaming implemented via streaming "plugins" in the web-browser (e.g.
mozilla plugin, a java applet or flash). These plugins could be accessed in
Xwiki via special velocity macros that cleanly encapsulate all the
scaffolding required to achieve this. The macro would allow easy
parametrization and placement of these "streaming UI objects" in a
Xwiki-based document/application.
For example VLC has a mozilla broser plugin that you can control with a
javascript API.
http://www.videolan.org/doc/play-howto/en/ch04.html#id310965 suggests the
following could be encapsulated within a velocity macro to implement this
functionality:
<embed type="application/x-vlc-plugin"
pluginspage="http://www.videolan.org" version="VideoLAN.VLCPlugin.2"
width="640"
height="480"
id="vlc">
</embed>
<script language="Javascript">
<!--
var vlc = document.getElementById("vlc");
vlc.audio.toggleMute();
!-->
</script>
In my experience, it is straightforward to integrate these kinds of things
with Xwiki, once you get adjusted to the possiblity of "computation"
happening in three places and at different times: browser, server and
plugin; and figuring out the dependencies and interactions therein.
Unfortunately, from a pragmatic perspective, expecting your users to install
VLC or other special browser plugins is the kiss-of-death. Most users will
just blow it off and move on to something else that uses Flash and "works
right out of the box" for the majority of users. (Therefore you can be
doctrinaire about being "purely open source" and it just means you'll be
strongly limiting your customer base and needlessly limiting your own
project's potential for success).
It would be nice to have a truly abstract streaming media macro that would
implement the same generic API for streaming media within Xwiki. The macro
would determine at run-time, whether the browser is enabled with specific
plugins needed to display a specific media type (such as the VLC moz
plugin); if not available, the macro would dynamically switch-in the
flash-based equivalent for people using IE or who don't want to install the
VLC moz plugin. For example given a "mp4", the macro would first attempt to
use VLC, on failure it might try the platform's browser-embeddable media
presenter if media-compatible (e.g. MS windows media), and would finally try
a "generic" flash player such as the Jeroen "JW" Wijering players (
http://www.longtailvideo.com/players/ ).
Who else is working on streaming media issues in Xwiki? Would love to see
some group interest and coding participation towards better integration of
streaming media in Xwiki.
Niels
http://nielsmayer.com
PS: some of my work-in-progress on some streaming clients in Xwiki (not
actual velocity macros yet, but at least they work).
http://nielsmayer.com/xwiki/bin/view/Macros/JW-Player?raw=1http://nielsmayer.com/xwiki/bin/view/Macros/YT-Chromeless?raw=1
Hai..
I'm trying to integrate the date picker to poll application date fields.
I would like to know is there a way that to set the object property name
(like $pobj.pollOpen) as the 'relative' in the javascript.
ex:
<script type="text/javascript">
var dpicker = new DatePicker({
relative : 'how to set the object parameter',
language: "$context.language"
});
</script>
Also I want to know that can we use the date picker inside the #info macro.
ex:#info("The poll is open from $pobj.pollOpen to $pobj.pollClose.")
Thank you.
~ Chathura Prabuddha Ganegoda~
Undergraduate,
Department of Computer Science & Engineering,
University of Moratuwa,
Sri Lanka.
http://gacpganegoda.blogspot.com/
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.9 Milestone 1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
First milestone of the XWiki Enterprise 1.9 version.
Main changes:
* New Office Importer feature: document splitting.
* Document syntax can be changed from the WYSIWYG editor.
Important bug fixes:
* Various bugfixes in syntax 2.0.
* Various bugfixes in the xwiki syntax 1.0 to 2.0 converter.
Note that general goals for XWiki Enterprise 1.9 are:
* Finish/stabilize/document new rendering
* Finish/stabilize/document new wysiwyg editor
* Finish/stabilize/document office importer + doc splitter/management
* Finish/stabilize/document webdav
* Finish/stabilize/document REST support
* Usability improvements
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise19M1
Thanks,
The XWiki dev team