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

Re: [xwiki-devs] Problem With Oracle Database 10gR1

by Ludovic Dubost

I see, You are building 1.2 and the oracle hbm files are probably not up to=20 date for the 1.2 store changes. You might want to try with 1.1 or help fix this. You can compare the=20 mysql hbm with the oracle hbm to see the missing tables. From the log file: com.xpn.xwiki.store.migration.XWikiDBVersion is not=20 declared in the oracle hbm Ludovic Colin Tay a écrit : > Hi, > > I am sure that i have change the hibernate config to use ORavle > specific hbm files. The details of the log are attached below: > > ERROR store.XWikiHibernateBaseStore - Failed updating schema: 2 > ERROR store.XWikiHibernateBaseStore - While executing query: update > xwikidoc set xwd_translation=0 where xwd_translation is null > ERROR store.XWikiHibernateBaseStore - Failed updating schema: > ORA-00942: table or view does not exist > WARN hql.QuerySplitter - no persistent classes found > for query class: delete from com.xpn.xwiki.store.migration.XWikiDBVersion > WARN query.HQLQueryPlan - manipulation query [delete > from com.xpn.xwiki.store.migration.XWikiDBVersion] resulted in [0] > split queries > WARN action.RequestProcessor - Unhandled Exception thrown: > class com.xpn.xwiki.XWikiException > ERROR store.XWikiHibernateBaseStore - Failed updating schema: 2 > ERROR store.XWikiHibernateBaseStore - While executing query: update > xwikidoc set xwd_translation=0 where xwd_translation is null > ERROR store.XWikiHibernateBaseStore - Failed updating schema: > ORA-00942: table or view does not exist > WARN hql.QuerySplitter - no persistent classes found > for query class: delete from com.xpn.xwiki.store.migration.XWikiDBVersion > WARN query.HQLQueryPlan - manipulation query [delete > from com.xpn.xwiki.store.migration.XWikiDBVersion] resulted in [0] > split queries > WARN action.RequestProcessor - Unhandled Exception thrown: > class com.xpn.xwiki.XWikiException > ERROR store.XWikiHibernateBaseStore - Failed updating schema: 2 > > and the list goes on..... > > I have also look into XWikiHibernateBaseStore file. In the > getSchemaUpdateScript(Configuration config, XWikiContext context) > method, the if(isOracle) { > dschema = config.getProperty(Environment.DEFAULT_SCHEMA); > > always return a null value. Why issit so? > > Need your help! > > */Ludovic Dubost <ludovic(a)xwiki.org>/* wrote: > > > Hi, > > Normally the schema should be created before calling this query. > Don't > you have more logs ? > Did you change the hibernate config to use the Oracle specific hbm > files ? > > Ludovic > > > Hi, > > > > I have successfully build Xwiki-1.2-SNAPSHOT and try to use it > > on oracle database. I have also followed the instructions on > > > http://www.xwiki.org/xwiki/bin/view/AdminGuide/InstallationOracle > closely. > > But error message were display instead as follow in the xwiki.log > > > > ERROR store.XWikiHibernateBaseStore - Failed updating schema: 2 > > ERROR store.XWikiHibernateBaseStore - While executing query: update > > xwikidoc set xwd_translation=0 where xwd_translation is null > > ................................ > > > > To clarify, i understand that i need to create the database schema > > manually but do i need to insert anything in the tables? Or else > there > > were be nothing show to the users? > > > > Need your guidances! > > > > > ------------------------------------------------------------------------ > > > > *Real people. Real questions. Real answers. Share what you know > > *. > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > -- > Ludovic Dubost > Blog: http://www.ludovic.org/blog/ > XWiki: http://www.xwiki.com > Skype: ldubost GTalk: ldubost > AIM: nvludo Yahoo: ludovic > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > > > ------------------------------------------------------------------------ > Yahoo! Movies > <http://sg.rd.yahoo.com/mail/sg/footer/def/*http://sg.movies.yahoo.com> > - Search movie info and celeb profiles and photos. -- Ludovic Dubost Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost AIM: nvludo Yahoo: ludovic

18 years

1
0
0 0

[xwiki-devs] [ANN] XWiki Enterprise 1.1 Released

by Vincent Massol

The XWiki development team team is pleased to announce the availability of the 1.1 release of XWiki Enterprise. Go grab it on http://www.xwiki.org/xwiki/bin/view/Main/Download This release implements 298 issues since XWiki Enterprise 1.0 was released less than 5 months ago. Major changes: * Improve default Wiki: better usability and better navigation o Search improvements and result filtering o Index page and Treeview page o WYSIWYG improvements and bug fixes * Full screen edition * RTF exports * Ability to enter comments on page modifications * Visual difference improvements when comparing versions * XMLRPC improvements * XWiki Platform is GWT-ready * Lucene experimental search And many more… See the release notes for all details at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise11 Enjoy -The XWiki development team

18 years

1
0
0 0

[xwiki-devs] New date for XEclipse 10.M2?

by Vincent Massol

Hi Asiri/Tharindu, I'd like to set a new target date for the XEclipse 1.0M2 release so that we have an objective. Could you please tell me what date would be reasonable, taking into account your studies and such? Thanks -Vincent

18 years

1
0
0 0

[xwiki-devs] [VOTE] Promote 1.1RC2 as 1.1 final

by Vincent Massol

Hi, I'd like to promote 1.1RC2 as 1.1 final. There's a 1.1.1 on the way if we require important bugs fixes. But I haven't seen important bugs yet on 1.1RC2. Here's my +1 Thanks -Vincent

18 years

5
6
0 0

[xwiki-devs] [Proposal] Remove copyright line in source file headers

by Vincent Massol

Hi, Maintaining copyright statements in source file headers is a pain. The ASF has solved this recently by removing copyright information from headers. Their header is now: /* * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional information * regarding copyright ownership. The ASF licenses this file * to you under the Apache License, Version 2.0 (the * "License"); you may not use this file except in compliance * with the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, * software distributed under the License is distributed on an * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY * KIND, either express or implied. See the License for the * specific language governing permissions and limitations * under the License. */ The important line is "See the NOTICE file distributed with this work for additional information regarding copyright ownership". I propose that we do the same and have this new boilerplate: /* * See the NOTICE file distributed with this work for additional information * regarding copyright ownership. * * This is free software; you can redistribute it and/or modify it * under the terms of the GNU Lesser General Public License as * published by the Free Software Foundation; either version 2.1 of * the License, or (at your option) any later version. * * This software is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Lesser General Public License for more details. * * You should have received a copy of the GNU Lesser General Public * License along with this software; if not, write to the Free * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA * 02110-1301 USA, or see the FSF site: http://www.fsf.org. */ And in the NOTICE file we would have: " This product includes software developed by XpertNet SARL and individual contributors under the following copyright: Copyright 2004-2007, XpertNet SARL, and individual contributors. " WDYT? I'm not a lawyer so I have no idea if this is valid or not but it looks sensible to me. -Vincent

18 years

4
3
0 0

[xwiki-devs] error using calendar application

by Daniel Bertinshaw

Hi, I have re-written the Xwiki.CalendarSheet code to add the calendar event object to $xwiki.getDocument("XWiki.CalendarSheet") rather than $doc (reason being, I want to include it in other contexts/pages). It works fine, until another user adds an event, then the events in the calendar display disappear, and re-appear if I edit the page and make no changes: oddly, the changes disappear for everyone and re-appear globally too. If I use my own account and add an even, there's no issue (im an admin, my test account is a normal user: I have tried fiddling with the rights). Any help? (code attached)

18 years

2
1
0 0

[xwiki-devs] [Proposal] Improve installer to include database setup

by Vincent Massol

Hi, I'm proposing to improve the generic install to add database configuration setup: 1) include different database driver jars in the installer 2) have some installation panels to let the user choose the database to use (using some combo box and fields to modify default DB values) 3) include the XAR in the installer 4) use the packager tool to import the XAR in the database at install time (using the information provided in 2)) Note: I'd also like to modify the web/standard build so that we release only a single WAR without database driver and without DB configuration. Advanced users will configure it manually and novice will use the installer. WDYT? Thanks -Vincent

18 years

5
10
0 0

[xwiki-devs] Lucene search enhancements

by David Ward

I've entered two bugs (XWIKI-1734 and XWIKI-1735) which relate to extending the Lucene Plugin search API. I would like to try getting them into the 1.1.1 version. The first is to allow Lucene to return the results in reverse order (one of the results columns we want to sort by is reverse alphabetical). The second is to index the creation and modification dates of the wiki pages (to allow "recently changed" type of searches limited by other criteria). The first is more important, but the second looks easy. David dward(a)curriki.org --

18 years

3
2
0 0

[xwiki-devs] [Proposal] New GWT-based WYSIWYG editor

by Vincent Massol

Hi, I'd like us all to welcome Marius Dumitru Florea who has joined the XWiki dev community to work on a new GWT-based WYSIWYG editor. Marius is very new to the XWiki team so I'd like all of us to support him for this very important work. This is really just the start of this project so we need everyone's help in designing it and for providing feedbacks and ideas. I've started a page on it there: http://www.xwiki.org/xwiki/bin/view/Idea/NewWysiwygEditorBasedOnGwt I'll we working with Marius on this for the time being and Jean- Vincent will probably help us in the future too. And anyone willing to help is most welcome. As I've mentioned on that page we have 3 main issues with the current WYSIWYG editor so it's time to start fixing them. The current Tiny- MCE based editor as the following deficiencies: * Slow * Complex code using complex regexs. This leads to a fragility that makes it break somewhere whenever someone adds a modification to it. * Lots of bug reports consistently for the past year, showing a non- optimal design I'll kick-start the discussion with some open questions I've listed on that page: * Is there a GWT editor component we can/should reuse? * Check WikiModel capabilities for conversions in both directions and especially from HTML to wiki syntax. * How to integrate WikiModel in the Rendering layer of XWiki? * Is there any code to be salvaged from the work done by Christian and Nam in that branch: svn+ssh://svn.forge.objectweb.org/svnroot/ xwiki/xwiki-platform/core/branches/XWIKI_WYSIWYG_NEWARCHI If anyone has any insight on these questions, please speak up! :) Thanks everyone, -Vincent

18 years

3
2
0 0

[xwiki-devs] XEM review

by Vincent Massol

Hi Thomas and everyone, I've started reviewing the XEM code in SVN in preparation for the 1.0M1 release for the 17th and I have the following questions/remarks (before putting them in JIRA): 1) Search.WebHome: This looks empty. Should it be removed or will there be something before 1.0M1 is released? 2) The XE XAR overwrites the XEM XAR in the build. I think it should be the other way around. 3) The XEM home page should be different than the XE one. It should mention things specific to XEM. 4) The Quick Links panel should be specific to XEM. 5) I think several XE pages should be removed from the default XEM. For example Photo Album is not something I'd think belongs to the XEM Administrator page by default. It would be belong to a subwiki for sure but not to the Admin one or at least not by default. This raises the question: what is the XEM administrator wiki for? Only for administrating subwikis or is it meant for other things too? 6) UserDirectory.WebHome is empty too 7) Utils space. Is that the right name for this space? From its content it look like some Admin space. 8) UserDirectory space. Wouldn't it be shorter and nicer to name this space: "Users" , and to name "Wikis" the space listing wikis instead of "WikiDirectory"? 9) The WikiDirectory.WebHome page shows the following which doesn't look very nice (especially the "listwikiempty" text): Wikis totalnumberofwiki : 0 createwiki Search listwikiempty 10) XEMAdmin.WebHome is empty 11) In XEMCode there's a XEMSkin document. Is it ready? If not we shouldn't keep pages that are not going to be released in 1.0M1 12) XWiki.SearchResults is not used/ + some other comments. Generally speaking it seems to me the default XEM wiki is not ready yet to be released. Also it would be nice if XEM had a different visual identity than XE. Do we have a skin in progress for it? Will it be ready for 1.0M1? I'm pretty sure I must be missing something (maybe there's a patch that hasn't been applied about XEM's XAR pages?)... :) These are just a few questions to get us started towards the 1.0M1 release of XEM. Thanks -Vincent

