Hi,
When exporting the page into PDF displaying the following error.
How can solve this issue..?
org.dom4j.DocumentException: Error on line -1 of document : Premature end
of file. Nested exception: Premature end of file.
at org.dom4j.io.SAXReader.read(SAXReader.java:482)
at
com.xpn.xwiki.pdf.impl.PdfExportImpl.applyCSS(PdfExportImpl.java:332)
at
com.xpn.xwiki.pdf.impl.PdfExportImpl.applyCSS(PdfExportImpl.java:293)
at
com.xpn.xwiki.pdf.impl.PdfExportImpl.exportHtml(PdfExportImpl.java:202)
at
com.xpn.xwiki.pdf.impl.PdfExportImpl.export(PdfExportImpl.java:225)
at
com.xpn.xwiki.web.ExportAction.exportPDFOrRTF(ExportAction.java:198)
at com.xpn.xwiki.web.ExportAction.render(ExportAction.java:61)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:189)
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:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Nested exception:
--
Prathap
Greetings
I finally completed my knowledge base. I separate the information in pages, and organize it by subject and
knowledge base. To do that I tag every page with a subject tag and a knowledge tag always started with "KB-".
If I want one page pesent in two knowledge bases I only nedd to tag it with the tags.
I send the example for you to see and say if it's worthy of being in the XWiki Code Zone?
Best regards
Bruno Neves
Hi,
I'd like to give the rights for the wikimodel project to reuse our
LocalEntityResolver class even though xwiki is under the LGPL 2.1
license and wikimodel under the Apache 2.0 license.
This is to fix http://code.google.com/p/wikimodel/issues/detail?id=37
I guess we need agreement from all contributors to this class. I guess
the main authors are Ludovic and myself.
So here's my +1
Thanks
-Vincent
Hi,
I just finished the implementation of full OpenID support for XWiki (see
http://jira.xwiki.org/jira/browse/XWIKI-2630). You can now create an user
account without password by using a OpenID from Yahoo, AOL, MyOpenID or any
other OpenID provider out there.
The other feature is that every XWiki user now gets a OpenID that he can use
on other OpenID sites to create an account without the need for yet another
username and password.
More infos about OpenID can be found on the official site:
http://www.openid.net/
Please test my work as much as you can. Thanks a lot
Have a nice weekend,
Markus
Hi,
We need to decide if we want our component implementations (the class
implementing the interface of a component) to be user-public or not.
By user-public I mean allowing user of the code to use them (for
composition, for inheritance). The alternative is to make them
internal and forbid users to import them. This means moving them to an
internal package (see http://www.eclipse.org/articles/
article.php?file=Article-API-Use/index.html) and telling
our users that they change anytime so they shouldn't use them. This
would also mean we wouldn't have to go through a deprecation stage to
make any change to our components.
My initial reaction to this was that they should be public but the
more I think about it the more I think making them internal might be
the best choice.
WDYT?
Thanks
-Vincent
Hi all,
I spent some time on completing ApplicationResources and replacing hard
coded messages in templates and would like now to discuss some issues
regarding translations.
In my opinion, the bundles became large, unclear, use different syntax rules
(sometimes simple keys, sometimes with prefixes and underscores, sometimes
built like node-structure...) and it’s difficult to find out if some of them
are not in use anymore and if some are missing.
I agree with http://jira.xwiki.org/jira/browse/XWIKI-918 - we need to clean
up the ApplicationResources and I think we could restructure/reorganize
resources files using nodes-structure and separate first of all separate XE
from other applications (in my opinion, every application should have its
own bundles – that would allow to manage translations easily) – just create
new AppRes with the clear-defined structure.
Perhaps there are the better solutions, but I find even the splitting inside
XE on xwiki-web (templates) and xwiki-wiki (default xar) would be already
helpful for insert the new keys and removing the wasted ones.
WDYT?
Best Regards,
Alla
--
View this message in context: http://n2.nabble.com/Internationalization-and-Localization-tp789607p789607.…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Greetings
It's possible to rename a tag present in diferent pages at once, or the only way is opening all the pages
where it is and rename it?
Best regards
Bruno Neves
Hi Vincent,
1) add props.setPruneTags("script, style"); in DefaultHTMLCleaner.
This will remove all the script and style tags and their contents.
script and style tags are useless for the later use, IMO.
2) remove the first p tag following th li tag.
<ul>
<li><p>test</p></li>
</ul>
could not render properly in xwiki syntax 1.0 and
xhtmlparser+xwikisyntaxrendering.
It should change to
<ul>
<li>test</li>
</ul>
I have a filter with w3c dom:
http://svn.xwiki.org/svnroot/xwiki/sandbox/xwiki-plugin-officeimporter/src/…
Maybe can help. If you need a jdom version, I can provide it later if necessary.
3) empty link. like <a/> <a href="">test</a> <a>something</a>
http://svn.xwiki.org/svnroot/xwiki/sandbox/xwiki-plugin-officeimporter/src/…
this filter can remove empty link tag.
Thanks
Wang Ning
Hi Vincent,
Sorry for not send the mail to the dev list. I just reply the mail.
On Sun, Aug 24, 2008 at 4:15 PM, Vincent Massol <vincent(a)massol.net> wrote:
>
> On Aug 24, 2008, at 6:40 AM, Wang Ning wrote:
>
>> Hi,
>>
>> Yes, I think it's necessary, if the client want to control the output
>> directory.
>
> Ok I've thought a bit about this and here's what I propose:
>
> 1) Introduce a new ConverterOutput interface with the following methods:
> - saveImage(String imageName, InputStream imageData);
> - saveDocument(InputStream documentData);
>
> 2) Modify Converter interface to be:
>
> void convert(InputStream sourceData, OfficeDocumentType sourceType,
> ConverterOutput outputData, OfficeDocumentType outputType);
>
> 3) Provide 1 implementation of ConverterOutput for the moment (+ a mock one
> for the unit tests of the Converter): XWikiDocumentConverterOutput. This
> implementation stores the result of the conversion in a XWiki Document (it's
> name/location is passed in the constructor). In the future if we need other
> implementations we could add them (like a FileConverterOutput, etc) but
> they're not needed for now.
>
> Note 1: 3) is much cleaner and allows to move some of the code in the plugin
> to the XWikiDocumentConverterOutput class.
> Note 2: We can fully read the sourceData internally to save the input data
> to a file in a XWiki temporary directory (and thus control the output of the
> image files by jodconverter)
If want to get the xwiki temp directory to handle the output dir of
conversion in OfficeConverter, I need use
context.getWiki().getTempDirectory(context) to get the xwiki temp dir.
But I don't think I can get the xwiki temp without a xwik context.
Maybe the interface should change to
void convert(InputStream sourceData, OfficeDocumentType sourceType,
ConverterOutput outputData, OfficeDocumentType outputType,
XWikiContext context) throws OfficeConverterException;
WDYT?
--
Thanks
Wang Ning
syam_kg wrote:
>
> Hi
>
> In the Registartion section of Admin Preferences,there is a field 'Check
> Active fields for user authentication'. Could anybody please tell me what is
> meant by this. Also please explain what should be put into the fields
> 'Validation e-Mail Content ','Confirmation e-Mail Content' and 'Invitation
> eMail Content' and how xwiki validates the registration.
>
Selecting "Use email verification" causes a verification email to be
sent to the email address provided by the user at registration. Still,
this doesn't prevent the user from logging in and using his account
until following the validation link in that email.
On the other hand, selecting "Check Active fields for user
authentication" does exactly this: prevent the user from using his
account until following the validation link.
Last night I committed some values for the validation and confirmation
email, which will be part of XWiki Enterprise starting with 1.6M1. Until
1.6 is released, you can put these in your wiki:
Validation email content:
#set($wikiurl = $xwiki.getDocument("Main.WebHome").getExternalURL())
#set($wikiname = $wikiurl.substring($wikiurl.indexOf("//")))
#set($wikiname = $wikiname.substring(2, $wikiname.indexOf("/", 3)))
Subject: Validate your account on $wikiname
Hello $xwiki.getUserName("XWiki.$xwikiname", false),
This email address was used to register a new account on ${wikiname}. If
you did not make the request, please ignore this message.
In order to activate your account, please follow this link:
$xwiki.getDocument("XWiki.AccountValidation").getExternalURL("view",
"validkey=${validkey}&xwikiname=${xwikiname}")
Confirmation email content:
#set($wikiurl = $xwiki.getDocument("Main.WebHome").getExternalURL())
#set($wikiname = $wikiurl.substring($wikiurl.indexOf("//")))
#set($wikiname = $wikiname.substring(2, $wikiname.indexOf("/", 3)))
Subject: Your account on $wikiname has been activated
Hello $xwiki.getUserName("XWiki.$xwikiname", false),
Your account on $wikiname has been successfully activated. You can now
login at $xwiki.getDocument("XWiki.XWikiLogin").getExternalURL("login")
using your username ($xwiki.getDocument($xwikiname).getName()).
You must also create a wiki page at XWiki/AccountValidation and put this
content:
#if("$!{request.validkey}" != "" && "$!{request.xwikiname}" != "")
#if($xwiki.validateUser(true) == 0)
#set($loginURL = $xwiki.getURL('XWiki.XWikiLogin', 'login'))
#info("Your account has been activated. You can now <a
href='${loginURL}'>login</a>.")
#else
#warning("There was a problem validating your account. Please
contact an administrator.")
#end
#else
$response.sendRedirect($xwiki.getURL("Main.WebHome"))
#end
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi Vincent,
I try to make the xhtmlparser work for the link. I have see the test
case links.test in xwiki-core-rendering.
I have some questions.
1) the xhtmlparser don't handle the rel attribute. Because wikimodel
don't pass the information in xhtmlparser. see
http://code.google.com/p/wikimodel/issues/detail?id=47. When this is
fixed, I think rel can works.
2) The output of <a href="mailto:john@doe.com">mailto:john@doe.com</a>
should be [[mailto:john@doe.com>mailto:john@doe.com]] but not
[[mailto:john@doe.com]]. We should not remove the label information of
mailto. Consider if the input is <a href="mailto:john@doe.com">Contact
me</a>, the output should be [[mailto:john@doe.com>Contact me]]
--
Thanks
Wang Ning
Hi,
I'd like to discuss the granularity we want to have for our
applications. This discussion was prompted by the recent password-
reset application. There are some pros and cons I think of having
small applications.
Pros:
- better compartimentation
- different release cycle
Cons:
- heaviness of release (separate XAR; etc)
- different release cycle
- fragmentation
My personal take is that this application should go under the
administration application so that it's released together with it (it
could be a sub module that is aggregated in the final XAR for the
admin app.).
WDYT?
Thanks
-Vincent
The new JDBC driver for postgresql 8.3.3 supports set/getcatalog()
now. Does that mean we can finaly use it with virtual xwiki ?
cheers
Michal
Michal Bielicki, COSO, Member of the Board
HaloKwadrat | ul. Polna 46/14, 00-644 Warszawa
t. +48228753290 x 203 | f. +48228753291
michal.bielicki(a)halokwadrat.pl | w. www.halokwadrat.pl
Knowledge & Low Prices. Guaranteed!
Halo Kwadrat Sp. z o.o.
z siedzibą w Warszawie przy ulicy Polnej 46/14,00-644 Warszawa
wpisana została do rejestru przedsiębiorców prowadzonego przez
Sąd Rejonowy dla M.ST.Warszawy w Warszawie, XII Wydział Krajowego
Rejestru Sądowego pod numerem
KRS 0000153539. NIP 525-22-59-473
Wysokość kapitału zakładowego: 50000,00 PLN
----------------------------------------------------------------------------
Wiadomość ta jest przeznaczona jedynie dla osoby lub podmiotu
będącego jej adresatem
i może zawierać poufne lub uprzywilejowane informacje. Zabronione
jest przeglądanie,
przesyłanie, rozpowszechnianie lub inne wykorzystywanie tych
informacji, jak również
podejmowanie działań na ich podstawie, przez osoby lub podmioty inne
niż zamierzony adresat.
Jeżeli otrzymali Państwo tę wiadomość przez pomyłkę, prosimy o
poinformowanie o tym nadawcy
i usunięcie jej z komputera.
Hi Vincent,
When I implement the XWikiDocumentConvertOutput, I meet some pb. I
understood that the XWikiDocumentConvertOutput contain a xwiki
document, and it will store the result html to the xwikidocument as
content, store the images to the xwikidocument as the attachments, and
save this xwiki document to the xwiki.
But we should separate the officeconverter from xwiki core, so
XWikiDocumentConvertOutput can't get any information about xwiki
contex, right?
Problems with this design:
1) when I use the saveDocument() method to save the inputstream to
document content, I need convert inputstream to html. But I can't get
the encoding of the xwiki because I can't access the xwiki context.
2) I can't set the attachments' author, because have no idea about the
author without context.
3) I can't save the xwikidocument to the xwiki without the xwiki context.
4) Maybe we can just save everything in the xwiki document and get it
from ConverterOutput and set author, then save it to the xwiki. If so,
we need a method getDocument() in ConverterOutput to get the document.
5) Actually, not all the accessory output is image. So the saveImage
interface is not appropriate.
Why we use ConverterOutput? I think because:
1) the output of conversion(especially convert to html) have no only
one output, so we just use ConverterOutput to save all this outputs
and their names for later use.
2) Maybe the special ConverterOutput like XWikiDocumentConvertOutput
can handle the coversion result to the special destination in special
format.
I think 2) is not right, because it make the office convert connected
to xwiki context.
So I proposal ConverterOutput is just a data structure to store the
output results and their name. My proposal is:
public interface ConverterOutput
{
/**
* Save the target contents in {@link InputStream} to the output
destination. And save the document's name as the
* main output file's name.
*
* @param documentName the name of the source content
* @param documentData the source data
*/
void saveDocument(String documentName, InputStream documentData);
/**
* Save the other output files like images, other htmls to the
output destination. In most case, this method will be
* used when convert office convert to html.
*
* @param accessoryName the accessory name
* @param accessoryData the accessory content
*/
void saveAccessory(String accessoryName, InputStream accessoryData);
/**
* @return the main document
*/
InputStream getDocument();
/**
* @return return the main document's name
*/
String getDocumentName();
/**
* @return the accessories of this document. The map's key is the
accessory's name.
*/
Map<String, InputStream> getAccessories();
}
I implement the office converter with this interface. Please review
the code at your convenience.
--
Thanks
Wang Ning
Hi Vincent & devs,
You are busy for 1.6M1 today, so you can handle this email later at
your convenience.
To provide something can work for gsoc, I take the convert2html
feature back with a little change about the filter. So the
officeconverter core + officeconvert plugin + office import appliation
can do:
1. import office document like doc, xls, ppt, odt, odp, ods to xwiki
page in html format. This feature works well in most case. Just try
it. It handles the images, the slides in ppt odp.
2. import office documents to xwiki page in xwiki syntax 2.0 format.
This feature is relative to xhtmlparser in new rendering. So it can
only work for some case. table, link, image, list are not supported
well.
I think this can be called some thing works in some extent.
--
Thanks
Wang Ning
Hi,
We're a bit late on the planning/roadmap so here's a first try.
* 1.6M1: 18 Aug
* 1.6M2: 8 Sep
* 1.6RC1: 15 sep
* 1.6RC2 or 1.6 final: 22 sep
Tentative Roadmap for XE 1.6:
Must have:
========
* Beta versions of new rendering + new WYSIWYG editor (Vincent & Marius)
* One of the following two:
** Revamped Blog UI + features (who?)
** Easy creating of structured pages (JV)
* Security issues already in JIRA (marked as high priority)
+ bug fixes or course
Good to have
==========
* Office import maybe but I think that should be optional depending on
how fast it progresses. It could be released as a separate plugin for
sure.
* Single sign on w/ openID
* French XE
* Send forgotten password
* Improved RSS feeds
* Excel plugin
* Installation wizard
* Skin extension/Interface extension finalization
* CSS + templates cleanup/simplification
* Invitation manager in XE
My personal take is that the core development team should really focus
on the "Must Have" and continue consolidating what we have by working
on make it more stable, nicer looking and more usable, rather than
working on new features. Of course we have all those nice SOC projects
(office import, sso) that we should release/integrate if they are
ready at the end of the milestone 2 of XE 1.6.
WDYT?
Thanks
-Vincent
Hi!
I am looking for some information on the supportablitlty of Xwiki with
SSO for authentication. At this stage, I am exploring the options on
how to set this configuration up. There is not much documentation
available on the Xwiki site on information for integrating with SSO
siteminder though a reference to siteminder is available on the site(
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication check
under Custom Aunthentication). I was wondering if any of you could
direct me towards more resources/documentation...
Thanks.
Sharan.
-----------------------------------------
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.
Hi,
Here's a proposal for implementing configuration in the new
architecture, using components.
Note: I think this is compatible with Sergiu's proposal here: http://tinyurl.com/6md5jd
General requirements
=================
* Each module/component can define its own configuration
* Accessing configuration parameters from Java should be strongly
typed (ie. getLinkLabelFormat() for getting the link label and not
getParameter("linklabelformat"))
* It should be possible to load Configuration data from different
sources (properties file, xml files, database, xwiki documents, etc)
* Configuration sources should have an order
* Any module/component should be able to get the configuration for
other module/component but in read only mode
* It should be possible to dynamically add a new configuration source
at runtime
* Configuration data should be loaded and cached
Proposed Implementation
====================
* Each module/component defines its configuration in a component which
is a java beans. For example let's take the rendering module. We would
have a RenderingConfiguration component as in:
public interface RenderingConfiguration
{
String getLinkLabelFormat();
}
public class DefaultRenderingConfiguration implements Initializable,
Reloadable, RenderingConfiguration
(in practice will extend AbstractConfiguration class probably)
{
private String linkLabelFormat;
// Injected
private ConfigurationManager manager;
public void initialize()
{
// Define the Configuration sources here. Default
configuration sources would be defined in AbstractConfiguration
probably)
List configurationSources = ....
// Configuration namespace (all properties should start with
the namespace value)
String namespace = "rendering";
reload();
}
// Should be located in AbstractConfiguration
public void addConfigurationSource(ConfigurationSource source);
public void reload()
{
// Populate java bean
manager.populate(this, configurationSources, namespace);
}
public void setLinkLabelFormat(String linkLabelFormat) {...}
public String getLinkLabelFormat() {...}
}
* The DefaultRenderingConfiguration class is registered as a component
in components.xml and with a singleton lifecycle. This means the data
it contains are cached for the whole application lifetime. They can be
reloaded using reload().
* The ConfigurationManager implementation will use Jakarta BeanUtils
to automatically populate a javabeans. It'll also use Jakarta Commons
Configuration for implementations of ConfigurationSource.
* ConfigurationSource interface should have a method like: Object
getParameter(String name). More details to be defined later.
* Code wanting to get Rendering Configuration would simply define a
component dependency on DefaultRenderingConfiguration and they'll have
it injected for them.
* There'll be a XWikiDocumentConfigurationSource that gets parameter
values from one or several xwiki documents. We'll need to define how
we get them but we could provide some standard XWikiConfigurationClass
for a single configuration element for example.
* The idea of the namespace is to use the package name and remove the
"org.xwiki" or "com.xpn.xwiki" prefix. For example
"org.xwiki.rendering.*" leads to "rendering.*".
WDYT?
If we agree I can whip up a first implementation of this relatively
quickly I think.
Thanks
-Vincent