Hello,
while trying to import Word document (non trivial) I'm hitting an issue
where underlaying PostgreSQL complains about value too long to be
stored. The message (cut from the console) looks as:
SQL next exception = [org.postgresql.util.PSQLException: ERROR: value
too long for type character varying(200000)]]
Actual exception looks like:
XWD_VERSION='2.1', XWD_CUSTOM_CLASS='', XWD_PARENT='', XWD_CLASS_XML='',
XWD_ELEMENTS='0', XWD_DEFAULT_TEMPLATE='', XWD_VALIDATION_SCRIPT='',
XWD_COMMENT='Created by office importer.', XWD_MINOREDIT='0',
XWD_SYNTAX_ID='xwiki/2.0', XWD_HIDDEN='0' where XWD_ID='-408553786' was
aborted. Call getNextException to see the cause.
at
org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError(AbstractJdbc2Statement.java:2598)
~[postgresql-9.0-801.jdbc4.jar:na]
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1836)
~[postgresql-9.0-801.jdbc4.jar:na]
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:407)
~[postgresql-9.0-801.jdbc4.jar:na]
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2737)
~[postgresql-9.0-801.jdbc4.jar:na]
at
org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
~[commons-dbcp-1.3.jar:1.3]
at
org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
~[commons-dbcp-1.3.jar:1.3]
at
org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
~[commons-dbcp-1.3.jar:1.3]
at
org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48)
~[hibernate-3.2.6.ga.jar:3.2.6.ga]
at
org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246) ~[hibernate-3.2.6.ga.jar:3.2.6.ga]
... 137 common frames omitted
this is XWiki 3.1 enterprise with few our custom patches but they are
not related to the storage nor import functionality, so I guess we've
not broken this ourself.
Do you have any idea how to workaround this issue or even how to
properly fix it?
Thanks a lot!
Karel
Hi all
It's a following of the recent discussion on this list :)
I have provided the basis for a java backed {{panel}} macro implementation.
The source code is currently hosted on my github account, but I would like
to move it under xwiki-contrib.
See https://github.com/sauthieg/xwiki-panel-macro
I've inited an extension page for this macro on the extension wiki:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Panel+Macro
BTW, what is the type for a Java Macro ? Macro type seems to be restricted
to Velocity ...
Any interest ?
--G
Hi,
The component writing tutorial seems outdated at
http://platform.xwiki.org/xwiki/bin/view/DevGuide/WritingComponents
The dependencies seems to not exist anymore
<dependencies>
<dependency>
<groupId>org.xwiki.platform</groupId>
<artifactId>xwiki-core-component-default</artifactId>
<version>${platform.core.version}</version>
</dependency>
<!-- Testing dependencies -->
<dependency>
<groupId>org.xwiki.platform</groupId>
<artifactId>xwiki-core-shared-tests</artifactId>
<version>${platform.core.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
Should the first one be:
xwiki-platform-component-multi
and
xwiki-platform-test
?
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi,
I will be in London tomorrow until thursday. We will be (with Guillaume
Lerouge) at the Online Information Show at the National Hall, Olympia (
http://www.online-information.co.uk/)
If there are some XWiki users that would like to meetup in London either
Tuesday or Wednesday night, please give ring us.
Ludovic
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi all
Some weeks ago, I've been discussing in IRC with Thomas and Vincent about
contributing a {{panel}} macro that could be used to replace the old
velocity #panelHeader()/#panelFooter() macro...
I've pushed that code into github :
https://github.com/sauthieg/xwiki-panel-macro
ATM, it probably has less features than the old velocity stuff, but I'm
sure it is a good starting point if you want to move to a Java-based panel
macro.
The code is tested using the XWiki Test Runner.
So if you're interested in that code, I'll be happy to re-contribute it to
XWiki.
Any thoughts ?
--Guillaume
Hi (Marius),
With the new powerful sheet system it's now very hard to know where is located the sheet used to display the page (it's magical now ;)).
Thus I think that when editing a page in wiki/wysiwyg edit modes we need to display a link to edit the sheet used to display the page, in the Document Information panel.
WDYT?
Thanks
-Vincent
Hi guys,
I'm trying to reduce the enormous number of lock done by the current
implementation of Embedded Component Manager and I could use some more
brains to check what I did.
You can find the new version on
https://github.com/xwiki/xwiki-commons/blob/feature-improvecm/xwiki-commons…
Quick comparison with the current one:
* removed all "synchronized (this)" that was in pretty much all the
methods and which made the CM block everything whenever anyone was
using it
* used ConcurrentHashMap to securize the insertion/search of components
* basically the only remaining explicit lock is on singleton component
initialization mostly to make sure we don't initialize the same
component at the same time
If you find some small modification to improve a bit the speed don't
hesitate too. There is possible improvements to speed up lookuplist
and lookupmap (not going though the whole map basically) but it
require important refactoring and I would prefer not doing too much
things at once since it's a pretty critical peace of code and locking
is the main issue right now.
Thanks,
--
Thomas Mortagne
Hi devs,
Summary:
========
I'd like to add the notion of Priority to Event Listeners. The reason is that in some cases it's important that some listeners execute before others.
The problem at hand:
=================
Here's a typical use case: When receiving the ApplicationStartedEvent, we have lot of code that needs to initialize. Initialization order is important (you can compare it to run levels in OS): for example some init must happen after the Database initialization has happened.
Note that another solution exists for this use case: some initializations could introduce their own events (such as a DatabaseStartedEvent) and other init could listen on those events instead of the generic ApplicationStartedEvent. However I can see several drawbacks to this:
* it's less generic than the priority solution
* it means creating more events
* but more importantly it means that modules will have strong dependencies (at maven level) on each other whereas it's not necessary and shouldn't be the case. In our example use case: it means that inits that must happen after database is started will need to depend on oldcore (which is where DB is started ATM)
Proposal:
========
* Don't break backward compat in Observation module
* Introduce a PrioritizedEventListener interface that adds a getPriority() method
* Modify ObservationManager implementation to take into account priorities
* In order to make it simple I propose to have only a single priority per Listener and not a priority per event supported by a given listener
General Context
=============
To give some context here's what I'd like to do on the medium term:
* Step 1: Introduce notion of priority in EventListeners
* Step 2: Refactor XWiki init to use an EventListener on AppStarted with low priority
* Step 3: Refactor wiki macros to use an EventListener on AppStarted with priority value lower than at step2
* Step 4: Write an EventListener for the new UI Extensions with a priority value higher than the one of step2 <-- this is the initial goal that led me to make this proposal ;)
WDYT?
Thanks
-Vincent
Hi Everyone!
I have read this document "Writing GWT applications in XWiki" (
http://dev.xwiki.org/xwiki/bin/view/Drafts/WritingGWTApplicationsInXWiki)
And I know how to develop GWT module for xwiki now. I also have read the
document "WYSIWYG Editor Module" (
http://code.xwiki.org/xwiki/bin/view/Modules/WysiwygEditorModule). I
followed the instruction which tried to integrate the WYSIWYG editor(GWT
application) in wiki pages, and I put the following code in my wiki editor:
"{{html}}
<script type="text/javascript" src="XWikiWysiwyg.js"> alert('WYSIWYG code is
loaded!'); </script> <textarea id="demo"></textarea> <script
type="text/javascript"> Wysiwyg.onModuleLoad(function() { new
WysiwygEditor({hookId:'demo'}); alert('WYSIWYG code is loaded!'); });
Wysiwyg.onModuleLoad(function() { editor = new WysiwygEditor({hookId:
'demo'}); }); }); </script> {{/html}}"
After saved, it only display a blank text area without any sign of WYSIWYG
editor, also there is no alart 'WYSIWYG code is loaded!' popup. Can you help
me figure it out what is wrong with it?
I am planing to develop a tree view using GWT to display Design Rationale
Element. Could you give me some ideas of after my development, how can I
embeded the GWT application into Xwiki pages and interact with the GWT
application?
Thank you very much!
Leon