Hello,
I am working on creating blog entries using xwiki. I was wondering if it would be possible to create a template for the blog entries so that they will be more structured?
Thank you for your time and help!
Hande Aksac
Hi,
Since I'm rewriting the new Rendering component
(see http://dev.xwiki.org/xwiki/bin/view/Design/NewRenderingArchitecture)
, we need to finalize the new syntax we want to have.
Right now I'v planned to use the same wiki syntax as now
(http://platform.xwiki.org/xwiki/bin/view/Main/
XWikiSyntax#HTextStyles) with only one change: all macros now need to
be closed.
For example: {macro}...{/macro} and {macro:text|param=value|.../}
Is that ok with everyone or do we want to make changes?
Thanks
-Vincent
Hi,
I have installed the xwiki.war complete all the intructions for Tomcat
Servlet and MySQL Database configuration. But my xwiki is not working
properly ,its giving me the following error.
I have installed the enterprise version of xwiki war. I have gone throught
the forum to see if anyone's got a similar error , but looks like its just
me, just in case if i have missed this error posted by some user and if
there was a solution posted earlier, please point me to that link.
Here is the exception what i get
type Exception report
message
description The server encountered an internal error () that prevented it
from fulfilling this request.
exception
javax.servlet.ServletException: Error number 3 in 0: Could not initialize
main XWiki context
Wrapped Exception: Error number 3001 in 3: Cannot load class
com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from
param xwiki.store.migration.manager.class
Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
Wrapped Exception: Hibernate Dialect must be explicitly set
org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:535)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:433)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
root cause
com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main
XWiki context
Wrapped Exception: Error number 3001 in 3: Cannot load class
com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from
param xwiki.store.migration.manager.class
Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
Wrapped Exception: Hibernate Dialect must be explicitly set
com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:328)
com.xpn.xwiki.XWiki.getXWiki(XWiki.java:515)
com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:136)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
note The full stack trace of the root cause is available in the Tomcat logs.
ANd i have installed JDK 1.5.
Can please let help me out with this error.
Thanks,
Nishii
--
View this message in context: http://n2.nabble.com/Could-not-initialize-main-XWiki-context-tp534219p53421…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
We need a deprecation strategy, i.e. decide for how long we keep
@deprecated methods/classes.
I propose to keep them for 2 full releases after the current version
is released as final.
For example if a method is deprecated in, say Core 1.3M2 then the
method will be removed in 1.6M1. Of course any major new release can
deprecate anything so a XWiki 2.0 is expected to break backward
compatibility.
So for methods deprecated in 1.0 we can remove them in 1.3M1, M2, etc.
WDYT?
If ok then I'll add this to our dev practice guide too.
Note that for this to be easy anyone deprecating methods should add
the information of when it was deprecated. For example:
/**
* @param time the time in milliseconds
* @return the time delta in milliseconds between the current
date and the time passed
* as parameter
* @deprecated replaced by {@link
com.xpn.xwiki.api.Util#getTimeDelta(long)} since 1.3M2
*/
public int XWiki.getTimeDelta(long time)
{
return this.util.getTimeDelta(time);
}
Here's my +1
Thanks
-Vincent
Hello Xwiki-Devs,
I am not quite sure if this one is just a stupid question I haven't been
able to find an answer for, or if it is just impossible.
Situation is this: If you hava a link in a page e.g. "[GrannySmith]" and
and this page doesn't exist yet (so it'll get a questionmark as marker),
as soon as somebody clicks on that link xwiki will suggest to create a
new Page or go straight to the editor. So far so clear. Now for instance
I have a xwiki class called "Apple" can I create a link that mandates
that the newly created page should be of the class "Apple" (respectively
should have an object of "Apple")? Or is there any other way to
accomplish this?
thanks and greetings
Jonas
Hello,
has anybody the same slow and choppy scrolling issue under Firefox3 with
XWiki?
Apparently this is linked to the fixed CSS background for the header menu...
It doesn't appear on all hardware/OS configurations but lots of people
complain about it.
As XWiki uses a fixed background by default, I preferred warning you because
this is really a pain using xwiki under FF3 on my computer :)
(if you remove the "fixed" CSS field, it works betteeeeeeeer)
regards
Pascal
Hi, devs.
I committed first version of XWQL (or XQL) language to our sandbox
(xwiki-query/xwql) for review.
I worked ~2 last weeks for it.
install info is in xwiki-query/README.
Currently it works according my proposal[1], but it is quite easy to modify.
It is not perfect, but it works and will be improved.
You can test it via QueryManager. (for example in velocity:
$xwiki.xWiki.store.queryManager.createQuery("select doc.fullName from
Document as doc, doc.XWiki.ArticleClass as a where a.title like
'%Launch'", "xwql").execute() )
plan for xwql (for fix in next week):
* use xwiki-bridge instead of xwiki-core in xwql.
(some methods in bridge are needed)
* create query velocity service
accessible like $services.query.xwql('...')
(according Vincent's velocity services proposal [2])
* move xwiki-query maven module from sandbox to platform/components/
* move QueryManager component from xwiki-core to xwiki-query
I would like to integrate xwql for hql in 1.6M2 (8 Sept) and improve it
in RC if needed.
JCRStore:
old JCRStore with some modifications is partly working (save/load
document is ok) on recent Jackrabbit, but missing some new stores and
need redesign.
plan:
* create xwiki-store/jcr maven module in platform/components (at
sandbox first)
it have to depend on xwiki-core (but not reverse). Is it a problem
for platform/components?
* split JCRStore into components. (RepositoryFacory, SessionFactory,
SessionPool, Stores, DAOs)
* jcrstore will contains DefaultStores which will contain only
business logic on data model, and use DAOs components for store/load data.
DefaultStores will be reused in future HibernateStore to remove
duplicating of code.
* get rid of patched graffito-jcr-mapping (~ORM for JCR). it is old and
unsupported.
candidates:
jcrom [3],
jackrabbit-ocm (former graffito),
simple hand-made annotation based mapping.
I'll look at jcrom first.
I already have some code and plan to work on it in sandbox, after finish
with xwql-hql.
I plan to create working version of JCRStore at the end of September.
xwql on JCRStore will work only on JCRv2 implementation.
[1] http://xwiki.markmail.org/message/uar73uglivj6fbbn
[2] http://markmail.org/message/jwcjomrck3yo2kjq
[3] http://code.google.com/p/jcrom/
--
Artem Melentyev
Hello,
I've tried building platform and XE from trunk under Eclipse 3.4(Ganymede)
with last M2Eclipse (Maven embedded 2.1.0 with m2eclipse 0.9.5) which brings
lots of new features but also some new problems...
I've checked out full platform trunk and tried to use the "nested modules
management" of m2eclipse in order to have something clean... so check out
using Subclipse and then activated Maven dependency management, Workspace
resolution and Nested Modules...
Due to some new features of both maven and m2eclipse and due to new nested
modules, there are some problems building everything from scratch...
Here are my short remarks (I'm only maven and eclipse user so this is what I
can seem with an external point of view):
- the famous out-of-memory still exists when building aspects so still needs
to creates a specific Run target with the now famous "-XmxLOTS_OF_MEMORY"
- now in Maven, compiled classes are separated: main classes goes in
target/classes and test classes goes in target/test-classes (which is not so
bad)
- In XWiki platform, we have now up to 3 levels of nested modules and
apparently the maven inheritance is not well managed by m2eclipse. By
default, maven tests are not run using parent compiled classes and I had to
explicitely trigger "resolve Workspace artifact" in my specific Maven Run
target not to have "no class def found exception for ...XWikiContext" when
running maven:test.
- the "resolve Workspace artifact" is sometimes not good: for web/standard,
it tries to copy the file xwiki-core/target/classes but as it is a
directory, it fails to copy it :)...
- Moreover, m2eclipse seems to run maven tests using target/classes from
parent or locally dependent maven modules but not target/test-classes. And
in XWiki, xwiki-rendering/xwiki-rendering-tests, for example, uses classes
from xwiki-core tests classes. I haven't found a clever solution for this.
- I can also see some code errors in Eclipse in web/gwt because Eclipse trie
to resolve some deprecated functions from xwiki-core trunk... not a problem
when compiling with maven
One other question about something I remark:
when compiling, I see this tens of times:
url = http://maven.xwiki.org/externals
Downloading:
http://maven.xwiki.org/externals/groovy/groovy-all-1.0-jsr/06/groovy-all-1.…
url = http://maven.xwiki.org/releases
Downloading:
http://maven.xwiki.org/releases/groovy/groovy-all-1.0-jsr/06/groovy-all-1.0…
url = http://repo1.maven.org/maven2
Downloading:
http://repo1.maven.org/maven2/groovy/groovy-all-1.0-jsr/06/groovy-all-1.0-j…
Apparently, it doesn't see it has already downloaded it... Do you know why?
So finally, compiling module per module triggering some options is OK but
compiling from scratch implies skipping tests...
Pascal