May 2009 - xwiki-devs@xwiki.org

Re: [xwiki-devs] [xwiki-notifications] r19510 - in platform: core/trunk/xwiki-containers/xwiki-container-api/src/main/java/org/xwiki/container core/trunk/xwiki-containers/xwiki-container-api/src/main/resources/META-INF/plexus core/trunk/xwiki-containers/xwiki-container-portlet/src/main/java/org/xwiki/container/portlet core/trunk/xwiki-containers/xwiki-container-portlet/src/main/resources/META-INF/plexus core/trunk/xwiki-containers/xwiki-container-servlet/src/main/java/org/xwiki/container/servlet core/trunk/
by Sergiu Dumitriu 11 May '09

11 May '09

asiri (SVN) wrote: > Author: asiri > Date: 2009-05-07 21:16:03 +0200 (Thu, 07 May 2009) > New Revision: 19510 > > Added: > platform/core/trunk/xwiki-containers/xwiki-container-api/src/main/java/org/xwiki/container/ApplicationContextListener.java > platform/core/trunk/xwiki-containers/xwiki-container-api/src/main/java/org/xwiki/container/ApplicationContextListenerManager.java > platform/core/trunk/xwiki-containers/xwiki-container-api/src/main/java/org/xwiki/container/DefaultApplicationContextListenerManager.java > platform/core/trunk/xwiki-officeimporter/src/main/java/org/xwiki/officeimporter/internal/openoffice/OpenOfficeServerManagerApplicationContextListener.java > Modified: > platform/core/trunk/xwiki-containers/xwiki-container-api/src/main/resources/META-INF/plexus/components.xml > platform/core/trunk/xwiki-containers/xwiki-container-portlet/src/main/java/org/xwiki/container/portlet/DefaultPortletContainerInitializer.java > platform/core/trunk/xwiki-containers/xwiki-container-portlet/src/main/resources/META-INF/plexus/components.xml > platform/core/trunk/xwiki-containers/xwiki-container-servlet/src/main/java/org/xwiki/container/servlet/DefaultServletContainerInitializer.java > platform/core/trunk/xwiki-containers/xwiki-container-servlet/src/main/java/org/xwiki/container/servlet/XWikiPlexusServletContextListener.java > platform/core/trunk/xwiki-containers/xwiki-container-servlet/src/main/resources/META-INF/plexus/components.xml > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web/XWikiPortlet.java > platform/core/trunk/xwiki-officeimporter/src/main/java/org/xwiki/officeimporter/internal/openoffice/DefaultOpenOfficeServerConfiguration.java > platform/core/trunk/xwiki-officeimporter/src/main/java/org/xwiki/officeimporter/internal/openoffice/DefaultOpenOfficeServerManager.java > platform/core/trunk/xwiki-officeimporter/src/main/java/org/xwiki/officeimporter/openoffice/OpenOfficeServerConfiguration.java > platform/core/trunk/xwiki-officeimporter/src/main/resources/META-INF/plexus/components.xml > platform/xwiki-tools/trunk/xwiki-configuration-resources/src/main/resources/xwiki.properties.vm > Log: > XWIKI-3710: Add support for automatically restarting OpenOffice server when XE is restarted > > * Implemented. > > Added: platform/core/trunk/xwiki-containers/xwiki-container-api/src/main/java/org/xwiki/container/DefaultApplicationContextListenerManager.java > =================================================================== > --- platform/core/trunk/xwiki-containers/xwiki-container-api/src/main/java/org/xwiki/container/DefaultApplicationContextListenerManager.java (rev 0) > +++ platform/core/trunk/xwiki-containers/xwiki-container-api/src/main/java/org/xwiki/container/DefaultApplicationContextListenerManager.java 2009-05-07 19:16:03 UTC (rev 19510) > + public void initializeApplicationContext(ApplicationContext applicationContext) > + { > + try { > + List<ApplicationContextListener> initializers = > + componentManager.lookupList(ApplicationContextListener.class); > + for (ApplicationContextListener initializer : initializers) { I'd say that you should surround this line with a try catch block, so that a broken listener doesn't break the entire notification. > + initializer.initializeApplicationContext(applicationContext); > + } > + } catch (ComponentLookupException ex) { > + getLogger().error(ex.getMessage(), ex); > + } > + } > + > + /** > + * {@inheritDoc} > + */ > + public void destroyApplicationContext(ApplicationContext applicationContext) > + { > + try { > + List<ApplicationContextListener> initializers = > + componentManager.lookupList(ApplicationContextListener.class); > + for (ApplicationContextListener initializer : initializers) { Same here. > + initializer.destroyApplicationContext(applicationContext); > + } > + } catch (ComponentLookupException ex) { > + getLogger().error(ex.getMessage(), ex); > + } > + } > +} -- Sergiu Dumitriu http://purl.org/net/sergiu/

