xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

Re: [xwiki-devs] [xwiki-notifications] [xwiki/xwiki-platform] f438eb: XWIKI-6741: Move all retro compatibility aspects t...

by Caleb James DeLisle

I see that this patch removed parseMessage() entirely as evidenced by broken login tests. Although I am very happy to see deprecated API removed, I'm not sure it's what you wanted. Caleb On 07/26/2011 04:04 AM, noreply(a)github.com wrote: > Branch: refs/heads/feature-legacyprojects > Home: https://github.com/xwiki/xwiki-platform > > Commit: f438eb421f58d22ca4a1e32aebdde36e08580448 > https://github.com/xwiki/xwiki-platform/commit/f438eb421f58d22ca4a1e32aebdd… > Author: tmortagne <thomas.mortagne(a)gmail.com> > Date: 2011-06-24 (Fri, 24 Jun 2011) > > Changed paths: > M xwiki-platform-core/xwiki-platform-application-manager/xwiki-platform-application-manager-api/pom.xml > M xwiki-platform-core/xwiki-platform-legacy/pom.xml > R xwiki-platform-core/xwiki-platform-legacy/src/main/java/com/xpn/xwiki/plugin/ldap/LDAPPlugin.java > R xwiki-platform-core/xwiki-platform-legacy/src/main/java/com/xpn/xwiki/plugin/ldap/LDAPPluginApi.java > R xwiki-platform-core/xwiki-platform-legacy/src/main/java/com/xpn/xwiki/user/impl/LDAP/LDAPAuthServiceImpl.java > R xwiki-platform-core/xwiki-platform-legacy/src/main/java/org/xwiki/annotation/internal/AnnotationVelocityContextInitializer.java > R xwiki-platform-core/xwiki-platform-legacy/src/main/java/org/xwiki/legacy/internal/LegacyEventDispatcher.java > R xwiki-platform-core/xwiki-platform-legacy/src/main/java/org/xwiki/observation/event/AbstractDocumentEvent.java > R xwiki-platform-core/xwiki-platform-legacy/src/main/java/org/xwiki/observation/event/DocumentDeleteEvent.java > R xwiki-platform-core/xwiki-platform-legacy/src/main/java/org/xwiki/observation/event/DocumentSaveEvent.java > R xwiki-platform-core/xwiki-platform-legacy/src/main/java/org/xwiki/observation/event/DocumentUpdateEvent.java > R xwiki-platform-core/xwiki-platform-legacy/src/main/resources/META-INF/components.txt > R xwiki-platform-core/xwiki-platform-legacy/src/test/java/org/xwiki/observation/DocumentEventTest.java > R xwiki-platform-core/xwiki-platform-legacy/src/test/java/org/xwiki/observation/event/LegacyEventDispatcherTest.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-annotation/pom.xml > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-annotation/src/main/java/org/xwiki/annotation/internal/AnnotationVelocityContextInitializer.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-annotation/src/main/resources/META-INF/components.txt > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-observation/pom.xml > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-observation/src/main/java/org/xwiki/observation/event/AbstractDocumentEvent.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-observation/src/main/java/org/xwiki/observation/event/DocumentDeleteEvent.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-observation/src/main/java/org/xwiki/observation/event/DocumentSaveEvent.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-observation/src/main/java/org/xwiki/observation/event/DocumentUpdateEvent.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-observation/src/main/java/org/xwiki/observation/legacy/LegacyEventDispatcher.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-observation/src/main/resources/META-INF/components.txt > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-observation/src/test/java/org/xwiki/observation/DocumentEventTest.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-observation/src/test/java/org/xwiki/observation/legacy/LegacyEventDispatcherTest.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-oldcore/pom.xml > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/XWikiCompatibilityAspect.aj > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-oldcore/src/main/java/com/xpn/xwiki/plugin/ldap/LDAPPlugin.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-oldcore/src/main/java/com/xpn/xwiki/plugin/ldap/LDAPPluginApi.java > A xwiki-platform-core/xwiki-platform-legacy/xwiki-platform-legacy-oldcore/src/main/java/com/xpn/xwiki/user/impl/LDAP/LDAPAuthServiceImpl.java > M xwiki-platform-core/xwiki-platform-oldcore/pom.xml > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/XWikiCompatibilityAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/XWikiContextCompatibilityAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/api/ApiCompatibilityAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/api/ContextCompatibilityAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/api/DocumentCompatibilityAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/api/StatsServiceCompatibilityAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/api/XWikiCompatibilityAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/doc/XWikiDocumentCompatibilityAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/objects/BaseCollectionCompatibiityAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/plugin/PluginApiAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/stats/impl/StatsUtilCompatibilityAspect.aj > R xwiki-platform-core/xwiki-platform-oldcore/src/main/aspect/compatibility/com/xpn/xwiki/web/UtilsCompatibilityAspect.aj > > Log Message: > ----------- > XWIKI-6741: Move all retro compatibility aspects to xwiki-legacy > > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications >

13 years, 5 months

[xwiki-devs] Building XWiki with Jenkins

by Ashleigh Ings-Lamb

Hi I have forked and cloned XWiki Enterprise and XWiki commons from Github and am trying to build Enterprise using Jenkins as part of an MSc project looking at cloud software testing and development but am receiving the following error: message : Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.2.1:bundle (default) on project xwiki-commons-tool-license-resources: Error creating remote resources manifest. cause : Error creating remote resources manifest. Stack trace : org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.2.1:bundle (default) on project xwiki-commons-tool-license-resources: Error creating remote resources manifest. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) . . . . Any pointers/help on how to solve this would be greatly appreciated. Thank you very much Ash Lamb (MSc candidate University of St Andrews) p.s. apologies if this is not the correct place to ask this question but an extensive web search and troubleshooting session have not been able to find a fix for this.

13 years, 5 months

[xwiki-devs] unresolved artifact

by Ashleigh Ings-Lamb

Hi Does anyone know where I can download org.xwiki.platform:xwiki-platform-legacy:jar:3.2-SNAPSHOT as it is the last unresolved artifact I need to build XWiki Enterprise. Thanks! -- Ash

13 years, 5 months

[xwiki-devs] ReSTful API example uses what full URL path?

by Mark Wallace

Looking at http://platform.xwiki.org/xwiki/bin/view/Features/XWikiRESTfulAPI#HCustomre…... If I create this class: package org.xwiki.contrib.rest; import javax.ws.rs.DefaultValue; import javax.ws.rs.GET; import javax.ws.rs.Path; import org.xwiki.component.annotation.Component; import org.xwiki.rest.XWikiResource; @Component("org.xwiki.contrib.rest.HelloWordResource") @Path("/myresources/{myresourcename}") class HelloWorldResource extends XWikiResource { @GET public String get(@PathParam("myresourcename") @DefaultValue("world") String myresourcename) { return "Hello " + myresourcename; } } Then what is the exact URI I use to access it. E.g. something like http://localhost:8080/myresources/test? Not sure exactly what full URL is. Thanks, -Mark

13 years, 5 months

[xwiki-devs] [xwiki-users] Task Manager app (fwd)

by Kevin P. Foote

Apologies in advance for the xpost. Can anyone provide some help with the, probably old, xwiki TaskManager app [1].. I've installed it -semi successfully- on xwiki 3.0... but now some of the stock macros have an odd look to them. Perhaps something got overwritten in the css / look area on the xar import. looks like css -> div.box.code got modified but I don't know where [1] http://extensions.xwiki.org/xwiki/bin/view/Extension/Task+Manager+Applicati… ------ thanks kevin.foote

13 years, 5 months

[xwiki-devs] How to write HQL queries for recently modified pages under a specific space

by 许凌志(Jamesxu)

I use $xwiki.searchDocuments(*'where doc.space='Main' order by doc.date desc *', 5, 0) to query for recently modified pages under a specific space "Main", but when I am executing it, error returns. Could anyone can tell me what is the problem with the query -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

13 years, 5 months

[xwiki-devs] page delete hook.

by Karel Gardas

Hello, I'm curious if there is any kind of hook or script or code executed when the page from the XWiki is deleted and which might be easily enhanced. I'm asking since during the page creation I also modify external database (page template do this) and if page is deleted the data in external db shall be also deleted to be consistent. Thanks! Karel

13 years, 5 months

[xwiki-devs] |PROPOSAL] Move all retro-compatibility aspects into xwiki-legacy

by Thomas Mortagne