18 years

2
2
0 0

[xwiki-devs] Problems with the Blog

by totoe

Hi! I have a big problem with my blog-function in my Wiki. I've delete all example posts over the wiki function and the blank categories over my SQL. My problem now is, that I cannot make new posts in the standard categories. If I click on "Create Blog Post", I can set the posttitle Name. That is normal... But then I click on "Create": I get the error message "This is not an article". What should I do? I really need the blog. I hope you can help me... Thanks for your help! Torben

18 years

2
5
0 0

[xwiki-devs] [Proposal] Stable vs Unstable Platform Core for Products: point releases in branches

by Vincent Massol

Hi, Now that we're starting to have several products (XE, XEM, Watch, Curriki, etc) we need to agree on a strategy for their dependencies on the Platform Core. Need ===== Here's a real use case on which we can base our discussion: * XEM needs to be released ASAP. More specifically there's a need to release 1.0M1 on 17th of Sept. and 1.0M2 on 1st of October. * Platform Core 1.2 in trunk is not stable yet and will only be released at end of November (if we agree on the schedule I sent this morning) * XEM needs to use a stable Core * XEM needs some features in core that are not in Core 1.1 (For example: the new Right Management UI which needs to change templates and possibly some code too) To summarize, Products may require a stable version of the core but with modifications. How do we solve this? Solutions ======== Short term solution: * We put whatever is required in point releases. For example, for XEM, we put the Rights Management changes in 1.1.x * We decide on the 1.1.x release dates based on the aggregated needs of the different Products * Once the Core trunk is released then the Products are modified to depend on it. * Of course each Product should try its maximum to internalize required changes inside its own code rather while waiting for the Core the released. To do this, JIRA issues with patches should be submitted to the Core to be applied. The other short term solution is to have a specific branch of Core for each product but I feel this is going to be a nightmare to maintain and merge so I'd much rather have a single 1.1.x branch which we can release as fast as we want. Medium/Long term solution: * Make the Core more and more modular with components so that a Product can keep all the core except for a specific component for which it can have its own implementation for some time till that makes it inside the core. * Reduce Core release lifecycles. Right now it's 3 months. We could probably reduce that to 1.5 month right now. * In order to reduce that even further, have more automated functional tests in the Core so that we can release a stable release of the core every 2-3 weeks. Once we reach that stage, I think there won't be any need to have branches for products. However this requires a change of mind for XWiki core developers since developers would need to write tests as they commit code instead of committing stuff and then fixing them later on, in further betas or RCs. This is our Graal. Conclusion ========= Are we all ok to agree that the 1.1.x releases will thus contain changes/improvements (i.e. each change must be reviewed carefully so that it's not risky and does not endanger the stability of the branch)? Thanks -Vincent

18 years

1
0
0 0

[xwiki-devs] [ANN] XWiki Enterprise 1.1 RC 2 Released

by Vincent Massol

The XWiki development team team is pleased to announce the availability of the 1.1 RC 2 release of XWiki Enterprise Go grab it on http://www.xwiki.org/xwiki/bin/view/Main/Download This is a bug fix release and is meant to be the last RC. If no major bugs are found for 2-3 days it'll be promoted as the 1.1 final release. Please help us in testing it. Release notes: http://www.xwiki.org/xwiki/bin/view/Main/ ReleaseNotesXWikiEnterprise11RC2 Enjoy -The XWiki development team

18 years

1
0
0 0

[xwiki-devs] [Proposal] New GWT-based WYSIWYG editor

by Marius Dumitru Florea

Hi all, I've just joined the XWiki dev community today and this is my first post. As Vincent told you, from now on I'll be working on the new GWT-based WYSIWYG editor. I'll do my best, but I need your help on this. In the next few days I'll be reading the documentation for the new architecture, including WikiModel and GWT. After that, I'll post my ideas so you can make comments. Thanks everyone, -Marius

18 years

1
0
0 0

Re: [xwiki-devs] [xwiki-dev] [Proposal] Document comments should not create new versions

by Vincent Massol

(resending - I sent it on the 6th to the wrong OW dev list...) > If we don't increase version then how is it going to appear in the > history view. Namely, how would you see that a comment has been added? > > Of course we would still need to send notifications even when > comments are added. > > This is a general question about objects attached to a document. As > of now I'm not sure we should treat some objects differently than > others. > > Just to step back and play the devil, why is it bad that document > version is increased when comments are added? > > Thanks > -Vincent > > On Aug 24, 2007, at 4:44 PM, Sergiu Dumitriu wrote: > >> Hi, >> >> This is more a matter of opinions. Should a comment increase the >> version of a document? I'd say yes, but the view of simple users is >> that a comment should not affect the document, as it is something >> describing the document, not belonging to the document. So we should >> have a parameter that configures this. >> >> WDYT? >> Sergiu >> -- >> http://purl.org/net/sergiu

18 years

2
1
0 0

[xwiki-devs] XWiki 1.1.1

by Vincent Massol

Hi, I've created a 1.1.1 version in JIRA. The idea is to have only important bug fixes in that release and to release it before we release 1.2M1. The main reason why we need that 1.1.1 instead of going straight to 1.2M1 is because we have introduced important core changes in 1.2M1 and we probably need a bit of time to stabilize it and ensure it works seamlessly. Ludovic, I've moved the issue you had created for 1.1 to 1.1.1 since 1.1 is just a marker and right now the 1.1RC2 release is meant to be promoted as the final 1.1. If we make a change we'll then need a 1.1RC3 which I'd rather not have at this stage. Last I've proposed a date of 24th of September for the 1.1.1 release (in 2 weeks time). Let me know if this is ok for everyone. Thanks -Vincent

18 years

2
1
0 0

[xwiki-devs] Testers need for testing 1.1RC2

by Vincent Massol

Hi everyone, I've released XWiki Enterprise 1.1RC2 on our Maven remote repository and I need some help in testing it before we officially release it on OjwectWeb's Forge and announce it on xwiki.org. It would be nice if I could get at least 2-3 tester saying that the distribution is ok. Here are the files to test: * Platform WAR: http://maven.xwiki.org/releases/com/xpn/xwiki/ platform/xwiki-web-standard/1.1-rc-2/xwiki-web-standard-1.1-rc-2- hsqldb.war * Standalone zip: http://maven.xwiki.org/releases/com/xpn/xwiki/ products/xwiki-enterprise/1.1-rc-2/xwiki-enterprise-1.1-rc-2-hsqldb.zip * XE XAR: http://maven.xwiki.org/releases/com/xpn/xwiki/products/ xwiki-enterprise-wiki/1.1-rc-2/xwiki-enterprise-wiki-1.1-rc-2.xar * Generic installer for XE: http://maven.xwiki.org/releases/com/xpn/ xwiki/products/xwiki-enterprise-installer-generic/1.1-rc-2/xwiki- enterprise-installer-generic-1.1-rc-2.jar * Windows installer for XE: http://maven.xwiki.org/releases/com/xpn/ xwiki/products/xwiki-enterprise-installer-windows/1.1-rc-2/xwiki- enterprise-installer-windows-1.1-rc-2.exe Thanks a lot for your help! -Vincent

18 years

1
1
0 0

[xwiki-devs] Question regarding XEclipse version numbering

by Erin Schnabel

This may be silly, but would it be clearer if the XEclipse versioning contained some indication of the XWiki base required? To me, XEclipse v1.0 somehow suggests to me that it should be able to run on XWiki 1.0... which of course is not true. Might be good to have the prereq explicit in the versioning.. maybe? -- 'Waste of a good apple' -Samwise Gamgee

18 years

5
5
0 0

Re: [xwiki-devs] [xwiki-notifications] r4852 - xwiki-platform/core/trunk/xwiki-core/src/main/resources

by Vincent Massol

Hi Sergiu, I'm just curious, is your change below going to be valid on all DBs? Thanks -Vincent On Sep 9, 2007, at 1:04 AM, Sergiu Dumitriu wrote: > Author: sdumitriu > Date: 2007-09-09 01:01:36 +0200 (Sun, 09 Sep 2007) > New Revision: 4852 > > Modified: > xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.hbm.xml > Log: > XWIKI-1726: Exception deleting large documents > Fixed. > > > Modified: xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.hbm.xml > =================================================================== > --- xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.hbm.xml 2007-09-08 19:49:47 UTC (rev 4851) > +++ xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.hbm.xml 2007-09-08 23:01:36 UTC (rev 4852) > @@ -139,7 +139,7 @@ > </natural-id> > <property name="deleter" type="string" > column="XDD_DELETER" index="deleter"/> > <property name="xml" type="text"> > - <column name="XDD_XML" not-null="true" /> > + <column name="XDD_XML" not-null="true" length="1000000000"/> > </property> > </class>

18 years

2
1
0 0

Re: [xwiki-devs] XMLRPC Interface (was Re: [xwiki-notifications] r4850 - xwiki-platform/core/trunk/xwiki-core xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xml

by Catalin Hritcu

Hi Vincent, On 9/8/07, Vincent Massol <vincent(a)massol.net> wrote: [snip] > > I think the model classes should reflect more XWiki's concepts since > it's meant to abstract the implementation (swizzle). > > For example the following don't look right to me: Blog*, Comment, > Label, Rss*. In XWiki they are all Objects. So I'd rather see an > Object class in the interface and possibly some verification on the > object type in the swizzle implementation to map them to swizzle > concepts. > I think that what you suggest here is not even possible to implement on top of the Confluence API. I suggest you have a look at the code. Catalin > This is very important and we need to agree on that before we can > release 1.2M1 since when we release it then this api is in the wild > and it'll be harder to change it. > > What do others think? > > Thanks > -Vincent > > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs >

18 years

1
0
0 0

[xwiki-devs] XMLRPC Interface (was Re: [xwiki-notifications] r4850 - xwiki-platform/core/trunk/xwiki-core xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/client xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/model xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/model/swizzle xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium-tests xwiki-products/xwiki

by Vincent Massol

Hi everyone, On Sep 8, 2007, at 8:57 PM, Catalin Hritcu wrote: > Author: hritcu > Date: 2007-09-08 20:57:32 +0200 (Sat, 08 Sep 2007) > New Revision: 4850 > > Added: > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/client/ > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/client/SwizzleXWikiClient.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/client/XWikiClient.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/client/XWikiClientConversionException.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/client/XWikiClientException.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/client/XWikiClientRemoteException.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/ > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/Attachment.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/BlogEntry.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/BlogEntrySummary.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/Comment.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/Label.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/MapObject.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/Page.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/PageHistorySummary.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/PageSummary.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/Permission.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/RssFeed.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/SearchResult.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/ServerInfo.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/Space.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/SpaceSummary.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/User.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/UserInformation.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/ > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/AttachmentImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/BlogEntryImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/BlogEntrySummaryImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/CommentImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/LabelImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/PageHistorySummaryImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/PageImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/PageSummaryImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/PermissionImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/SearchResultImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/ServerInfoImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/SpaceImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/SpaceSummaryImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/UserImpl.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/model/swizzle/UserInformationImpl.java > Modified: > xwiki-platform/core/trunk/xwiki-core/pom.xml > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/ConfluenceRpcHandler.java > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > xmlrpc/DomainObjectFactory.java > xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium- > tests/pom.xml > xwiki-products/xwiki-enterprise/trunk/distribution-test/xmlrpc- > tests/src/test/it/com/xpn/xwiki/it/xmlrpc/AnonymousAccessTest.java > xwiki-products/xwiki-enterprise/trunk/distribution-test/xmlrpc- > tests/src/test/it/com/xpn/xwiki/it/xmlrpc/AttachmentsTest.java > xwiki-products/xwiki-enterprise/trunk/distribution-test/xmlrpc- > tests/src/test/it/com/xpn/xwiki/it/xmlrpc/CommentsTest.java > xwiki-products/xwiki-enterprise/trunk/distribution-test/xmlrpc- > tests/src/test/it/com/xpn/xwiki/it/xmlrpc/PagesTest.java > xwiki-products/xwiki-enterprise/trunk/distribution-test/xmlrpc- > tests/src/test/it/com/xpn/xwiki/it/xmlrpc/SpacesTest.java > xwiki-products/xwiki-enterprise/trunk/distribution-test/xmlrpc- > tests/src/test/it/com/xpn/xwiki/it/xmlrpc/framework/ > AbstractXmlRpcTestCase.java > Log: > XWIKI-1706: Use swizzle-confluence through a facade I think the model classes should reflect more XWiki's concepts since it's meant to abstract the implementation (swizzle). For example the following don't look right to me: Blog*, Comment, Label, Rss*. In XWiki they are all Objects. So I'd rather see an Object class in the interface and possibly some verification on the object type in the swizzle implementation to map them to swizzle concepts. This is very important and we need to agree on that before we can release 1.2M1 since when we release it then this api is in the wild and it'll be harder to change it. What do others think? Thanks -Vincent

18 years

1
0
0 0

[xwiki-devs] [Proposal] Separate module for XMLRPC/SOAP and remote wiki access in general

by Vincent Massol

Hi, Catalin is finishing his work on the xmlrpc API. We'd like to propose to create the following modules: xwiki-platform-core/ |_ xwiki-remote/ |_ model/ |_ client/ |_ server/ Where: * model: Generates a JAR and contains common objects shared between client and server code. Namely they are objects such as Space, Attachment, Comment, Page, User, etc (see http://swizzle.codehaus.org/ swizzle-confluence/ for more). Note: In the future, it's maybe possible that these be shared with XWiki's model objects too. * client: Client API for code needing to call XWiki servers from another JVM. * server: Server API in XWiki for accepting and handling remote APIs. Open questions: ============= * What about GWT? It's also a protocol to call XWiki remotely so we need to integrate it in this new structure. So maybe, instead use: xwiki-platform-core/ |_ xwiki-remote/ |_ model/ |_ client/ |_ server/ |_ gwt/ The reason I don't put gwt in clients/ and servers/ is because it's special as it's both and it generates client and server code when compiled. * Is it possible to share interfaces between the XMLRPC/SOAP implementation and the GWT one? * Do we want to have a separate module for the client/server APIs and for the implementations? My take is that we should put them in a single place and only separate them when we have more than one implementation. So when there are 2 we would have: xwiki-platform-core/ |_ xwiki-remote/ |_ model/ |_ client/ |_ api/ |_ swizzle/ |_ secondimplementation/ |_ server/ |_ api/ |_ swizzle/ |_ secondimplementation/ |_ gwt/ WDYT? Anything else I forgot? Thanks -Vincent

18 years

1
0
0 0

[xwiki-devs] XECLIPSE-21 : [actually - space description ignored in back-end xmlrpc]

by Asiri Rathnayake

Hi All, XECLIPSE-21 <http://jira.xwiki.org/jira/browse/XECLIPSE-21> complains that space description set on the space creation page (on xeclipse) is not added to the space's home page. But the actual problem is that addSpace() xmlrpc intentionally ignores space description . I think catalin worked on this and he has mentioned about this on the method comments. Anyway, i'm attaching a patch with this mail that would fix it. Catalin, is there a particular reason to ignore the space description ? Thanks. - Asiri

18 years

3
5
0 0

[xwiki-devs] [VOTE] Release XWiki 1.1RC2

by Vincent Massol

Hi, I'd like to start releasing XWiki 1.1RC2 as it is now. Is anyone still working on something for 1.1RC2? Here's my +1 to release now and as is. Thanks -Vincent

18 years

4
5
0 0

[xwiki-devs] Problems with PDF

by totoe

Hi! I've some problems with the PDF-Converter: If I use links like [Hi>http://www.hi.de>_blank] in my Wiki-Pages, the PDF-Converter doesn't work any more. With normal links (without _blank or _new) the converter has no problems... What can I do to solve this problem? It would be great if I get an answer! Kind regards, Torben

18 years

2
3
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