1 0

[xwiki-devs] plugin to another webapp?
by Paul Libbrecht 10 May '09

10 May '09

Hello XWikiers, do I have a possibility for a plugin to access the classes of another webapp? Can this other webapp maybe offer some services shareable to others? (JNDI?) thanks in advance paul

3 8

[xwiki-devs] 1.9m2?
by Lilianne E. Blaze 10 May '09

10 May '09

According to http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap 1.9m2 is due at 4 may? Was it changed / is there an ETA yet / what exactly is blocking it? Greetings, Lilianne

2 2

Re: [xwiki-devs] Xwiki+Simile Exhibit integration // request for help w/ portability issue
by Niels Mayer 10 May '09

10 May '09

On Sat, May 9, 2009 at 10:04 AM, David Huynh <dfhuynh(a)alum.mit.edu> wrote: > Looking at the HTML source, I see > <div ex:role="coder" ex:coderClass="Color" > id="party-colors"> > Republican > Democratic > Other > parties > Many > parties > No party > </div> > I think the is causing problem. Could you remove it and see if that > helps? That was exactly the problem! Thank you so much, as that's one I would have never spotted myself! FYI, here's what happened: Since I just cut/paste the HTML from view-source on the presidents example on simile-widgets.org, the newlines got interpreted as paragraphs by the wiki-engine in Xwiki. So, I removed the extra newline in Exhibit.Presidents2, and it now works in IE! This is a "gotcha" I frequently hit in Xwiki, although I find the ability to mashup HTML and wikitext in an active document quite useful. Now both the "standalone" http://nielsmayer.com/xwiki/bin/view/Exhibit/Presidents2 and locally-hosted-exhibit http://nielsmayer.com/xwiki/bin/view/Exhibit/Presidents work in IE! Thanks again and also thanks for Exhibit which is just all around great! The updated XAR (zip format) of "Presidents2" example is here: http://nielsmayer.com/xwiki/bin/download/Exhibit/Presidents2/Exhibit.Presid… Length Date Time Name -------- ---- ---- ---- 94080 05-09-09 10:30 Exhibit/Presidents2.xml 2226 05-09-09 10:30 Exhibit/PresidentsSchemaJSON.xml 29379 05-09-09 10:30 Exhibit/PresidentsJSON.xml 544 05-09-09 10:30 package.xml -------- ------- 126229 4 files Niels http://nielsmayer.com PS: After sending the announcement yesterday, I realized there was one issue that makes this example not quite standalone. Exhibit.PresidentsPkg.xar contains a hard-coded google-maps key that you receive when registering your site <http://code.google.com/apis/maps/signup.html>. You'll need to change "gmapkey" setting in object XWiki.JavaScriptExtension[2] on document "Exhibit.Presidents2": > params: { bundle: true, authenticated: false, autoCreate: false, safe: > false, gmapkey: "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", views: "timeline,map" } Until this is changed, you'll get a dialog box from google saying you need to register. When you click away the dialog box, it should load the interface even if not correctly registered. PPS: What does this Exhibit parameter setting do, and what is the correct value: namespace: "http://simile.mit.edu/2006/11/exhibit#", (also in object XWiki.JavaScriptExtension[2] on document "Exhibit.Presidents2)

1 1

[xwiki-devs] Xwiki+Simile Exhibit integration // request for help w/ portability issue
by Niels Mayer 09 May '09

09 May '09