Hi devs, Here is the general idea: I would like to start doing important cleanup to oldcore project by moving aspect to xwiki-legacy and deprecated stuff hard to move right now. Here are the pros: * we will be able to move a lots of deprecated classes like the old event system and some others to xwiki-legacy. It's very hard now because of methods using theses APIs in XWiki class * oldcore will be quicker to build (no aspectj build anymore) * that way we make sure we don't use any deprecated APIs in platform Along with it I would also like to start separating xwiki-legacy in sub modules. In details it means that there will be two xwiki-oldcore jars, the "normal" one and the one including aspects and legacy classes. Projects will depends on the first one and the second one will actually be packaged with XE/XEM. And It will basically be the same for any other project with aspect based retro-compatibility. You can have a look at the current state which is pretty much ready to merge (need to update some code that is still using deprecated API) in https://github.com/xwiki/xwiki-platform/tree/feature-legacyprojects. Right now only oldcore have a conflicting jar package, other legacy modules are like xwiki-legacy used to be: they just contains some deprecated classes and bridges but they are not repackaging the non legacy jar because it's not really needed (no aspects). There is lots of more things to move but I would like to validate the idea and we will move stuff later. WDYT ? here is my +1 -- Thomas Mortagne

13 years, 5 months

Re: [xwiki-devs] XWiki/XEclipse template/form system.

by Eduard Moraru

Hi Karel, Don`t forget about textareas :) It would be nice if you could, when you finish the project, cotribute it as a feature of XEclipse. The REST templates service could become a part of XE as well. Thanks, Eduard On Mon, Aug 8, 2011 at 11:40 AM, Karel Gardas <karel.gardas(a)centrum.cz>wrote: > > Hi Eduard, > > thanks a lot for your help with this. Indeed, your JS kind of works. I've a > little bit fixed this and now I'm using: > > String js = "function > getFormData() {\n"; > js = js + "var formData = > {};\n"; > js = js + "var stringData = > '';\n"; > js = js + "var inputs = > document.getElementsByTagName(**'input');\n"; > js = js + "for (var i = 0; i > < inputs.length; ++i) {\n"; > js = js + "var input = > inputs[i];\n"; > js = js + "if (input.value > == null || input.value == '' || input.type == 'button' || input.type == > 'submit') {\n"; > js = js + "continue;\n"; > js = js + "}\n"; > //js = js + "alert('Input [' > + i + '] (' + input.type + '): ' + input.name + ' = ' + input.value)\n"; > js = js + "formData[ > input.name] = input.value;\n"; > js = js + "stringData = > stringData + '[' + input.name + ']=' + input.value;\n"; > js = js + "}\n"; > js = js + "var selects = > document.getElementsByTagName(**'select');\n"; > js = js + "for (var j = 0; j > < selects.length; ++j) {\n"; > js = js + "var input = > selects[j];\n"; > js = js + "if (input.value > == null || input.value == '' || input.type == 'button' || input.type == > 'submit') {\n"; > js = js + "continue;\n"; > js = js + "}\n"; > //js = js + "alert('Input [' > + i + '] (' + input.type + '): ' + input.name + ' = ' + input.value)\n"; > js = js + "formData[ > input.name] = input.value;\n"; > js = js + "stringData = > stringData + '[' + input.name + ']=' + input.value;\n"; > js = js + "}\n"; > //js = js + > "alert.log(formData);\n"; > //js = js + > "alert(formData);\n"; > //js = js + "return > formData.toString();\n"; > js = js + "return > stringData;\n"; > js = js + "}\n"; > //js = js + "formData;\n"; > js = js + "return > getFormData();\n"; > > > Thanks! > Karel > > > On 06/29/11 02:59 PM, Eduard Moraru wrote: > >> Hi Karel, >> >> On Tue, Jun 28, 2011 at 9:46 PM, Karel Gardas<karel.gardas(a)centrum.cz** >> >wrote: >> >> >>> Hi Eduard, >>> >>> >>> On 06/28/11 05:45 PM, Eduard Moraru wrote: >>> >>> After googling around on this topic, it seems that there is no clean way >>>> of >>>> doing this. >>>> >>>> The initial community-accepted way I managed to find was using >>>> javascript >>>> (Browser.execute(String)) to retrieve your data, store it in >>>> window.status >>>> and then, a BrowserStatusText listener would get that value from the >>>> status >>>> text. An example is here: >>>> http://www.java2s.com/Code/****Java/SWT-JFace-Eclipse/**<http://www.java2s.com/Code/**Java/SWT-JFace-Eclipse/**> >>>> QueryDOMnodevalue.htm<http://**www.java2s.com/Code/Java/SWT-** >>>> JFace-Eclipse/**QueryDOMnodevalue.htm<http://www.java2s.com/Code/Java/SWT-JFace-Eclipse/QueryDOMnodevalue.htm> >>>> > >>>> >>>> >>>> On the other hand, by checking the Eclipse/SWT API, it seems that >>>> Browser.evaluate(String) also got implemented along the way and, >>>> compared >>>> to >>>> execute(String), it actually returns the value of the executed >>>> JavaScript >>>> so >>>> you can use it directly. Documentation here: >>>> http://help.eclipse.org/****indigo/index.jsp?topic=%2Forg.****<http://help.eclipse.org/**indigo/index.jsp?topic=%2Forg.**> >>>> eclipse.platform.doc.isv%****2Freference%2Fapi%2Forg%** >>>> 2Feclipse%2Fswt%2Fbrowser%****2FBrowser.html<http://help.** >>>> eclipse.org/indigo/index.jsp?**topic=%2Forg.eclipse.platform.** >>>> doc.isv%2Freference%2Fapi%**2Forg%2Feclipse%2Fswt%** >>>> 2Fbrowser%2FBrowser.html<http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.…> >>>> > >>>> >>>> >>>> So, to sum it up, use JS to document.getElementById(...) for each field >>>> in >>>> the form and use their names+values to build the request performed by >>>> your >>>> Finish button. >>>> >>>> >>> I'm afraid this is not possible. Imagine you do have completely unknown >>> template to you and you need your new page wizard to support it. You >>> don't >>> know at all what id you should use and how many of them to get all the >>> template forms values. For example let's have a template for book type >>> with >>> a fields: "Book name", "Author name" and "publication". Id's of those >>> fields >>> in my particular case are: Book store.BookClass_0_name, Book >>> store.BookClass_0_author, Book store.BookClass_0_publication how the >>> template wizard author should know this? So IMHO this way is not possible >>> or >>> at least not in this way... >>> >>> >>> >>> Well, from your template wizard and by using JavaScript, you could get >> all >> the<input...> elements with their name and value and pass them to the >> request performed by the 'Finish' button. I doubt that there will be more >> than one<form> element in the template page, but even so, the main<form> >> element's ID is 'inline'. >> >> Here's a starting point based on the above: >> >> var formData = {}; >> >> var inputs = document.getElementsByTagName(**'input'); >> for (var i = 0; i< inputs.length; ++i) { >> var input = inputs[i]; >> if (input.value == null || input.value == '' || input.type == 'button' >> || >> input.type == 'submit') { >> continue; >> } >> console.log('Input [' + i + '] (' + input.type + '): ' + input.name + ' >> = >> ' + input.value) >> formData[input.name] = input.value; >> } >> >> console.log(formData); >> >> Note: Replace 'console' with alert if you are not running this in >> Firebug's >> console. >> >> It does need some fine tuning, but it should work. >> >> >> P.S.: Can you post a screenshot of the wizard page containing the >>> >>>> template's >>>> form? >>>> >>>> >>> It's small, so I hope nobody will be angry for attaching this directly. >>> This is a second page of the wizard creating page for Book with name >>> "Matka" >>> (Mother in English), author's name is "Karel Capek" and publication date >>> is >>> set to "1929" -- but this is completely untrue, just my example, the >>> first >>> real publication was in 1938. BTW: Karel Capek is listed from the dynamic >>> list of authors, which is a result of SPARQ query on top of Jena's DB. >>> Code >>> which shall be also open-source once we get green from the customer legal >>> department... "FOUND BOOK NAME" and "FOUND AUTHOR NAME" together with >>> "<set >>> property operation aborted!>" are just debug messages from template .vm >>> code >>> where I'm using some of our semantics marcos (also to be open-sourced) -- >>> this all is about semantic XWiki book store demo example... I'm creating >>> pages for authors and books using author and book template. Once you add >>> author page all the semantics props are set so you get it listed >>> automatically inside the book template code in author name dynamic SPARQ >>> list... >>> >>> >> Thanks for the preview. It looks like you are using xpage=plain for plain >> HTML rendering. This should be enough for basic templates. I some >> templates >> contain javascript inside them (for input validation, autocomplete, etc) , >> I >> don`t think it will work since the JS is not included in xpage=plain. >> Don`t >> know if that`s a problem for your usecase. >> >> Good luck, >> Eduard >> >> >> Now I just need to make sure page template creation is really working >>> even >>> from XEclipse (this thread is all about)... >>> >>> Thanks! >>> Karel >>> >>> >>> >>> On Tue, Jun 28, 2011 at 2:56 PM, Karel Gardas<karel.gardas(a)centrum.cz** >>>> ** >>>> >>>>> wrote: >>>>> >>>> >>>> >>>> Hi Eduard, >>>>> >>>>> On 06/15/11 06:59 PM, Eduard Moraru wrote: >>>>> >>>>> Hi Karel, >>>>>> >>>>>> On 06/15/2011 01:54 PM, Karel Gardas wrote: >>>>>> >>>>>> Hello Sergiu, >>>>>>> >>>>>>> thanks a lot for you hint, when I renamed >>>>>>> xwiki-enterprise-web-3.1-****SNAPSHOT to simple xwiki, then after >>>>>>> clicking >>>>>>> on<save and view> button I got to normal login screen and when I >>>>>>> log >>>>>>> >>>>>>> in >>>>>> >>>>> >>>>> the page is really created. >>>>>> >>>>>>> >>>>>>> If you look at my first reply (with initial suggestions), you`ll see >>>>>>> >>>>>> that I suggested that the actual Save action when completing the >>>>>> creation of a page should be performed by your wizard`s Finish button >>>>>> (sending a HTTP request with all the parameters set), otherwise you >>>>>> mix >>>>>> up the user by having 2 sets of buttons (XWiki`s and the wizard`s). >>>>>> >>>>>> >>>>> I remember well your initial recommendation. Thanks for it! The way of >>>>> using SWT browser directly was just rather a proof-of-concept of the >>>>> idea of having browser embedded inside the wizard. Now, the situation >>>>> is >>>>> a little bit different. I do have: >>>>> >>>>> - small http client code which logs into xwiki server if needed and >>>>> access the newly created page >>>>> - strip all not needed information from the newly created page and >>>>> leave >>>>> just a form to fill the template data >>>>> - show such page in the browser embedded inside the wizard window and >>>>> allow user to fill the form. >>>>> >>>>> That's what working. Now I would like to press Finish button get the >>>>> filled form from SWT browser (somehow!) and POST it to the xwiki server >>>>> to save the page with entered data. The problem is that if I use >>>>> getText() method on SWT browser it does not return page with filled >>>>> data >>>>> and I don't see any other API which should support this. >>>>> >>>>> So my question now is : do you have any idea how to get filled form >>>>> page >>>>> from the browser back into my code? >>>>> >>>>> Thanks a lot! >>>>> Karel >>>>> >>>>> ______________________________****_________________ >>>>> devs mailing list >>>>> devs(a)xwiki.org >>>>> http://lists.xwiki.org/****mailman/listinfo/devs<http://lists.xwiki.org/**mailman/listinfo/devs> >>>>> <http://**lists.xwiki.org/mailman/**listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs> >>>>> > >>>>> >>>>> ______________________________****_________________ >>>>> >>>> devs mailing list >>>> devs(a)xwiki.org >>>> http://lists.xwiki.org/****mailman/listinfo/devs<http://lists.xwiki.org/**mailman/listinfo/devs> >>>> <http://**lists.xwiki.org/mailman/**listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs> >>>> > >>>> >>>> >>>> >>> >> >

13 years, 5 months

[xwiki-devs] Package name best practice

by Vincent Massol

Hi devs, I've updated the doc on http://dev.xwiki.org/xwiki/bin/view/Community/JavaCodeStyle#HPackagenames From: * All code that is **not** moved to the new XWiki Architecture based on components should use ##com.xpn.xwiki##. New architecture code should use ##org.xwiki##. To: * All code that is not located in the oldcore module should use ##org.xwiki##. Hope it's ok with you. Thanks -Vincent

13 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs