- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] [VOTE] Modification to groupid for contrib projects

by Vincent Massol

hi devs, I'd like to propose a small improvement for contrib project group ids. ATM our rule is: "A generic maven groupId : org.xwiki.contrib (until the project reaches a certain size and visibility, in which case it can have its own maven group id)" ( see http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome) I'd like to change that to: "A generic maven groupId : org.xwiki.contrib.<module name> (until the project reaches a certain size and visibility, in which case it can have its own maven group id)" So for example if I have a "Mail Archive Application" I'd use the groupid: org.xwiki.contrib.mailarchive Here's my +1 for the change Thanks -Vincent

13 years

5
7
0 0

Re: [xwiki-devs] [GSoc] XWiki Android

by sasinda rukshan

Hi Thomas, >>I restarted it and it seems ok now. Thanks a lot. Instrumentation tests that check the activities are running ok. (XWiki Android Instrumentation Tests<http://ci.xwiki.org/job/xwiki-android-client/216/org.xwiki.android$xwiki-an…> ) I disabled the base rest api tests (xwiki-android-test-rest). I'll enable them in the next commit. There should be a local xwiki test instance in jenkins server as well. Can you tell me how to access it. Tried http://ci.xwiki.org:8080. Since the test properties are directing to a local server instance 10.0.2.2:8080 it should be there. We will be running tests bottom up. i.e. low lvl rest API --> Rest API in RAL --> application layer UI components. And RAL tests will use low lvl rest API to achieve its pre-conditions and do cleanup after tests. If low level fails testing highlvl ones are not meaningful if they depend on the components that failed. ;-). Best Regards. Sasinda. > > > On Mon, Aug 6, 2012 at 1:00 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com > > wrote: > >> On Mon, Aug 6, 2012 at 9:12 AM, Thomas Mortagne >> <thomas.mortagne(a)xwiki.com> wrote: >> > On Mon, Aug 6, 2012 at 9:10 AM, Thomas Mortagne >> > <thomas.mortagne(a)xwiki.com> wrote: >> >> On Mon, Aug 6, 2012 at 8:57 AM, Thomas Mortagne >> >> <thomas.mortagne(a)xwiki.com> wrote: >> >>> On Sun, Aug 5, 2012 at 5:42 PM, sasinda rukshan >> >>> <sasindarukshan(a)gmail.com> wrote: >> >>>> Hi Thomas, >> >>>> :-) >> >>>> Also still we cannot ignore failed tests in maven android plugin. If >> a test >> >>>> fails we get Build Failure as result. >> >>> >> >>> Well that's the whole point, not sure why you want to ignore failing >> tests. >> >>> >> >>>> http://code.google.com/p/robotium/issues/detail?id=130 >> >>>> >> >>>>> Need an AVD / Device connected to Jenkins to >> >>>> run the tests. >> >>>> I think you just have to download android sdk to the jenkins server >> and use >> >>>> avd-manager to start up an avd in it. >> >>>> Not urgent ;-). >> >> >> >> Well thing is there is an AVD running and always have (since it was >> >> required by previous tests) so I don't understand exactly what's >> >> wrong. >> > >> > Here is what I have in ps aux: >> > >> > emulator -avd test-2.1 -noaudio -no-window -wipe-data >> >> Looks like it was not in a very good state actually, I restarted it >> and it seems ok now. >> >> > >> >> >> >>>> >> >>>> Still writing tests for core module. >> >>>> >> >>>> Regards. >> >>>> Sasinda Rukshan. >> >>>> >> >>>> On Sun, Aug 5, 2012 at 8:49 PM, Thomas Mortagne < >> thomas.mortagne(a)xwiki.com> >> >>>> wrote: >> >>>>> >> >>>>> On Sun, Aug 5, 2012 at 4:46 PM, sasinda rukshan >> >>>>> <sasindarukshan(a)gmail.com> wrote: >> >>>>> > Hi Thomas, >> >>>>> > Thnx. >> >>>>> > >> >>>>> >>No, you need to start one (which is not very hard with >> jetty/hsqldb >> >>>>> >>distribution) >> >>>>> > Well what about the earlier project's test server. It should have >> had >> >>>>> > its >> >>>>> > test environment setup properly. Shouldn't it?. >> >>>>> >> >>>>> Yes it should have but Chamika did not had time to finish. >> >>>>> >> >>>>> > >> >>>>> > >> >>>>> >>(but then you have the risk that you don't >> >>>>> >>have the exact same behavior) when you start the tests. You can >> look >> >>>>> >>at how >> >>>>> >> >> >>>>> >> >> https://github.com/xwiki/xwiki-enterprise/tree/master/xwiki-enterprise-test… >> >>>>> >>does it for example. >> >>>>> > Thanks. I'll make the setup, tear down methods to achieve >> preconditions >> >>>>> > and >> >>>>> > cleanup. >> >>>>> > >> >>>>> > Best Regards. >> >>>>> > >> >>>>> > On Sun, Aug 5, 2012 at 7:14 PM, Thomas Mortagne >> >>>>> > <thomas.mortagne(a)xwiki.com> >> >>>>> > wrote: >> >>>>> >> >> >>>>> >> On Sun, Aug 5, 2012 at 11:42 AM, sasinda rukshan >> >>>>> >> <sasindarukshan(a)gmail.com> wrote: >> >>>>> >> > Hi Thomas, >> >>>>> >> > >> >>>>> >> > >> >>>>> >> > This is the latest result for >> xwiki-android-tests-instrumentation >> >>>>> >> > (The >> >>>>> >> > UI stress testing test module) >> >>>>> >> > >> >>>>> >> > >> >>>>> >> > >> >>>>> >> > [INFO] *Found 0 devices connected with the Android Debug >> Bridge* >> >>>>> >> > mojoFailed >> >>>>> >> > >> >>>>> >> > >> com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.3.0(default-internal-pre-integration-test) >> >>>>> >> > projectFailed >> >>>>> >> > >> org.xwiki.android:xwiki-android-tests-instrumentation:1.0-SNAPSHOT >> >>>>> >> > sessionEnded >> >>>>> >> > >> >>>>> >> > >> >>>>> >> > Need an AVD / Device connected to Jenkins to run the tests. >> >>>>> >> >> >>>>> >> Will look at it. >> >>>>> >> >> >>>>> >> > >> >>>>> >> > Also the ....test-rest will have failures if some >> preconditions are >> >>>>> >> > not >> >>>>> >> > met. (like having a page named Blog/test2 ) >> >>>>> >> > >> >>>>> >> > Is there a testing server instance running on the Jenkins >> server?. >> >>>>> >> >> >>>>> >> No, you need to start one (which is not very hard with >> jetty/hsqldb >> >>>>> >> distribution) or mock one (but then you have the risk that you >> don't >> >>>>> >> have the exact same behavior) when you start the tests. You can >> look >> >>>>> >> at how >> >>>>> >> >> >>>>> >> >> https://github.com/xwiki/xwiki-enterprise/tree/master/xwiki-enterprise-test… >> >>>>> >> does it for example. >> >

13 years

2
11
0 0

[xwiki-devs] [vote] improvements for the REST api

by Ludovic Dubost

While working on a prototype on a HTML5 mobile and desktop application I've hit a few limitations of the REST APIs. This is why I propose some enhancements to the current REST APIs to give more flexibility, particularly: Support for start and order parameter in queries returning large list of pages Support order parameter in page list Adding page version, author information and data information when missing Hidden documents filter activation or deactivation in REST APIs Adding pretty display of title and author names Support queries using XWQL, HQL and Lucene The rendered content should be accessible from REST apis The details of the proposal is here: http://dev.xwiki.org/xwiki/bin/view/Design/RESTApiImprovements A pull request for a prototype implementation of these requirements is available here: https://github.com/xwiki/xwiki-platform/pull/56/files#r1040052 Not everything has an implementation (hidden docs and rendered content is not implemented yet). Other are not implementing according to this specification as some comments have already been made. Particularly the following votes are required: VOTE to accept supporting "start" and "order" parameters only on queries having only one unique scope VOTE in search queries for just adding the descendent date order or add more order possibilities using order and orderdir param VOTE in page list queries for just adding the descendent date order or add more order possibilities using order and orderdir param VOTE to add page version and author fields to page and other resources VOTE for adding the additional fields with or without a parameter "pagedetails=1" VOTE for adding a parameter to show/hide hidden documents independent of user setting VOTE to add the displayTitle field with or without the pagedetails=1 parameter or with it's own parameter displayTitle=1 VOTE to add the author display names with or without the displayPrettyNames parameter VOTE for supporting the searchQuery API at the wiki level with multi wiki support at the lucene level VOTE for adding rendered content using the withrenderedcontent=1 param VOTE for having absolute URLs in the rendered content using withabsoluteurls=1 param Thanks Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

13 years

3
7
0 0

[xwiki-devs] Lucene - external indexing

by Jones, Dan

Would it be possible to add an external directory for lucene to crawl and index? I want to be able to search wiki content, including the attachments, and also incorporate external search results as well. I was taking a look at Solr, and might try to go that route, despite being intimidated a bit. It looks extremely cool and well suited. Gracias! ________________________________ This communication (including all attachments) is intended solely for the use of the person(s) to whom it is addressed and should be treated as a confidential AAA communication. If you are not the intended recipient, any use, distribution, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately delete it from your system and notify the originator. Your cooperation is appreciated.

13 years

3
2
0 0

[xwiki-devs] [GSOC] SOLR status evaluation

by Vincent Massol

Hi Guys, I haven't been that closely the SOLR GSOC work and it would be great to see where we stand. I'd love to know the following: * What's the status of the code; is it following our best practices (code style/passing checkstyle, unit tests, functional tests)? * What's the level of the UI in term of readiness, compared to our current one? * Do we have all the features of the current Lucene plugin (including improvements already listed in JIRA, we should verify that they can be implemented with the current code if not already there) * Could we do drop-in replacement of the current search? In general, how much work remains to be able to commit this in platform and start bundling it and using it in XE? Thanks a lot -Vincent

13 years

2
5
0 0

Re: [xwiki-devs] [GSoC] [Request] Responsive Skin - data for extensive testing/bug finds/feature requests

by Jonathan Solichin

Hello friends, Beside yesterday's addition, these have also been addressed. I apologize if you checked yesterday and the addition was not on github/live instance, I uploaded the unchanged folder. - Lots of sections in Administration are missing the styles + some portion > of settings are displayed after the administration menu ends (Chrome) (you > need to scroll in order to see all the options, see Administration -> > Applications -> WYSIWYG Editor settings ) - .xform style for .xHint are gone (you can observe this when creating > pages/spaces) I just uploaded some stylings that makes this more eye pleasing and responsive. - The page -> Share by email feature is style-less. Styled this as well Thank you, Jonathan Solichin

13 years

3
9
0 0

[xwiki-devs] Developer Scripting Reference Documentation Prototype

by Ludovic Dubost

Hi Developers, With the help of Andrei (from the XWiki SAS support team), we have worked on a prototype to provide a reference documentation for XWiki scripting development. We have found that new XWiki developers have difficulties getting around everything that's available in XWiki and struggle a bit to find the appropriate documentation. Providing a reference documentation would go a long way to help the developers getting up to speed faster. This is the objective of this prototype. You'll find the design page here: http://dev.xwiki.org/xwiki/bin/view/Design/DeveloperReferenceDocumentation A first prototype is available here: http://incubator.myxwiki.org/xwiki/bin/view/ScriptingReferenceDocumentation… At this point it only provides documentation for the latest version (4.1.x), but it's already quite good as we have nothing really good currently. The first step would be to find a home on xwiki.org for this documentation. It could be: http://dev.xwiki.org/xwiki/bin/view/ScriptingReferenceDocumentation/ We also need a space to store all the builds of the full javadoc of the XWiki platform for each version (I don't think using ZipExplorer is a good idea given the size of the zip of the javadoc). I suggest making them available through Apache at: http://dev.xwiki.org/docs/${version} If that's ok I can proceed to publish the prototype on dev.xwiki.org and continue on the plan listed on the design wiki. Any comments and ideas are of course welcome. Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

13 years

8
17
0 0

[xwiki-devs] XEM xmlpc using a wiki farm

by Jones, Dan

How can you use the standard XWikiXMLRPCClient to add pages or spaces to a particular wiki, when you are running the XWiki Enterprise Manager application? I have installed everything, and I've made 2 new wikis. When I log in as localhost:8080/xwiki/xmlrpc/confluence, I can add a space or page, but I can't specify which wiki to use! The url localhost:8080/xwiki/wiki/NEW_WIKI/xmlrpc/confluence doesn't hit the xml rpc servlet filter. It initializes my context to the XWiki that is the main one, not a sub-wiki. String url = "http://localhost:8080/xwiki/xmlrpc/confluence"; XWikiXmlRpcClient rpc = new XWikiXmlRpcClient( url); rpc.login( user, pass); rpc.storePage(someNewPage); Thanks! Dan ________________________________ This communication (including all attachments) is intended solely for the use of the person(s) to whom it is addressed and should be treated as a confidential AAA communication. If you are not the intended recipient, any use, distribution, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately delete it from your system and notify the originator. Your cooperation is appreciated.

13 years

2
1
0 0

[xwiki-devs] [XWiki Devs] [GSOC] [Solr] : Advance Search and Admin module

by savitha sundaramurthy

Dear XWiki Community, I have implemented the Advanced Search Features and Admin Module for Solr Search Component. The features include: *Querying over:* 1. Plain strings ( can filtered based on space and language ) 2. Objects [ object:XWiki.XWikiUsers ] 3. Properties [ XWiki.XWikiUsers.first_name : Sa* ] 4. Attachments [ filename:gsoc.pdf ] 5. Facets [ Space, Creator, Author, Creation Date, Modification Date, Language ...] 6. Advanced search using document fields like title, name, comments, space, language etc.. 7. Multilingual Support *Admin Gui:* 1. Index based on the wiki and the available spaces. 2. All the statistics - Indexing stats - Solr details, versions - Solr configuration files and their sizes. - Component details. 3. Indexing page. - Details of indexing process in progress. For more detailed information for Advanced search refer to the link below: http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Solr+Feature+Page The detailed information about the admin module, Progress of the project, API and the recent code is given in the progress page: http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SOLRsearchcomponent Running instance of the amazon ec2 server: http://ec2-50-19-181-163.compute-1.amazonaws.com:8080/xwiki/bin/admin/XWiki… http://ec2-50-19-181-163.compute-1.amazonaws.com:8080/xwiki/bin/view/Search… -- Thanks, Savitha

13 years, 1 month

3
3
0 0

[xwiki-devs] Spreadsheet JS component

by Vincent Massol

Hi, Might be interesting to integrate: https://github.com/mleibman/SlickGrid/wiki -Vincent

13 years, 1 month

3
4
0 0

[xwiki-devs] Issue with copy of XWikiPreferences and custom mapped classes

by Denis Gervalle

Hi devs, Following upon an issue with migration encountered by Jeremie Bousquet, I felt on an unexpected issue that I do not really know how to fix. When you made a copy of a document containing a custom mapped class, a new custom mapped class is created by the exact copy of the original document class definition, but the custom mapping for this copied class is probably incorrect or not available. For exemple, if you made a copy of XWiki.XWikiPreferences, you get a new class that has an internal mapping, but since the .xbm is unchanged, there is probably no chance that the newly defined class has a mapped entity in the hibernate mapping. This is precisely the cause of the issue I have encounter with Jeremie, since the migration tried to migrate IDs of that new class, which was unusable. Initially, I had an NPE that I have transformed into an exception now, since I see this as a corruption somewhere in the store. The issue with a dynamically custom mapped class could even be worse, since both class will have the same mapping. So my question is more generally about how we handle copy of custom mapped classes ? now and in the future ? -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

13 years, 1 month

2
3
0 0

[xwiki-devs] [PROPOSAL] Add XWikiAttachmentContent#setContent() which returns an OutputStream to write content to.

by Caleb James DeLisle

Hi, In the development of Cassandra attachments, I found I want to load an attachment one chunk at a time and write that chunk to a provided OutputStream, this is how I envision next generation Hibernate attachments working too. I would like to add to XWikiAttachmentContent: public OutputStream addContent(); which returns an OutputStream that allows writing the attachment content and upon close, sets the attachment content as dirty and resets the size field. WDYT? Caleb

13 years, 1 month

6
12
0 0

[xwiki-devs] xwiki activity stream is very very slow, and the user profile.

by Kirby Zhou

xwiki activity stream is very very slow My 4.1.3 instance performance is not acceptable. It takes me more than 10 seconds to display the activity stream. Is there a simple workaround to remove 'activity stream' from user profile view? I have already remove 'activity stream' from WebHome. ✉ Kirby Zhou

13 years, 1 month

2
1
0 0

[xwiki-devs] [VOTE] More accuracy about QA in Release Notes

by Sorin Burjan

Hello devs, I want to cast a vote regarding the following proposal: Remove the section about manual testing and the link to the MTR's from M1, M2 and RC1 Release Notes, since we test against MTR only after we release RC1. This means that we will have a MTR only for final releases, which will be linked from the RN page of the final version. After releasing each M1, M2 and RC1, only the newly added features are tested. The rationale behind this is that ATM we point a link to a MTR (for every minor release) but the MTR will be empty ("Not Tested"), so this renders it useless for minor releases. Waiting for your votes/opinions Regards, Sorin B.

13 years, 1 month

7
11
0 0

[xwiki-devs] [VOTE] Add 4.2 Milestone 3

by Marius Dumitru Florea

Hi devs, One of the main goals of 4.2 release was to be able to upgrade an XWiki farm in a few minutes. Thomas has started working on this and I need to improve the UI which is currently very minimal. We are pretty late overall and one way to still have this in 4.2 is to postpone the final release by adding a third milestone. The current planning is: * 4.2M2: 6 Aug 2012 (Today!) * 4.2RC1: 20 Aug 2012 * 4.2Final: 27 Aug 2012 With a third milestone we could have this: * 4.2M2: 6 Aug 2012 (Today!) * 4.2M3: 27 Aug 2012 * 4.2RC1: 10 Sep 2012 * 4.2Final: 17 Sep 2012 However, doing this means we're going to miss the unofficial "1 cycle per year rule" (we were already over 1 year at the current rate but it's going to be worse with this) which means we would need from now on to have shorter release cycle for the 4.x cycle: * 4.3: October (2 months) * 4.4: December (1 month) * 4.5: January (1 month) In any case the 4.4 and 4.5 release are supposed to be cycle stabilization releases so it's not a bad thing. We just need to agree we're not going to put any more big stuff in the 4.x cycle. One thing we would still need to put in is a new skin which must go in 4.3 (would be too late afterwards). I'm +1. Thanks, Marius P.S.: This is actually Vincent's proposal, but I'm sending the vote myself because he's on holiday.

