Hi Devs,
As reported @ http://jira.xwiki.org/jira/browse/XWIKI-3288 and
http://jira.xwiki.org/jira/browse/XAOFFICE-10, OfficeImporter wysiwyg plugin
has issues with importing some documents on some platforms.
When importing documents from the wysiwyg plugin, the approach we follow is
to upload the file that need to be imported into the current page and then
import the corresponding attachment. But this scheme has two problems:
1) If the file being uploaded contains special characters, the attachment
name will be different from the file name. And this will cause the
officeimporter to fail because after uploading the file we will be making a
second request to import the attachment with the original file name (but now
there is no such attachment).
2) The fileName returned by GWT FileUpload widget is different from Firefox
to IE. While Firefox returns the file name, IE returns the whole file path.
This causes the officeimporter wysiwyg plugin to fail completely under IE
(File Import Tab only).
The solution I can see is the following,
1) Upload the file as an attachment just as before.
2) Make a second rpc call. This RPC call will import the latest attachment
to the current page by the current user. This way we don't need to worry
about crappy file names and browser specific stuff.
I know it's a bit ugly but it will work.
WDYT?
Thanks.
Hello,
I am inderested with "XWiki Jabber, Google Talk, Skype Integration" idea.
There Jabber and gtalk both are XMPP based chat server. For any XMPP
we can use smack api. personal servers also can be integrated, my idea
is to create a common interface for any XMPP based chat server.
And for skype intregration can be possible using skype client api.
I was worked in a project of social networking server using J2EE,
which has a module for chat with its own XMPP server(Open Fire). I was
worked on this module.
This past experience make me interested for the "XWiki Jabber, Google
Talk, Skype Integration" idea. Hope I have the ability to contribute a
little to open source XWiKi project.
--
--------------------------------------------------------------
Regards,
Shamal Roy
For once, let's self-congratulate ourselves. I want to thank everyone
who has participated to the development of the XWiki Enterprise 1.8
release. I know all committers have been extremely busy, working night
and days, and the work they have all achieved is tremendous. Well done
guys!
Thanks
-Vincent
PS: Now let's finish completely this new rendering/wysiwyg for 1.9
final :)
fmancinelli (SVN) wrote:
> Author: fmancinelli
> Date: 2009-03-23 22:15:24 +0100 (Mon, 23 Mar 2009)
> New Revision: 17953
>
> Modified:
> platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiUtils.java
> platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java
> Log:
> XWIKI-3449: Authenticated XWiki user name might be incorrect in XMLRPC login
> XWIKI-3450: Allow guest access to be disabled in XMLRPC
> + /* Check if we must grant access when no token is provided */
> + boolean allowGuest = context.getWiki().ParamAsLong("xwiki.authentication.always", 0) != 1;
> +
Fabio, you are using this parameter wrong. This doesn't mean that only
authenticated users are allowed, but it controls the optimization done
by Thomas, which is to only check the authentication only if there is no
Principal in the session. This parameter forces to check the cookies at
each request instead of using the session object.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hello,
I am planning to submit an application for the upcoming Google Summer of
Code 2009
to develop a collaborative drawing/mapping application for xwiki using
GWT but with
some variation.
I intend to achieve this by developing a web front end to the Compendium
Mapping tool.
Compendium is very flexible concept mapping tool that was recently fully
open-sourced.
It is extensible through the use of 'stencils' which allow for modelling
in other modelling
languages such as UML.
I would like to know what you think about this. Your input will be very
much appreciated.
Kind Regards,
Kojo Gambrah-Sampaney.
Hi all,
When the XWiki class is instantiated, it is done in a way that made it
almost singleton, except for one special case that seems to be for
test purposed, but I feel it is now useless. I am asking because if
XWiki is a singleton, some very often used synchronisation could be
optimized to avoid useless locking.
Here is the excerpt from getMainXWiki() that shows this special case:
String xwikiname = "xwiki";
XWiki xwiki = null;
XWikiEngineContext econtext = context.getEngineContext();
try {
if (context.getRequest().getRequestURL().indexOf("/
testbin/") != -1) {
xwikiname = "xwikitest";
context.setDatabase("xwikitest");
context.setOriginalDatabase("xwikitest");
}
} catch (Exception e) {
}
context.setMainXWiki(xwikiname);
Anyone knows for what it was ? is it still in use ? could it be
removed ?
Denis
On Mar 24, 2009, at 8:36 AM, asiri (SVN) wrote:
> Author: asiri
> Date: 2009-03-24 08:36:32 +0100 (Tue, 24 Mar 2009)
> New Revision: 17954
>
> Modified:
> platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentModelBridge.java
> platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentName.java
> platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/
> XWikiDocument.java
> Log:
> XWIKI-3427: Introduce DocumentModelBridge.setParent() method
>
> * Changed tha parameter type of setParent() method from
> DocumentModelBridge to DocumentName.
>
> Modified: platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/
> bridge/DocumentModelBridge.java
> ===================================================================
> --- platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentModelBridge.java 2009-03-23 21:15:24 UTC (rev 17953)
> +++ platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentModelBridge.java 2009-03-24 07:36:32 UTC (rev 17954)
> @@ -30,11 +30,11 @@
> public interface DocumentModelBridge
> {
> /**
> - * Sets the parent document attribute of this document to the
> given value.
> + * Sets the parent document name attribute for this document.
> *
> - * @param parent the {@link DocumentModelBridge} representing
> the parent document.
> + * @param parentName name of the parent document.
> */
> - void setParent(DocumentModelBridge parent);
> + void setParent(DocumentName parentName);
>
> /**
> * Retrieve the full name of the document, in the
> <code>Space.Name</code> format, for example <tt>Main.WebHome</tt>.
>
> Modified: platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/
> bridge/DocumentName.java
> ===================================================================
> --- platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentName.java 2009-03-23 21:15:24 UTC (rev 17953)
> +++ platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentName.java 2009-03-24 07:36:32 UTC (rev 17954)
> @@ -77,4 +77,14 @@
> {
> return this.page;
> }
> +
> + /**
> + * Converts this {@link DocumentName} into a string
> representation.
> + *
> + * @return a string representing this {@link DocumentName} of
> the form wiki:space.page.
> + */
> + public String toString()
> + {
> + return getWiki() + ":" + getSpace() + "." + getPage();
This will fail if the wiki, space or page are null.
Note that the serializer should resolve not specified values when
calling getXXX() using current wiki/space. You can do this by
injecting the Execution component and accessing the XWikiContext. Then
you can call getDoc().getSpace() to get the current space. Use
"WebHome" when the page isn't specified and use getDatabase() when the
wiki isn't specified.
Also you should create a DocumentNameSerializer() interface and a
DefaultDocumentNameSerializer implementation:
String serialize(DocumentName();
Then refactor XWikiDocument to use DocumentNameSerializer in
setFullName()
Thanks
-Vincent
> + }
> }
>
> Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> doc/XWikiDocument.java
> ===================================================================
> --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/
> XWikiDocument.java 2009-03-23 21:15:24 UTC (rev 17953)
> +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/
> XWikiDocument.java 2009-03-24 07:36:32 UTC (rev 17954)
> @@ -71,6 +71,7 @@
> import org.suigeneris.jrcs.rcs.Version;
> import org.suigeneris.jrcs.util.ToString;
> import org.xwiki.bridge.DocumentModelBridge;
> +import org.xwiki.bridge.DocumentName;
> import org.xwiki.rendering.block.Block;
> import org.xwiki.rendering.block.HeaderBlock;
> import org.xwiki.rendering.block.LinkBlock;
> @@ -570,9 +571,9 @@
> /**
> * {@inheritDoc}
> */
> - public void setParent(DocumentModelBridge parent)
> - {
> - this.parent = parent.getFullName();
> + public void setParent(DocumentName parentName)
> + {
> + this.parent = parentName.toString();
> }
>
> public String getFullName()
Hi guys! I'd like to know what you think about this matter, which has
been raised on http://jira.xwiki.org/jira/browse/XWIKI-3375.
As I posted there, this is what I think:
-the parameters for the two macros are completely different, so i see no
point for having the box specific parameters (cssClass, title, image,
width and blockTitle) among the rss macro's ones, this will lead to
confusion for the user. The box parameters are deduced from the rss
feed's properties and then passed to the box macro. No need for them to
be exposed in the Rss Macro. Therefore, extending the RssMacroParameters
from the BoxMacroParameters is unreliable.
-extending the RssMacro from the AbstractBoxMacro<RssMacroParameters>
doesn't mean simply implementing AbstractBoxMacro.parseContent instead
of Macro.execute. Currently, most of the code about the box around the
css macro is placed in the box macro's implementation, which is
DefaultBoxMacro, so we do make use of the existing implementations.
Giving up using the box macro internally means giving up using most of
the features already presented in the box macro and rewriting them
-and finally, the most time costing disadvantage is that extending the
rss macro from the box basically means rewriting this macro from
scratch, because it involves redesigning it, task that will cost us time.
So, therefore, I'm -1 for this.
Tnx,
Dan
Hello,
<br><br>I had the same problem.
<br>I have 2 PCs: the first one with a JRE 5 and the all-in-one installer exe bundle worked perfectly. PC no. 2, JDK 5, Tomcat 5.5 and Postgres using the war file - not OK, I had this problem.
<br><br>My resolution to this problem: I have upgraded my JDK to 6, and I don't have the problem any more. This is curious as I compared the dirs & files from the 2 distributions and they were identical. So I didn't have to download this file: jcip-annotations-1.0.jar. I am guessing that the system tries to look for that file only in some cases, and if jdk 6 is installed, it doesn't need this lib any more.
<br><br>Best regards,
<br>CS.
--
View this message in context: http://n2.nabble.com/XWikiException-Unable-to-build-interceptor-chain-tp131…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
Just to quickly introduce myself. My name is Anamaria Stoica, and I'm
studying Computer Science at University "Politehnica" of Bucharest. I'm
currently in the 5th year. (graduation year)
I have a 2 year experience working with Java SE & EE on the ITerating.com
platform (http://www.iterating.com) (also with JS, AJAX, HTML&CSS). The team
(less than 10 members) was spread out in several countries (but mostly in
Romania) and worked remotely.
My working experience also includes a summer internship (in 2008) at Cresta
Technology, Inc. (http://www.crestatech.com) in Santa Clara, CA. There I
worked as a Software Engineer Intern.
Regarding the "Anti Vandalism Filters" project, before today it had as a
developer requirement Machine Learning knowledge.
I loved the idea of the project since the first time I saw it, not only
because of the Machine Learning component in which I have recently developed
a lot of interest, but also of the project as a whole.
So, my question is: does the project still imply some work on ML Algorithms,
just that it isn't a strong requirement as before or has that change ?
Also, will the project use some other components already developed towards
this end ?
Thanks in advance,
Anamaria