Although I was previously able to do a hack integration with Simile's Exhibit and Xwiki, it was too heinous to actually live with. A cleaner solution, using Xwiki's "skin extensions" for stylesheets and javascript now works. The "clean" solution required hosting my own copy of Exhibit based on checking out from the trunk the latest copy of "Exhibit." Hosting my own copy of Exhibit seems to be problematic, as the version of Exhibit I checked out from svn/trunk has issues such as (1) a non-working minified jquery that needed to be replaced w/ original, and (2) portability issue on IE (see below) on which I need help/advice. Here's my example of Xwiki/Exhibit integration: http://nielsmayer.com/xwiki/bin/view/Exhibit/Presidents Here's the original example from which above was derived: http://simile-widgets.org/exhibit/examples/presidents/presidents.html Xwiki Source Code: Presidents<http://nielsmayer.com/xwiki/bin/view/Exhibit/Presidents?viewer=code> Data used by example: PresidentsSchemaJSON<http://nielsmayer.com/xwiki/bin/view/Exhibit/PresidentsSchemaJSON?xpage=pla…>, PresidentsJSON<http://nielsmayer.com/xwiki/bin/view/Exhibit/PresidentsJSON?xpage=plain> Attached, because there's no easy way to view these, the contents of XWiki.StyleSheetExtension[0] and XWiki.JavaScriptExtension[0] -- these are objects attached to the underlying Xwiki document http://nielsmayer.com/xwiki/bin/view/Exhibit/Presidents which cause the appropriate magic to happen in the header via calls to $xwiki.ssx.use("$doc.fullName") and $xwiki.jsx.use("$doc.fullName"). It's all explained in the preamble for http://nielsmayer.com/xwiki/bin/view/Exhibit/Presidents?viewer=code : > ## Note that to get this whole thing working requires jquery NOT FROM > EXHIBIT SVN TRUNK > ##( http://nielsmayer.com/js/exhibit/api/scripts/jquery-1.3.2.min.js ) > ## Instead, preload > http://nielsmayer.com/xwiki/resources/js/exhibit/api/scripts/jquery-1.3.2.m… > ## for details see > http://nielsmayer.com/xwiki/resources/js/exhibit/api/scripts/jquery-1.3.2.m… > $xwiki.jsfx.use("js/exhibit/api/scripts/jquery-1.3.2.min.js")## > ## Note that > http://nielsmayer.com/xwiki/resources/js/exhibit/api/exhibit-api.jsdifferent > ## to trunk http://nielsmayer.com/js/exhibit/api/exhibit-api.js > $xwiki.jsfx.use("js/exhibit/api/exhibit-api.js")## > ## though > http://nielsmayer.com/xwiki/resources/js/Simile/Exhibit/webapp/styles.csswo… the line below does not: > ##$xwiki.ssfx.use("js/simile/Exhibit/webapp/styles.css")##same loaded from > XWiki.StyleSheetExtension[0] via ssx.use. > $xwiki.ssx.use("$doc.fullName")## > $xwiki.jsx.use("$doc.fullName")## > ------------ ISSUE AND REQUEST FOR HELP: In IE, after the simile busy-spinner has popped up indicating a successful load of Exhibit, the following errors happen, causing three successive dialog boxes: (1) "Caught exception: ColorCoder: Error processing configuration of coder Details: 'firstChild.nodeValue' is null or not an object (2) Caught exception: undefined Details: 'firstChild.nodeValue' is null or not an object (3) IE error: Line 1831, char 52, Error: object expected Suggestions on which version of "Exhibit" or "Simile-Ajax-API" to use in order to get rid of this error would be appreciated. It is interesting to note that the "trunk" version of the same example http://trunk.simile-widgets.org/exhibit/examples/presidents/presidents.html… fine in IE. Is this the same issue noted previously: http://www.mail-archive.com/[email protected]/msg00385.html http://www.mail-archive.com/[email protected]/msg00391.html http://www.mail-archive.com/[email protected]/msg00846.html??? ---------- TODO: One last remaining hack is that I put the following in the headers > <link rel="exhibit/data" type="application/json" > href="$xwiki.getURL("Exhibit.PresidentsSchemaJSON","view","xpage=plain")" /> > <link rel="exhibit/data" type="application/json" > href="$xwiki.getURL("Exhibit.PresidentsJSON","view","xpage=plain")" /> > via the "Exhibit" space's "HTTP Meta Information" administration setting ( http://nielsmayer.com/xwiki/bin/admin/Exhibit/WebPreferences?editor=spacead…) I would like to figure out a way to set these values directly in javascript inside the document itself (or inside additional instances of XWiki.JavaScriptExtension) rather than having them read as external json files, e.g. http://www.mail-archive.com/[email protected]/msg02434.html http://www.nabble.com/JSON-created-locally-td17507332.html http://www.patrickgmj.net/node/161 -- Niels. http://nielsmayer.com

2 2

[xwiki-devs] Running Sellinium Tests XWIKI-3697
by Tharindu Madushanka 08 May '09

08 May '09