13 years, 1 month

5
4
0 0

Re: [xwiki-devs] [GSoC] [Request] Responsive Skin - data for extensive testing/bug finds/feature requests

by Jonathan Solichin

I think that's a great idea, it would make the skin more extensible. Right now I am exploring creating a xar to create a page where there can be options-- right now for the colors, like you did with the "fluid" option on lyrebird. As I am separating the codes, i am wondering how far i should separate the core? Should i just leave enough css that there is a sidebar, the header, and the main content area? Thank you, Jonathan Solichin On Mon, Jul 30, 2012 at 1:09 PM, Jonathan Solichin <j.s.solichin(a)gmail.com>wrote: > I think that's a great idea, it would make the skin more extensible. Right > now I am exploring creating a xar to create a page where there can be > options-- right now for the colors, like you did with the "fluid" option on > lyrebird. > > As I am separating the codes, i am wondering how far i should separate the > core? Should i just leave enough css that there is a sidebar, the header, > and the main content area? > > Thank you, > Jonathan Solichin > > > On Thu, Jul 26, 2012 at 1:42 AM, Jonathan Solichin <jssolichin(a)gmail.com>wrote: > >> Hi Jerome, >> >> All the advise you mentioned should now be fixed on github. Ajax search >> is now implemented. >> >> I will be working on color themes, while still trying to ensure >> consistency through out XE UI. >> >> Thank you again! >> Jonathan Solichin >> >> >> On Tue, Jul 17, 2012 at 11:50 AM, Jonathan Solichin <jssolichin(a)gmail.com >> > wrote: >> >>> Hello Friends, >>> >>> As you may or may not know, I have been working on a responsive skin for >>> XWiki for GSOC (http://23.21.87.183:8080/xwiki/bin/view/Main/WebHome). >>> As I continue to add further details and refinements into the skin, I would >>> like to kindly ask for your help in doing so. In order to make sure that I >>> did not miss anything and the skin is as complete as possible, I would like >>> to, if possible, request a XAR of an existing wiki (or complex pages) so >>> that I may see the result of implementing the skin on more than the default >>> wiki data. >>> >>> If this is not a possible, I would like to still enlist your help in >>> testing some basic/your favorite functionality/features of xwiki. There are >>> several ways to do this: >>> >>> - By downloading the current skin and testing it on your XWiki: >>> https://github.com/jssolichin/xo5 >>> - By playing around with the live instance (uses default admin >>> user/password): http://23.21.87.183:8080/xwiki/bin/view/Main/WebHome >>> - By letting me know of your favorite applications (so that I may >>> look into implementing them) >>> >>> Anything you want to note is fine. Bug and feature request are both >>> welcome, as I think communal ideas are often better than one. Even if you >>> did not have a chance to play too much with the skin, go ahead and let me >>> know what you think I should check on (based on your experience) and/or >>> give me any suggestions that may have come up while reading this. >>> Technicality permitting, I will check myself. >>> >>> Helping with this process will help make the skin better, and maybe help >>> it to be tailored to your (/type of) wiki and the community surrounding the >>> platform in general. >>> >>> Thank you in advance for your time! >>> Jonathan Solichin >>> >> >> >

13 years, 1 month

3
5
0 0

[xwiki-devs] New REST APIs for managing wikis

by Fabio Mancinelli

Hi everybody, I've just sent a pull request for an extension I did to the REST API for managing wikis. In particular this extension implements http://jira.xwiki.org/browse/XWIKI-7076 and http://jira.xwiki.org/browse/XWIKI-8120. The pull request is here: https://github.com/xwiki/xwiki-platform/pull/68 Code review + comments are welcome. Thanks, Fabio

13 years, 1 month

2
1
0 0

[xwiki-devs] [ANN] XWiki Enterprise and XWiki Enterprise Manager 4.2 Milestone 2 released

by Marius Dumitru Florea

The XWiki development team is proud to announce the availability of XWiki Enterprise 4.2 Milestone 2. This release adds support for storing an email address and a list of wiki page names in XWiki objects using dedicated xclass property types. It also adds the ability to have an object property whose value is computed from the other properties. For developers this release introduces default custom displayers for easier customization of the way XWiki object properties are displayed. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris… Thanks -The XWiki dev team

13 years, 1 month

1
0
0 0

[xwiki-devs] 4.2 Milestone 2 release planned for today

by Marius Dumitru Florea

Hi devs, I'd like to start the release this afternoon (EET). The CI looks in good shape. I'll check the two failing tests in xwiki-enterprise-test-extension. Please let me know if you have any pending commits for 4.2M2 or any blocking issues that needs to be fixed before the release. Thanks, Marius

13 years, 1 month

2
2
0 0

Re: [xwiki-devs] [GSoc] XWiki Android

by sasinda rukshan

Hi Thomas, This is the latest result for xwiki-android-tests-instrumentation (The UI stress testing test module) [INFO] *Found 0 devices connected with the Android Debug Bridge* mojoFailed com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.3.0(default-internal-pre-integration-test) projectFailed org.xwiki.android:xwiki-android-tests-instrumentation:1.0-SNAPSHOT sessionEnded Need an AVD / Device connected to Jenkins to run the tests. Also the ....test-rest will have failures if some preconditions are not met. (like having a page named Blog/test2 ) Is there a testing server instance running on the Jenkins server?. Best Regards Sasinda. PS: I created a login with username sasindar. On Thu, Jul 12, 2012 at 6:08 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com>wrote: > BTW don't put too much details in mail in general, better making sure > that references places like > https://github.com/xwiki-contrib/android-client/blob/master/README and > http://extensions.xwiki.org/xwiki/bin/view/Extension/Google+Android+Client > are up to date and link to them. Unless the mail is about asking some > details of course, I mostly talking about announcement mails. > > On Thu, Jul 12, 2012 at 2:35 PM, Thomas Mortagne > <thomas.mortagne(a)xwiki.com> wrote: > > On Thu, Jul 12, 2012 at 1:10 PM, sasinda rukshan > > <sasindarukshan(a)gmail.com> wrote: > >> Hi > >> :-) > >> Do you mean to put a mail to Xwiki Users list users(a)xwiki.org., Not > >> Developers list ? > > > > I mean users and dev list. The idea is to talk about your project to > > the community (what already exist, what coming, etc). Note that dev > > mailing list is not for developers, it's for developers of XWiki > > itself, developers that are going to use XWiki and in this case > > android framework are users from mailing list point or view. > > > >> Well did you check the apk ? is it enough to show off. > > > > As long as it's working and there anything new to advertise it's > > enough. The important things here is to show that there is something > > produced which is easy to test and that people can try it whenever > > they want to check last stuff. > > > >> > >> Regards > >> Sasinda. > >> > >> > >> > >> > >> On Thu, Jul 12, 2012 at 3:55 PM, Thomas Mortagne < > thomas.mortagne(a)xwiki.com> > >> wrote: > >>> > >>> It's an announcement mail, not a documentation. It's made to show off > ;) > >>> > >>> On Thu, Jul 12, 2012 at 12:23 PM, Thomas Mortagne > >>> <thomas.mortagne(a)xwiki.com> wrote: > >>> > On Thu, Jul 12, 2012 at 12:15 PM, sasinda rukshan > >>> > <sasindarukshan(a)gmail.com> wrote: > >>> >> Hi, > >>> >> You mean to a real phone? > >>> >> I was thinking about an emulator. :-) > >>> > > >>> > Not was talking about real quick test for end user. > >>> > > >>> >>>>I don't understand, you don't need command line to install any APK > on > >>> >>>>a phone. You just need to enable it. > >>> >> Well I mean for the developers to test what the API offers. Not the > >>> >> application users to check what is available. > >>> >> The demo blog app was not meant for real users. I only spent about > 7-8 > >>> >> hours > >>> >> developing the UI of it. > >>> > > >>> > It's not a big deal, it's just about showing that you have something > >>> > working and that it's easy to try it. > >>> > > >>> > You should also obviously talk about what's not visible yet and > >>> > provide links for developers. But no need to explain developer how to > >>> > put an APK in an emulator, just indicate what new and where it is. > >>> > > >>> >> > >>> >> Regards > >>> >> Sasinda. > >>> >> > >>> >> > >>> >> On Thu, Jul 12, 2012 at 3:07 PM, Thomas Mortagne > >>> >> <thomas.mortagne(a)xwiki.com> > >>> >> wrote: > >>> >>> > >>> >>> On Thu, Jul 12, 2012 at 11:35 AM, Thomas Mortagne > >>> >>> <thomas.mortagne(a)xwiki.com> wrote: > >>> >>> > On Thu, Jul 12, 2012 at 11:32 AM, sasinda rukshan > >>> >>> > <sasindarukshan(a)gmail.com> wrote: > >>> >>> >> Hi, > >>> >>> >> Thanks. > >>> >>> >>>>Evaluation (you passed by the way unless Google has soemthing > to > >>> >>> >>>> say > >>> >>> >>>>about it but I think they let us decide) > >>> >>> >> Thanks a lot! I am happy to here that. > >>> >>> >> > >>> >>> >> By the way I did not care about making the visual aspects. Since > >>> >>> >> you > >>> >>> >> said > >>> >>> >> that the API is the most important one. > >>> >>> >> So it looks only little work. > >>> >>> >> I mean, no one will see that I have automated the work of > sending > >>> >>> >> the > >>> >>> >> representation of the Xwiki Document to the server > >>> >>> >> with just one method call (i.e. create()). I am very happy to > have > >>> >>> >> made > >>> >>> >> such an abstraction because I were originally planning to show > the > >>> >>> >> Blog > >>> >>> >> demo > >>> >>> >> using earlier project's fine grained API directly. The > abstraction > >>> >>> >> was > >>> >>> >> made > >>> >>> >> such that XE can keep on changing the ReST API without affecting > >>> >>> >> the > >>> >>> >> upper > >>> >>> >> application layers. > >>> >>> >> But I am afraid nobody(not you :-)) will notice that because all > >>> >>> >> that > >>> >>> >> is > >>> >>> >> internal technical functionality. > >>> >>> >> > >>> >>> >> > >>> >>> >>>> But try to do > >>> >>> >>>>a not too technical mail and gives phone/tablet oriented > >>> >>> >>>> instructions > >>> >>> >>>>to install the APK > >>> >>> >> I'll send a mail to the community without tech stuff. ( I mean > the > >>> >>> >> ORM > >>> >>> >> frameworks , restful abstractions etc) > >>> >>> >> But they will have to install it using cmd line any way. > >>> >>> >> adb install <apk> . No GUI ;-) > >>> >>> >> Navigation is intuitive. > >>> >>> > > >>> >>> > I don't understand, you don't need command line to install any > APK > >>> >>> > on > >>> >>> > a phone. You just need to enable it. > >>> >>> > >>> >>> Talking about enable installing APK comming from "unkown sources" > in > >>> >>> Applications preferences. > >>> >>> > >>> >>> > > >>> >>> >> > >>> >>> >> > >>> >>> >> I will only mention the internals in the design docs. > >>> >>> >> > >>> >>> >> > >>> >>> >> Thanks. > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> On Thu, Jul 12, 2012 at 2:00 PM, Thomas Mortagne > >>> >>> >> <thomas.mortagne(a)xwiki.com> > >>> >>> >> wrote: > >>> >>> >>> > >>> >>> >>> I'm the one that is assigned to this project as the most > available > >>> >>> >>> to > >>> >>> >>> help you and follow you work but your are actually working with > >>> >>> >>> XWiki > >>> >>> >>> community, not just me ;) > >>> >>> >>> > >>> >>> >>> On Thu, Jul 12, 2012 at 10:28 AM, Thomas Mortagne > >>> >>> >>> <thomas.mortagne(a)xwiki.com> wrote: > >>> >>> >>> > On Thu, Jul 12, 2012 at 10:02 AM, sasinda rukshan > >>> >>> >>> > <sasindarukshan(a)gmail.com> wrote: > >>> >>> >>> >> Hi, > >>> >>> >>> >> PS: > >>> >>> >>> >>>> * Post, Publish a blog post > >>> >>> >>> >>>> ( > >>> >>> >>> >>>> These two features use the internal functionality as > >>> >>> >>> >>>> follows. > >>> >>> >>> >>>> Posting a Document in the server using the new ReSTful > >>> >>> >>> >>>> Access > >>> >>> >>> >>>> Layer > >>> >>> >>> >>>> simplified API. > >>> >>> >>> >>>> Actually an API user would only have to call a > create(doc) > >>> >>> >>> >>>> method > >>> >>> >>> >>>> passing the Xwik Document he made. All the logic of > >>> >>> >>> >>>> transforming > >>> >>> >>> >> ... > >>> >>> >>> >> All the logic of transforming is done behind the scenes. The > >>> >>> >>> >> developer > >>> >>> >>> >> need > >>> >>> >>> >> not know much about the underlying restful api. That is > >>> >>> >>> >> he does not need to know he has to post objects to a page, > then > >>> >>> >>> >> post > >>> >>> >>> >> tags > >>> >>> >>> >> comments and etc. > >>> >>> >>> >> All the ReST calls are done under the ReSTful Access layer. > It > >>> >>> >>> >> is > >>> >>> >>> >> just > >>> >>> >>> >> like > >>> >>> >>> >> the hibernate layer above the Xwiki Enterprise Database > ;-). > >>> >>> >>> >> > >>> >>> >>> >> Also For the API user's ease, we have integrated ORMLite a > ORM > >>> >>> >>> >> library. So > >>> >>> >>> >> Hibernate, JPA users will feel familiar here. > >>> >>> >>> >> > >>> >>> >>> >> Those are the important points in a summary. > >>> >>> >>> >> Further details will be provided when I update the > >>> >>> >>> >> documentations. > >>> >>> >>> > > >>> >>> >>> > Again do not send all that only to me. > >>> >>> >>> > > >>> >>> >>> > Evaluation (you passed by the way unless Google has > soemthing to > >>> >>> >>> > say > >>> >>> >>> > about it but I think they let us decide) is good period to > start > >>> >>> >>> > announcing what you have done so far and how to test it. But > try > >>> >>> >>> > to > >>> >>> >>> > do > >>> >>> >>> > a not too technical mail and gives phone/tablet oriented > >>> >>> >>> > instructions > >>> >>> >>> > to install the APK people should try since most people are > not > >>> >>> >>> > going > >>> >>> >>> > to test it with the debugger ;) > >>> >>> >>> > > >>> >>> >>> >> > >>> >>> >>> >> Please feel free to suggest. > >>> >>> >>> >> > >>> >>> >>> >> Thanks. > >>> >>> >>> >> Best Regards. > >>> >>> >>> >> Sasinda. > >>> >>> >>> >> > >>> >>> >>> >> > >>> >>> >>> >> > >>> >>> >>> >> On Thu, Jul 12, 2012 at 1:21 PM, sasinda rukshan > >>> >>> >>> >> <sasindarukshan(a)gmail.com> > >>> >>> >>> >> wrote: > >>> >>> >>> >>> > >>> >>> >>> >>> Hi Thomas , all, > >>> >>> >>> >>> > >>> >>> >>> >>> Oops.Very Sorry. I was doing it on my office machine. I > >>> >>> >>> >>> commented > >>> >>> >>> >>> out > >>> >>> >>> >>> the > >>> >>> >>> >>> parent reference. Big mistake with removing comments. > >>> >>> >>> >>> The build did work in the local machine. The earlier > build's > >>> >>> >>> >>> problem > >>> >>> >>> >>> was > >>> >>> >>> >>> that it did not export the dependencies. Now with the older > >>> >>> >>> >>> jayway > >>> >>> >>> >>> plugin > >>> >>> >>> >>> the export of dependencies to the apk is done ok. > >>> >>> >>> >>> Thanks for pointing out. > >>> >>> >>> >>> > >>> >>> >>> >>> >>Note that it still not fully building. > >>> >>> >>> >>> > >>> >>> >>> >>> [INFO] XWiki Android - Parent POM ........................ > >>> >>> >>> >>> SUCCESS > >>> >>> >>> >>> [5.786s] > >>> >>> >>> >>> [INFO] XWiki REST Model .................................. > >>> >>> >>> >>> SUCCESS > >>> >>> >>> >>> [1.991s] > >>> >>> >>> >>> [INFO] XWiki REST Simple-Xml Model ....................... > >>> >>> >>> >>> SUCCESS > >>> >>> >>> >>> [4.136s] > >>> >>> >>> >>> [INFO] XWiki REST GSON Model ............................. > >>> >>> >>> >>> SUCCESS > >>> >>> >>> >>> [3.222s] > >>> >>> >>> >>> [INFO] XWiki Android REST Connector ...................... > >>> >>> >>> >>> SUCCESS > >>> >>> >>> >>> [4.277s] > >>> >>> >>> >>> [INFO] XWiki android core lib ............................ > >>> >>> >>> >>> SUCCESS > >>> >>> >>> >>> [6.672s] > >>> >>> >>> >>> [INFO] Xwiki Android Components .......................... > >>> >>> >>> >>> SUCCESS > >>> >>> >>> >>> [4.882s] > >>> >>> >>> >>> [INFO] XWiki Client Apps ................................. > >>> >>> >>> >>> SUCCESS > >>> >>> >>> >>> [12.440s] > >>> >>> >>> >>> [INFO] XWiki Android REST Tests .......................... > >>> >>> >>> >>> FAILURE > >>> >>> >>> >>> [8.884s] > >>> >>> >>> >>> [INFO] XWiki Android Instrumentation Tests ............... > >>> >>> >>> >>> SKIPPED > >>> >>> >>> >>> > >>> >>> >>> >>> The two test modules are not building. Well I did not check > >>> >>> >>> >>> there > >>> >>> >>> >>> build, > >>> >>> >>> >>> as I did not change the lower layer APIs which they > depended > >>> >>> >>> >>> on. > >>> >>> >>> >>> Well, the > >>> >>> >>> >>> Junit version tag is missing in their poms. > >>> >>> >>> > > >>> >>> >>> > There were building well before you change the plugin version > >>> >>> >>> > (and > >>> >>> >>> > many things that has nothing to do with the plugin version > >>> >>> >>> > despite > >>> >>> >>> > what you indicated in the commit log) so it would be nice > that > >>> >>> >>> > you > >>> >>> >>> > fix > >>> >>> >>> > this. Having them working should be first priority. Generally > >>> >>> >>> > specking > >>> >>> >>> > the whole build should always work on master especially > >>> >>> >>> > automated > >>> >>> >>> > tests which are checking for you automatically if you > introduce > >>> >>> >>> > any > >>> >>> >>> > regression. > >>> >>> >>> > > >>> >>> >>> >>> > >>> >>> >>> >>> I did not add my own tests yet. > >>> >>> >>> >>> > >>> >>> >>> >>> But you can check out the apk at > >>> >>> >>> >>> > >>> >>> >>> >>> > >>> >>> >>> >>> > >>> >>> >>> >>> > >>> >>> >>> >>> > http://maven.xwiki.org/snapshots/org/xwiki/android/xwiki-android-client/1.0… > >>> >>> >>> >>> It is working. > >>> >>> >>> >>> Steps to install. > >>> >>> >>> >>> 1) Download android SDK > >>> >>> >>> >>> > >>> >>> >>> >>> > http://developer.android.com/sdk/installing/adding-packages.html > >>> >>> >>> >>> 2) Start SDK Manager.exe in the extracted folder and > download > >>> >>> >>> >>> Android > >>> >>> >>> >>> 2.1 > >>> >>> >>> >>> API 7 or later. (I test on API 7). > >>> >>> >>> >>> 3) Start AVD Manager.exe and make a Android Virtual Device > >>> >>> >>> >>> named > >>> >>> >>> >>> exactly > >>> >>> >>> >>> "android-7". > >>> >>> >>> >>> 4) Make sure you have added the path to > >>> >>> >>> >>> <android-sdk-installation > >>> >>> >>> >>> path>/platform-tools and <android-sdk-installation > path>/tools > >>> >>> >>> >>> as > >>> >>> >>> >>> described > >>> >>> >>> >>> in the above guide at (Tip in the bottom) > >>> >>> >>> >>> > >>> >>> >>> >>> > http://developer.android.com/sdk/installing/adding-packages.html > >>> >>> >>> >>> > >>> >>> >>> >>> 5) download > xwiki-android-client-1.0-20120711.121416-177.apk > >>> >>> >>> >>> or a > >>> >>> >>> >>> later > >>> >>> >>> >>> apk in > >>> >>> >>> >>> > >>> >>> >>> >>> > >>> >>> >>> >>> > >>> >>> >>> >>> > http://maven.xwiki.org/snapshots/org/xwiki/android/xwiki-android-client/1.0… > >>> >>> >>> >>> 6) run command>> adb install <your apk> ex: for the > build on > >>> >>> >>> >>> July 11 > >>> >>> >>> >>> adb install > xwiki-android-client-1.0-20120711.121416-177.apk > >>> >>> >>> >>> > >>> >>> >>> >>> After install is successful please press the XWiki icon in > >>> >>> >>> >>> the > >>> >>> >>> >>> android > >>> >>> >>> >>> virtual device's launcher. > >>> >>> >>> >>> Features: > >>> >>> >>> >>> * Password , username, server url remember feature added. > >>> >>> >>> >>> * Connection timeouts added > >>> >>> >>> >>> * Generalized Launch pad added for android client apps. ( > >>> >>> >>> >>> Client > >>> >>> >>> >>> app > >>> >>> >>> >>> icons > >>> >>> >>> >>> are shown in the launch pad). > >>> >>> >>> >>> * Post, Publish a blog post > >>> >>> >>> >>> ( > >>> >>> >>> >>> These two features use the internal functionality as > >>> >>> >>> >>> follows. > >>> >>> >>> >>> Posting a Document in the server using the new ReSTful > >>> >>> >>> >>> Access > >>> >>> >>> >>> Layer > >>> >>> >>> >>> simplified API. > >>> >>> >>> >>> Actually an API user would only have to call a > create(doc) > >>> >>> >>> >>> method > >>> >>> >>> >>> passing the Xwik Document he made. All the logic of > >>> >>> >>> >>> transforming > >>> >>> >>> >>> > >>> >>> >>> >>> > >>> >>> >>> >>> Conversion of XWiki Domain model to relevant rest model > >>> >>> >>> >>> objects. > >>> >>> >>> >>> ) > >>> >>> >>> >>> > >>> >>> >>> >>> * Save, Load blog posts ( Persisting the XWiki Domain > model) > >>> >>> >>> >>> > >>> >>> >>> >>> The UI here is just demo purpose only. > >>> >>> >>> >>> > >>> >>> >>> >>> > >>> >>> >>> >>> > >>> >>> >>> >>> > >>> >>> >>> >>> On Wed, Jul 11, 2012 at 9:39 PM, Thomas Mortagne > >>> >>> >>> >>> <thomas.mortagne(a)xwiki.com> wrote: > >>> >>> >>> >>>> > >>> >>> >>> >>>> On Wed, Jul 11, 2012 at 2:13 PM, Thomas Mortagne > >>> >>> >>> >>>> <thomas.mortagne(a)xwiki.com> wrote: > >>> >>> >>> >>>> > I fixed many mistakes in the root pom.xml, there is no > way > >>> >>> >>> >>>> > you > >>> >>> >>> >>>> > could > >>> >>> >>> >>>> > build anything with that so I don't understand exactly > what > >>> >>> >>> >>>> > you > >>> >>> >>> >>>> > tested... > >>> >>> >>> >>>> > >>> >>> >>> >>>> Note that it still not fully building. > >>> >>> >>> >>>> > >>> >>> >>> >>>> > > >>> >>> >>> >>>> > On Tue, Jul 10, 2012 at 9:13 AM, Thomas Mortagne > >>> >>> >>> >>>> > <thomas.mortagne(a)xwiki.com> wrote: > >>> >>> >>> >>>> >> The build is still failing on > >>> >>> >>> >>>> >> http://ci.xwiki.org/job/xwiki-android-client/, you > should > >>> >>> >>> >>>> >> always > >>> >>> >>> >>>> >> make > >>> >>> >>> >>>> >> sure this is working well. > >>> >>> >>> >>>> >> > >>> >>> >>> >>>> >> On Mon, Jul 9, 2012 at 2:07 PM, sasinda rukshan > >>> >>> >>> >>>> >> <sasindarukshan(a)gmail.com> wrote: > >>> >>> >>> >>>> >>> Hi Thomas, > >>> >>> >>> >>>> >>> The issue with the build was solved by reverting back > to > >>> >>> >>> >>>> >>> older > >>> >>> >>> >>>> >>> version of > >>> >>> >>> >>>> >>> jayway android maven plugin. This seems not the > correct > >>> >>> >>> >>>> >>> option, > >>> >>> >>> >>>> >>> but > >>> >>> >>> >>>> >>> it > >>> >>> >>> >>>> >>> works now. :-). > >>> >>> >>> >>>> >>> > >>> >>> >>> >>>> >>> Thanks > >>> >>> >>> >>>> >>> Regards. > >>> >>> >>> >>>> >>> Sasinda. > >>> >>> >>> >>>> >>> > >>> >>> >>> >>>> >>> On Mon, Jul 9, 2012 at 12:51 PM, sasinda rukshan > >>> >>> >>> >>>> >>> <sasindarukshan(a)gmail.com>wrote: > >>> >>> >>> >>>> >>> > >>> >>> >>> >>>> >>>> Hi Thomas, > >>> >>> >>> >>>> >>>> >As you want, was just a suggestion to make it > easier. > >>> >>> >>> >>>> >>>> > Not > >>> >>> >>> >>>> >>>> > sure > >>> >>> >>> >>>> >>>> > how > >>> >>> >>> >>>> >>>> >XWord deal with macros. > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> Well actually I did not use code macro there. Just > copy > >>> >>> >>> >>>> >>>> pasted > >>> >>> >>> >>>> >>>> from > >>> >>> >>> >>>> >>>> eclipse ;-). Less work it was!. > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> >From what I can see this is not a real issue. > >>> >>> >>> >>>> >>>> Yes, its not a real issue. > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> > I need > >>> >>> >>> >>>> >>>> > to finish something before 4.2M1, will try to look > at > >>> >>> >>> >>>> >>>> > it > >>> >>> >>> >>>> >>>> > after > >>> >>> >>> >>>> >>>> > that. > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> No problem. Don't be distracted with this. I am > trying a > >>> >>> >>> >>>> >>>> workaround, > >>> >>> >>> >>>> >>>> to > >>> >>> >>> >>>> >>>> copy the needed jars with maven-dependancy plugin.(I > >>> >>> >>> >>>> >>>> upgraded > >>> >>> >>> >>>> >>>> maven > >>> >>> >>> >>>> >>>> to > >>> >>> >>> >>>> >>>> 3.0.4. also) . I will try more and hopefully get this > >>> >>> >>> >>>> >>>> thing > >>> >>> >>> >>>> >>>> done. It > >>> >>> >>> >>>> >>>> is not > >>> >>> >>> >>>> >>>> halting my development because I can build with > eclipse. > >>> >>> >>> >>>> >>>> Thanks for offering me help. :-). > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> Best Regards. > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> On Mon, Jul 9, 2012 at 12:37 PM, Thomas Mortagne < > >>> >>> >>> >>>> >>>> thomas.mortagne(a)xwiki.com> wrote: > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>>> On Mon, Jul 9, 2012 at 6:35 AM, sasinda rukshan > >>> >>> >>> >>>> >>>>> <sasindarukshan(a)gmail.com> wrote: > >>> >>> >>> >>>> >>>>> > Hi, > >>> >>> >>> >>>> >>>>> > Thanks for the info. > >>> >>> >>> >>>> >>>>> > I did it using XWord . I will do some more > >>> >>> >>> >>>> >>>>> > documentation > >>> >>> >>> >>>> >>>>> > after > >>> >>> >>> >>>> >>>>> > reaching > >>> >>> >>> >>>> >>>>> the > >>> >>> >>> >>>> >>>>> > milestone 3( security module). That documentation > is > >>> >>> >>> >>>> >>>>> > not > >>> >>> >>> >>>> >>>>> > enough > >>> >>> >>> >>>> >>>>> > to give > >>> >>> >>> >>>> >>>>> the > >>> >>> >>> >>>> >>>>> > whole picture. Need to separate the API how to s, > >>> >>> >>> >>>> >>>>> > from > >>> >>> >>> >>>> >>>>> > the > >>> >>> >>> >>>> >>>>> > design > >>> >>> >>> >>>> >>>>> > and architecture descriptions.So the documentation > >>> >>> >>> >>>> >>>>> > will > >>> >>> >>> >>>> >>>>> > get > >>> >>> >>> >>>> >>>>> > changed in > >>> >>> >>> >>>> >>>>> the > >>> >>> >>> >>>> >>>>> > future. Is it ok if I edit the formatting later at > >>> >>> >>> >>>> >>>>> > that > >>> >>> >>> >>>> >>>>> > time?. > >>> >>> >>> >>>> >>>>> > >>> >>> >>> >>>> >>>>> As you want, was just a suggestion to make it > easier. > >>> >>> >>> >>>> >>>>> Not > >>> >>> >>> >>>> >>>>> sure > >>> >>> >>> >>>> >>>>> how > >>> >>> >>> >>>> >>>>> XWord deal with macros. > >>> >>> >>> >>>> >>>>> > >>> >>> >>> >>>> >>>>> > > >>> >>> >>> >>>> >>>>> > By the way the maven build of the android project > is > >>> >>> >>> >>>> >>>>> > currently > >>> >>> >>> >>>> >>>>> > having > >>> >>> >>> >>>> >>>>> the > >>> >>> >>> >>>> >>>>> > following issue. > >>> >>> >>> >>>> >>>>> > > >>> >>> >>> >>>> >>>>> > > >>> >>> >>> >>>> >>>>> > > >>> >>> >>> >>>> >>>>> > > >>> >>> >>> >>>> >>>>> > > http://code.google.com/p/maven-android-plugin/issues/detail?id=266 > >>> >>> >>> >>>> >>>>> > >>> >>> >>> >>>> >>>>> From what I can see this is not a real issue. Also > note > >>> >>> >>> >>>> >>>>> that > >>> >>> >>> >>>> >>>>> it's > >>> >>> >>> >>>> >>>>> working well with the other application > >>> >>> >>> >>>> >>>>> (xwiki-android-client). > >>> >>> >>> >>>> >>>>> I > >>> >>> >>> >>>> >>>>> need > >>> >>> >>> >>>> >>>>> to finish something before 4.2M1, will try to look > at > >>> >>> >>> >>>> >>>>> it > >>> >>> >>> >>>> >>>>> after > >>> >>> >>> >>>> >>>>> that. > >>> >>> >>> >>>> >>>>> > >>> >>> >>> >>>> >>>>> > I am trying to resolve it, but still not > successful. > >>> >>> >>> >>>> >>>>> > The > >>> >>> >>> >>>> >>>>> > build > >>> >>> >>> >>>> >>>>> > works in > >>> >>> >>> >>>> >>>>> > eclipse. > >>> >>> >>> >>>> >>>>> > Currently I have implemented the functionality for > >>> >>> >>> >>>> >>>>> > saving > >>> >>> >>> >>>> >>>>> > and > >>> >>> >>> >>>> >>>>> > loading > >>> >>> >>> >>>> >>>>> back > >>> >>> >>> >>>> >>>>> > xwiki document model. It is working fine. > >>> >>> >>> >>>> >>>>> > (We can save, load , list documents stored in the > >>> >>> >>> >>>> >>>>> > system). I > >>> >>> >>> >>>> >>>>> > have > >>> >>> >>> >>>> >>>>> stopped > >>> >>> >>> >>>> >>>>> > development until the maven build issue is solved. > >>> >>> >>> >>>> >>>>> > > >>> >>> >>> >>>> >>>>> > Thanks. > >>> >>> >>> >>>> >>>>> > Regards. > >>> >>> >>> >>>> >>>>> > > >>> >>> >>> >>>> >>>>> > > >>> >>> >>> >>>> >>>>> > > >>> >>> >>> >>>> >>>>> > On Sun, Jul 8, 2012 at 11:11 PM, Thomas Mortagne > >>> >>> >>> >>>> >>>>> > <thomas.mortagne(a)xwiki.com>wrote: > >>> >>> >>> >>>> >>>>> > > >>> >>> >>> >>>> >>>>> >> On Sun, Jul 8, 2012 at 2:53 PM, sasinda rukshan > >>> >>> >>> >>>> >>>>> >> <sasindarukshan(a)gmail.com> wrote: > >>> >>> >>> >>>> >>>>> >> > Hi, > >>> >>> >>> >>>> >>>>> >> > I updated the documentation for XWiki Android > >>> >>> >>> >>>> >>>>> >> > project > >>> >>> >>> >>>> >>>>> >> > at, > >>> >>> >>> >>>> >>>>> >> > > >>> >>> >>> >>>> >>>>> >> > > >>> >>> >>> >>>> >>>>> >> > > http://dev.xwiki.org/xwiki/bin/view/Design/XWikiAndroid. > >>> >>> >>> >>>> >>>>> >> > > >>> >>> >>> >>>> >>>>> >> > Sorry for the little formatting errors. > >>> >>> >>> >>>> >>>>> >> > >>> >>> >>> >>>> >>>>> >> You should use code macro instead of setting your > >>> >>> >>> >>>> >>>>> >> own > >>> >>> >>> >>>> >>>>> >> styling. > >>> >>> >>> >>>> >>>>> >> > >>> >>> >>> >>>> >>>>> >> > > >>> >>> >>> >>>> >>>>> >> > Thanks > >>> >>> >>> >>>> >>>>> >> > Sasinda. > >>> >>> >>> >>>> >>>>> >> > _______________________________________________ > >>> >>> >>> >>>> >>>>> >> > devs mailing list > >>> >>> >>> >>>> >>>>> >> > devs(a)xwiki.org > >>> >>> >>> >>>> >>>>> >> > http://lists.xwiki.org/mailman/listinfo/devs > >>> >>> >>> >>>> >>>>> >> > >>> >>> >>> >>>> >>>>> >> > >>> >>> >>> >>>> >>>>> >> > >>> >>> >>> >>>> >>>>> >> -- > >>> >>> >>> >>>> >>>>> >> Thomas Mortagne > >>> >>> >>> >>>> >>>>> >> > >>> >>> >>> >>>> >>>>> > _______________________________________________ > >>> >>> >>> >>>> >>>>> > devs mailing list > >>> >>> >>> >>>> >>>>> > devs(a)xwiki.org > >>> >>> >>> >>>> >>>>> > http://lists.xwiki.org/mailman/listinfo/devs > >>> >>> >>> >>>> >>>>> > >>> >>> >>> >>>> >>>>> > >>> >>> >>> >>>> >>>>> > >>> >>> >>> >>>> >>>>> -- > >>> >>> >>> >>>> >>>>> Thomas Mortagne > >>> >>> >>> >>>> >>>>> _______________________________________________ > >>> >>> >>> >>>> >>>>> devs mailing list > >>> >>> >>> >>>> >>>>> devs(a)xwiki.org > >>> >>> >>> >>>> >>>>> http://lists.xwiki.org/mailman/listinfo/devs > >>> >>> >>> >>>> >>>>> > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>>> > >>> >>> >>> >>>> >>> _______________________________________________ > >>> >>> >>> >>>> >>> devs mailing list > >>> >>> >>> >>>> >>> devs(a)xwiki.org > >>> >>> >>> >>>> >>> http://lists.xwiki.org/mailman/listinfo/devs > >>> >>> >>> >>>> >> > >>> >>> >>> >>>> >> > >>> >>> >>> >>>> >> > >>> >>> >>> >>>> >> -- > >>> >>> >>> >>>> >> Thomas Mortagne > >>> >>> >>> >>>> > > >>> >>> >>> >>>> > > >>> >>> >>> >>>> > > >>> >>> >>> >>>> > -- > >>> >>> >>> >>>> > Thomas Mortagne > >>> >>> >>> >>>> > >>> >>> >>> >>>> > >>> >>> >>> >>>> > >>> >>> >>> >>>> -- > >>> >>> >>> >>>> Thomas Mortagne > >>> >>> >>> >>> > >>> >>> >>> >>> > >>> >>> >>> >> > >>> >>> >>> > > >>> >>> >>> > > >>> >>> >>> > > >>> >>> >>> > -- > >>> >>> >>> > Thomas Mortagne > >>> >>> >>> > >>> >>> >>> > >>> >>> >>> > >>> >>> >>> -- > >>> >>> >>> Thomas Mortagne > >>> >>> >> > >>> >>> >> > >>> >>> > > >>> >>> > > >>> >>> > > >>> >>> > -- > >>> >>> > Thomas Mortagne > >>> >>> > >>> >>> > >>> >>> > >>> >>> -- > >>> >>> Thomas Mortagne > >>> >> > >>> >> > >>> > > >>> > > >>> > > >>> > -- > >>> > Thomas Mortagne > >>> > >>> > >>> > >>> -- > >>> Thomas Mortagne > >> > >> > > > > > > > > -- > > Thomas Mortagne > > > > -- > Thomas Mortagne >

