Hi,
I've noticed that we're bundling both C3P0 and Apache DBCP connection
pools frameworks. Do we need to bundle 2?
By default we have DBCP configured in our hibernate.cfg.xml files.
I'm thus proposing to drop C3P0 from the distribution WAR.
WDYT?
Thanks
-Vincent
[reposting because of wrong xwiki-users address. please reply to this
email and not the previous one]
Hi,
I'm beating Vincent by announcing XWiki Watch 1.0M1 before he announces
XWiki 1.1M2 (which is needed for XWiki Watch 1.0M1).
XWiki Watch 1.0M1 is the first official release and is a functional beta.
XWiki Watch is:
- A collaborative RSS/Atom Feed aggregator
- Feeds, Groups and Keywords configuration using an AJAX interface.
Configuration are managed by spaces.
- Storing of articles themselves in XWiki pages using the FeedPlugin's
capabilities
- AJAX UI to navigate articles, open the content
- Collaborative tagging, commenting and flagging of articles, store a
'read' status
- Filtering UI to see only articles from a group, a feed, only flagged
articles, matching a keyword, etc..
- TagCloud of tags applied to articles
- Text analysis feature on the content of articles matching a filter
- Press Review feature allowing to generate an HTML, RSS or PDF page
listing articles and comments matching a filter
- Look and Feel adapted to the Albatross skin by Laurent Lunati !
- Packaged as an XWiki Application (xar) that can run on XWiki 1.1M2 or
later
- French and English User Interface
This release needs some developer skills to be installed. If you are
interested in beta-testing XWiki Watch but don't feel that you can
install XWiki and tweak configuration files, you can send us an email at
marketing(a)xwiki.com to get access to our online beta.
Don't hesitate to send us your feedback with bugs and suggestions. We
manage bugs and new feature requests on JIRA at
http://jira.xwiki.org/jira/browse/XWATCH
Ludovic
--
Ludovic Dubost
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
AIM: nvludo Yahoo: ludovic
On Jun 19, 2007, at 11:49 PM, Ludovic Dubost wrote:
>
> Hi,
>
> I'm beating Vincent by announcing XWiki Watch 1.0M1 before he
> announces XWiki 1.1M2 (which is needed for XWiki Watch 1.0M1).
Well, you "thought" you were beating but mail arrived first here! ;-)
> XWiki Watch 1.0M1 is the first official release and is a functional
> beta.
Congrats for this nice release and all the hard work.
We need to discuss on how to integrate XWiki Watch's release process
into the main dev process for XWiki.
Thanks
-Vincent
>
> XWiki Watch is:
>
> - A collaborative RSS/Atom Feed aggregator
> - Feeds, Groups and Keywords configuration using an AJAX interface.
> Configuration are managed by spaces.
> - Storing of articles themselves in XWiki pages using the
> FeedPlugin's capabilities
> - AJAX UI to navigate articles, open the content
> - Collaborative tagging, commenting and flagging of articles, store
> a 'read' status
> - Filtering UI to see only articles from a group, a feed, only
> flagged articles, matching a keyword, etc..
> - TagCloud of tags applied to articles
> - Text analysis feature on the content of articles matching a filter
> - Press Review feature allowing to generate an HTML, RSS or PDF
> page listing articles and comments matching a filter
> - Look and Feel adapted to the Albatross skin by Laurent Lunati !
> - Packaged as an XWiki Application (xar) that can run on XWiki
> 1.1M2 or later
> - French and English User Interface
>
> This release needs some developer skills to be installed. If you
> are interested in beta-testing XWiki Watch but don't feel that you
> can install XWiki and tweak configuration files, you can send us an
> email at marketing(a)xwiki.com to get access to our online beta.
>
> Don't hesitate to send us your feedback with bugs and suggestions.
> We manage bugs and new feature requests on JIRA at http://
> jira.xwiki.org/jira/browse/XWATCH
>
> Ludovic
The XWiki development team team is pleased to announce the
availability of the 1.1 Milestone 2 release.
Go grab it on http://www.xwiki.org/xwiki/bin/view/Main/Download
Main changes:
* Lots of bugs fixed
* WYSIWYG editor improvements:
o Added new toolbar icon for creating horizontal lines
o Added new toolbar icon for removing all styling on the
selected text
o Make current cell visible when selected in a table
* Improved Photo Album performances
* When deleting a page, first show the list of pages linking to
it and warn about them
* Improved AllDocs page on the default wiki by adding an Index
with A-Z links and added a Treeview tab for showing pages with parent-
children relationships
* The Navigation panel now displays all pages when the logged in
user has Admin rights
* The "Recently Created", "Recently Visited" and "Members"
Panels now only display the last 5 elements
* Added a cancel button to the Rename page
* Added support for the Derby Database and bundled version
10.2.2.0 of Derby
* The Zip Explorer plugin and the AutoTag plugins are now
activated by default in the default configurations
* Added new "Recently Modified Documents" Panel
* New space rights inheritance mechanism
+ lots of other changes.
See the full release notes on http://www.xwiki.org/xwiki/bin/view/
Main/ReleaseNotesXWiki11M2
Enjoy
-The XWiki development team
Hello,
Is there a way to add meta-attributes to a class ? Like
BeforeAfterMetaclasses approaches or hooks.
The underlying use case is to synchronize XWiki objects with a backend
repository.
A typical approach is to have the following attributes automatically changed
or incremented on object change : lastmodificationdate, lastsynchronization,
uptodateSequenceNumber, highwatermark...
Or do you see another way for synchronization ?
Thanks !
Oliver
--
View this message in context: http://www.nabble.com/Changing-BaseClass-to-put-metadatas---tf3946533.html#…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
I think it's time to officially decide if we want to standardize on
1.5. Some reasons we may want to do this:
* JDK 1.4 is old. 1.5 is mainstream. 1.6 is about to be released.
* Most libraries have now switched to 1.5 and it's going to be real
hard to stay on 1.4 if we want to get bug fixes/new features from the
libraries we use
* Radu needs to use some google jars for his GSOC and they seem to
require JDK 1.5
* We already require 1.5 I believe (although it's a light dependency)
and have been requiring 1.5 for now several months (> 5 months) and
we haven't heard complaints from users about this
The vote is about officially dropping support for 1.4 and
standardizing on 1.5 (and thus allowing us to use the new features of
the language too like generics, annotations, etc).
Here's my +1
Please cast your votes.
Thanks
-Vincent
Hi!
I never got an answer to this email. Did I miss a point in some way?
Were my comments not what you guys actually asked for? Maybe I should
add the suggestions and the screenshots to the jira issue XWIKI-523?
Anyway, I'll be offline for a month now, so I won't have the chance to
follow up on the discussion. I hope all you devoted developers also get
the break you want or deserve this summer; you're doing an impressive
job on xwiki!
best regards :-)
Thomas
-------- Original Message --------
Subject: Re: [xwiki-dev] Regarding issue XWIKI-523 (Tags should be shown
with comments and attachments)
Date: Mon, 11 Jun 2007 11:45:28 +0200
From: Thomas Drevon <thomas.drevon(a)intermedia.uio.no>
Reply-To: thomas.drevon(a)intermedia.uio.no
To: xwiki-dev(a)objectweb.org
References: <4665547D.4040408(a)intermedia.uio.no>
<C7BC95C2-AF6F-4F77-94E8-D615340B188C(a)massol.net>
Vincent Massol wrote:
>
> Here's how we could work together: you send some emails on the list,
> maybe with some GUI mockups about how you think tags should be
> integrated. You'll get lots of feedbacks I'm sure, especially if you
> show something in a mockup (people love images ;-)). Then you start
> sending some emails about how you think it should be done and committers
> will comment, tell you if there's a better way. And you can ask for any
> question you have along the way.
>
> WDYT?
Sure! Ok here we go:
1. View tags along with a document. It doesn't really matter what kind
of document, but for this example I've used a blog entry. See the
attached file called blog_entry_view.png. In order to achieve this, just
add the following lines to an appropriate place in XWiki.ArticleClassSheet:
<code>
Tags:
#foreach($tag in $doc.getTagList())
<a href="$xwiki.getURL("Main.Tags", "view", "tag=$tag")")">$tag</a>
#end
</code>
This code is tested and works fine.
Problem: On docs without a template sheet, this gets a bit more messy,
as it seems the above code must be added directly to content.vm. Maybe
all docs should inherit from some sort of generic template sheet? This
will give users more flexibility by sparing them the messing up of
velocity files, and thus making an upgrade of their xwiki version harder.
And by the way, is it correct that while viewing this doc, the
breadcrumbs read "BLOG: Administration > Samarkand" even though I'm not
logged in? "Administration" here seems a bit strange?
2. Intuitive edit of tags while in edit mode. See the attached file
called blog_entry_edit.png. In order to achieve this, add the following
lines to the correct place in XWiki.ArticleClassSheet:
<code>
<dt>Tags:</dt>
<dd><input type="text" id="tags" name="tags" size="60"
value="$!tdoc.tags"/></dd>
</code>
Though this code produces a nice input field as expected, tags entered
here will not be saved along with the doc, unless the servlet engine is
restarted between the creation of the docs and the editing of tags. Strange.
Well, what do you think?
Oh yes, and I'm all for letting users turn on/off the tag functionality
in xwiki.cfg, by the way.
cheers :-)
Thomas
Hi,
Starting from today I'm going to spend some time every week on the V2
Architecture/Redesign. Today I'd like to start at the heart of the
topic with the domain model. Here's my proposal:
* Model classes are classes representing the XWiki model. The main
classes are:
- Farm
- Wiki
- Space
- Document
- XObject
- XClass
- (probably lots of others)
* As you can see I'd like to introduce the Space and Farm objects
* We create a model/ build module in trunks-devs/xwiki/model for
storing model classes
* Model classes cannot access other classes outside of the model/
module. They are meant to be used by components to provide services
but they shouldn't provide services themselves. They can methods to
manipulate their fields and they can call each other but they cannot
call outside of their model.
* We use the org.xwiki.model package for storing Model classes
* These model classes are all user public (API)
WDYT?
Barring any negative feedback I'll start implementing this today and
in the coming days. One question that remains unanswered in my mind
is how do we integrate back these model classes into the V1
architecture. I think we should be able to retrofit the existing
classes to use these classes by composition. For example the Document
object could have 2 fields: one org.xwiki.model.Document and one
org.xwiki.model.Space. The XWiki object could have 2 fields: Wiki and
Farm, etc. I'm not sure how this would work out though. Any idea is
welcome.
Thanks
-Vincent
Hi!
We're experimenting with xmlprc calls to xwiki (using code from
http://www.xwiki.org/xwiki/bin/view/UserGuide/XMLRPCExample), and are
encountering some strange behaviour:
A newly created document will appear directly in xwiki as expected.
However, when we update this newly created doc the database is updated,
but when we view the page in xwiki, we still see the old doc. If a
restart of tomcat is done, the updated doc appears as expected.
It seems as if xwiki is sticking more closely to it's cached verion of
what's in the database than what we would prefer. And it looks very
similar to what I discovered while editing tags on blog entries.
Is this behaviour considered a bug? Is there any code that can be invoke
in order to re-read the object in question from the database?
Once again, any help would be greatly appreciated.
cheers :-)
Thomas