Hi, I have completed sending loging / logout observation events and trying to write integration test for the task. I have written a test case similar to the attached file. I want to clear few things about it. As well as I got few issues while trying to run. *Question 1* - I think this test should check my observation event sending - Please comment on if there is any mistake on groovy script added to createPage() content. *Question 2 *- On running the selinium tests Test is named LoginObservationTest After writing the test case, For first time run, I went to /enterprise/distribution-test/selenium-tests directory and run the following command as in tutorial mvn install -Dpattern=LoginObservationTest It showed an error saying java.lang.RuntimeException: Firefox couldn't be found in the path! Please add the directory containing 'firefox-bin' to your PATH environment variable, or explicitly specify a path to Firefox like this: *firefox /blah/blah/firefox-bin Then I have linked the firefox folder as it was suggested in this http://willbryant.net/software/2008/05/26/selenium_rc_firefox_2_on_ubuntu_h… But in my case I have firefox-3.0.10 and inside that I had firefox binary not a file named firefox-bin Then I linked to path like this. sudo ln /usr/lib/firefox-3.0.10/firefox /usr/lib/firefox/firefox-bin Now I get an exception like this when I run the command to test my selenium test :( ------------------------------------------------------- T E S T S ------------------------------------------------------- Running com.xpn.xwiki.it.selenium.AllTests 09:59:44,591 INFO [org.mortbay.util.Credential] Checking Resource aliases 09:59:44,602 INFO [org.openqa.selenium.server.SeleniumDriverResourceHandler] Command request: getNewBrowserSession[*firefox, http://localhost:8080, ] on session null 09:59:44,603 INFO [org.openqa.selenium.server.BrowserSessionFactory] creating new remote session 09:59:44,936 INFO [org.openqa.selenium.server.BrowserSessionFactory] Allocated session 775dad4fbed24b0e98a86c0652ec136c for http://localhost:8080, launching... 09:59:45,092 INFO [org.openqa.selenium.server.browserlaunchers.FirefoxCustomProfileLauncher] Preparing Firefox profile... Could not read application.ini 10:00:05,235 WARN [org.mortbay.http.HttpConnection] POST /selenium-server/driver/ HTTP/1.1 java.lang.RuntimeException: Timed out waiting for profile to be created! Kindly tell me some tips to solve this. Thank you, -Tharindu

4 3

Re: [xwiki-devs] [xwiki-notifications] r19499 - in platform/web/trunk: standard/src/main/webapp/templates wysiwyg wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/client/plugin/table wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/client/plugin/table/feature wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/client/plugin/table/ui
by Sergiu Dumitriu 08 May '09

08 May '09

Marius Dumitru Florea wrote: > We should keep the buttons and let the user choose whether he wants to > use the tool bar, the menu bar or both, by changing the configuration. > By default we put table features in the menu. But in some cases we'll > have to drop the menu and use only the tool bar with a few features in > order to have a compact editor. In this case the user might want to have > the insert table button on the tool bar. +1. We must not forget that the editor is supposed to be generic, and that shortly we'll want it to be reusable outside XWiki. Thus, "customizability" is a key objective. -- Sergiu Dumitriu http://purl.org/net/sergiu/

1 0

Re: [xwiki-devs] [xwiki-notifications] r19471 - platform/web/branches/xwiki-web-1.8/wysiwyg/src/main/resources/com/xpn/xwiki/wysiwyg/client/editor
by Sergiu Dumitriu 07 May '09

07 May '09

jvdrean (SVN) wrote: > Author: jvdrean > Date: 2009-05-07 15:47:17 +0200 (Thu, 07 May 2009) > New Revision: 19471 > > Modified: > platform/web/branches/xwiki-web-1.8/wysiwyg/src/main/resources/com/xpn/xwiki/wysiwyg/client/editor/Strings.properties Shouldn't this file be posted on l10n.xwiki.org? -- Sergiu Dumitriu http://purl.org/net/sergiu/

2 3

[xwiki-devs] Embedded ComponentManager
by Vincent Massol 07 May '09

07 May '09

Devs, This is to let you know that I've started working on a very simple and lightweight ComponentManager implementation that I'd like to use for 2 use cases: 1) External users who want for ex to use some xwiki components without using the plexus would be able to use it with no additional dependencies (it'll be in our xwiki-component module) 2) Our unit/integration tests could use it and this will allow us to have component mocks and thus prevent duplicating for ex MockDocumentAccessBridge 10 times and allow the test to control the component mock behavior using jmock I'm planning to finish it over the week end. Please let me know quickly if you see an issue with 1) or 2). Thanks -Vincent

1 0

[xwiki-devs] [PROPOSAL] Always store document names as fully qualified names
by Thomas Mortagne 07 May '09

07 May '09

Hi devs, The real full qualified name of a document is wiki:Space.Page. I think we sould always use only this form for technical purposes like storing in database or old API which does not support DocumentName. pros: - don't need to take care of the context, the information is always right. - if everything is stored in only one form it's way easier to compare things and do requests cons: - old code which does not support this document name form will fail. This could hardly be a good arguments since this form is a officially valid document name but i can't see anything else. Among others, the last use case which make me send this proposal is http://jira.xwiki.org/jira/browse/XWIKI-3754. IMO getLinkedPages return and the link table should only contains fully qualified links, especially since theses lists are supposed to contains uniques documents and we need to know the 3 parts of the document name to make sure of that . Note that a document could contain a link to a document in another wiki or even a link to the same document but written in its full form so a code which support only local form is wrong anyway. WDYT ? Here is my +1. The pros are basically the same that make us introduce DocumentName to not manipulate String anymore in code. -- Thomas Mortagne

7 13