13 years, 1 month

2
1
0 0

[xwiki-devs] When a document has translations, they are listed as if it was duplicate

by Marczisovszky Daniel

Hi, When a document has translations, it appears in the document list as many times as many translations exists. This bug was added about 2 years ago and we believe it is really an annoying one. http://jira.xwiki.org/browse/XWIKI-6228 I'd like to ask if there is any plan for fixing it, and hopefully we can discuss different solutions for this. Here are the original suggestion and ours: 1. Document list should show the translated title, every document appears as many times as many translations exists. 2. (we think this is better ;) ) Every document should appear in the list only once according to the current language, with the following rules: 2.a. if there is no translation in the current languages, the document should not appear 2.b. if translations exists, but the title is not translated, then the title of the original document should appear. Thanks, Daniel

13 years, 1 month

2
1
0 0

[xwiki-devs] Social Login Extension Problem

by Caroline

Hi, i installed the "Social Login Extension" and followed the steps to implement it to my wiki. First i wanted to try the facebook login. Therefore, i created a facebook app and put the app keys in the oauth_consumer.properties file. My wiki runs on my localhost. So i put "http://localhost:8080" in the configuration of my facebook app. When i click on the social login button at the xwiki login it redirects me to facebook, where i have to confirm that i want to do this. But when i am redirected to xwiki i get the following error message: org.xwiki.rendering.macro.MacroExecutionException: Failed to evaluate Script Macro for content [import org.brickred.socialauth.AuthProvider import org.brickred.socialauth.AuthProviderFactory /** * Displays a form with a single field for a new SSO user to pickup its usernamem */ def outputUsernameCreationForm = { defaultValue, provider -> if (!defaultValue) defaultValue = "" xwiki.ssx.use('XWiki.SocialLogin') println """ {{html clean=false}} <form class="xform" action=${doc.getURL('view')} method="post" id="createUsernameForm"> <div class="centered"> <fieldset class="xwikimessage"> <legend>${msg.get('xwiki.socialLogin.youMustBeNewHere')}</legend> <input type="hidden" name="xaction" value="createProfile" /> <p class="message"> ${msg.get('xwiki.socialLogin.createProfileMessage', [provider])} </p> <dl> <dt>${msg.get('xwiki.socialLogin.pickupUsername')}</dt> <dd><input type="text" name="username" value="${defaultValue}" /></dd> </dl> <div class="buttons"> <input class="button" type="submit" value="${msg.get('xwiki.socialLogin.createMyAccount')}" /> </div> </fieldset> </div> </form> {{/html}} """ } /** * Authenticate a user and make it remembered in XWiki authentication system */ def authenticateUser = { userDoc -> def password = userDoc.getObject('XWiki.SocialLoginClass').getProperty('password_cache').value def xwikiAuthenticator = xwiki.@xwiki.getAuthService().@authenticators.get('xwiki') def psm = xwikiAuthenticator.@persistentLoginManager psm.rememberLogin(request, response, userDoc.fullName, password) response.sendRedirect(xwiki.getURL('Main.WebHome', 'view')) } // Load oauth properties file def properties = new java.util.Properties() properties.load(com.xpn.xwiki.web.Utils.getComponent("org.xwiki.container.Container").applicationContext.getResourceAsStream("/WEB-INF/oauth_consumer.properties")) /** * Initiate the OAuth dance with the requested provider */ if(!request.callback && request.provider) { try { def provider = AuthProviderFactory.getInstance(request.provider, properties) println provider String url = provider.getLoginRedirectURL(doc.getExternalURL('view','callback=1')); // Store in session request.session.setAttribute("org.brickred.socialauth.AuthProvider", provider); request.session.setAttribute("org.brickred.socialauth.AuthProvider.hint", request.provider); response.sendRedirect(url) } catch(Exception e) { println """ {{error}} ${msg.get('xwiki.socialLogin.genericError', [e.message])} {{/error}} """ } } /** * We've got a response from the provider, let's treat it */ else if (request.callback){ try { // get the provider back from session def provider = request.session.getAttribute("org.brickred.socialauth.AuthProvider"); def providerID = request.session.getAttribute("org.brickred.socialauth.AuthProvider.hint"); // verify the authentication def profile = provider.verifyResponse(request); // Search for this user in database def query = services.query.xwql("from doc.object(XWiki.XWikiUsers) as user, doc.object(XWiki.SocialLoginProfileClass) as profile where profile.provider = '" + providerID + "' and profile.validatedId = '" + profile.validatedId + "'") for (result in query.execute()) { authenticateUser(xwiki.getDocument(result)) } // Not authenticated/redirected yet ? -> You must be new here // You will have to pick-up a username and dad will create an account for you // Store the social profile in the session request.session.setAttribute("org.brickred.socialauth.Profile", profile); // Try to guess what username the user will want to use def guessedUsername = profile.displayName // Outputs the form to create the username outputUsernameCreationForm(guessedUsername, providerID) } catch(Exception e) { println """ {{error}} ${msg.get('xwiki.socialLogin.genericError', [e.message])} {{/error}} """ } } /** * Create a new user profile from the social profile result */ else if (request.xaction && request.xaction == 'createProfile') { def profile = request.session.getAttribute("org.brickred.socialauth.Profile") def provider = request.session.getAttribute("org.brickred.socialauth.AuthProvider.hint"); def username = request.username if (username && username != '' && !xwiki.exists("XWiki." + username)) { // Everything clear, let's proceed def userDocName = "XWiki." + username // Generate a random password password = xwiki.generateRandomString(16) def propMap = [:] propMap.put("active", "1") propMap.put("email", profile.email) propMap.put("first_name", profile.firstName) propMap.put("last_name", profile.lastName) propMap.put("password", password) xwiki.(a)xwiki.createUser(username, propMap, xcontext.@context) def userDoc = xwiki.getDocument(userDocName) def socialProfile = userDoc.getObject('XWiki.SocialLoginProfileClass', true) socialProfile.set('provider', provider) socialProfile.set('fullName', profile.fullName) socialProfile.set('firstName', profile.firstName) socialProfile.set('lastName', profile.lastName) socialProfile.set('displayName', profile.displayName) socialProfile.set('email', profile.email) socialProfile.set('profileImageURL', profile.profileImageURL) socialProfile.set('gender', profile.gender) socialProfile.set('dob', profile.dob) socialProfile.set('validatedId', profile.validatedId) socialProfile.set('country', profile.country) socialProfile.set('location', profile.location) def socialPrefs = userDoc.getObject('XWiki.SocialLoginClass', true) socialPrefs.set('password_cache', password) socialPrefs.set('preferred_provider', provider) userDoc.saveWithProgrammingRights(msg.get('xwiki.socialLogin.updatedSocialProfile'), true) authenticateUser(userDoc) } else { if (!username || username == '') println """ {{error}} ${msg.get('xwiki.socialLogin.youMustPickUsername')} {{/error}} """ else if (xwiki.exists('XWiki.' + username)) println """ {{error}} ${msg.get('xwiki.socialLogin.usernameAlreadyTaken')} {{/error}} """ outputUsernameCreationForm("", provider); } } /** * View mode */ else { println """ {{info}} ${msg.get('xwiki.socialLogin.nothingToDo')} {{/info}} """ }] at org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.evaluateBlock(AbstractJSR223ScriptMacro.java:178) at org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.evaluateBlock(AbstractJSR223ScriptMacro.java:53) at org.xwiki.rendering.macro.script.AbstractScriptMacro.execute(AbstractScriptMacro.java:198) at org.xwiki.rendering.macro.script.AbstractScriptMacro.execute(AbstractScriptMacro.java:59) at org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transformOnce(MacroTransformation.java:190) at org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transform(MacroTransformation.java:135) at org.xwiki.rendering.internal.transformation.DefaultTransformationManager.performTransformations(DefaultTransformationManager.java:83) at org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:248) at org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:124) at org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:54) at org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:80) at org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:38) at org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:111) at org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:50) at org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:67) at org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:41) at com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:901) at com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:880) at com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:911) at com.xpn.xwiki.api.Document.getRenderedContent(Document.java:582) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:395) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:384) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:173) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:224) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:184) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:105) at com.xpn.xwiki.XWiki.evaluateTemplate(XWiki.java:1799) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1739) at com.xpn.xwiki.api.XWiki.parseTemplate(XWiki.java:854) at sun.reflect.GeneratedMethodAccessor133.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:395) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:384) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:173) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:369) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:216) at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:311) at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:230) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:207) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:224) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:184) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:105) at com.xpn.xwiki.XWiki.evaluateTemplate(XWiki.java:1799) at com.xpn.xwiki.web.Utils.parseTemplate(Utils.java:155) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:241) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:621) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:120) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:144) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:66) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:208) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:111) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:185) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:151) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:269) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: javax.script.ScriptException: javax.script.ScriptException: groovy.lang.MissingPropertyException: No such property: msg for class: Script2 at org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.eval(GroovyScriptEngineImpl.java:122) at org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.eval(AbstractJSR223ScriptMacro.java:280) at org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.evaluateBlock(AbstractJSR223ScriptMacro.java:213) at org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.evaluateBlock(AbstractJSR223ScriptMacro.java:173) ... 103 more Caused by: javax.script.ScriptException: groovy.lang.MissingPropertyException: No such property: msg for class: Script2 at org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.eval(GroovyScriptEngineImpl.java:323) at org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.eval(GroovyScriptEngineImpl.java:116) ... 106 more Caused by: groovy.lang.MissingPropertyException: No such property: msg for class: Script2 at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231) at Script2.run(Script2.groovy:117) at org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.eval(GroovyScriptEngineImpl.java:320) ... 107 more Do u have any idea, what i can do? I tried so much, but nothing worked. Thank you a lot Caroline -- View this message in context: http://xwiki.475771.n2.nabble.com/Social-Login-Extension-Problem-tp7580669.… Sent from the XWiki- Dev mailing list archive at Nabble.com.

13 years, 1 month

2
3
0 0

[xwiki-devs] export to pdf: the content is not carried on the next page

by Elena Roman

Hi, I am developing a script on groovy which compiles a table of content "manually" and then includes the children documents before exporting to PDF. So finally compiled document content looks like " =={{{ }}}[[1. Software Requirements Specification>>#H1.SoftwareRequirementsSpecification-1]]== ==={{{ }}}[[1.1. Use cases>>#H1.1.Usecases-1]]=== ===={{{ }}}[[1.1.1. Bite registration and occlusal clearance UC ...... ...... == 1. Software Requirements Specification== {{include document="Polaris.SoftwareRequirementsSpecification" context="new"/}} === 1.1. Use cases=== {{include document="Polaris.Use cases" context="new"/}} ...... " But when I export the document to PDf my compiled TOC(which is rather large) is not carried on the next page, it is just cut in the middle. The Export to RTF passes ok with carrying the TOC on the next page. Could somebody help to understand where is the problem? Thanks, elena

13 years, 1 month

2
3
0 0

[xwiki-devs] Slight Improvements to ExtensionCode.ExtensionVersionSheet

by Ludovic Dubost

I've improved a bit ExtensionCode.ExtensionVersionSheet to create the additional version in one click and allow then to edit it from the normal UI. I'm not sure where to propose a patch for the Extension Repository UI ? Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

13 years, 1 month

2
5
0 0

[xwiki-devs] Exclude a piece of content from pdf result document

by Elena Roman

Hi, I need to compile all pages (from parent to children) to one pdf document. Pages may contain a piece of data not to be included to the final document. This piece of data can be bound with [Exclude] ... [/Exclude] tags, or smth like this. Currently I see the only way to do it with parsing the each page 'String' content before including it to the output document and get rid of these pieces. But currently I experience some issues with this approach and it seems not clean. Is there another way around? Or maybe some doc links. <sorry if the question is too dumb, I have just started with the xwiki> thanks

13 years, 1 month

2
2
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs