Does XWiki use something like Java Persistence API ?
I cant figure out what Database is being used by the XWiki Enterprise.
--
Thanks and Regards,
Shoubhik Bose
IF I REST, I SHALL RUST.. SO, LETS SHARE THE KNOWLEDGE !
I'm Shoubhik Bose, a 3rd year student( Computer Science and Engineering) at
West Bengal University of Technology.
I wish to work on the " XWiki on Appengine " project.
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/XWikionAppEngineprot…
The project requires me to port the database queries of XWiki to the the
Datastore compliant queries run on the backend of AppEngine.
I have discussed this on the IRC channel already.
My skills:
I have been developing web applications ( JAVA) for a long time now.
I have used Tomcat, Glassfish and Websphere Application Server.
As back-end, I have experience working with Db2, Oracle 10g and MySQL.
Most importantly I have worked on Appengine platform and consider it very
helpful for programmers as one can concentrate on the code.
On the flip-side, porting to different databases require significant changes
in code ( as AppEngine uses Java Persistence API)
Thanks and Regards,
Shoubhik Bose
IF I REST, I SHALL RUST.. SO, LETS SHARE THE KNOWLEDGE !
Hi
I am Supreet and I would like to participate in GSoC-2011. I am mainly
interested in contributing to the project idea "Mobile Skin for XWiki
Enterprise". I have been working on web development for the past two years
and developed a couple of websites. I have a good knowledge of HTML,XHTML
and CSS , I also know PHP and am learning Javascript. If someone could help
me regarding this , I would be really thankful.
Hi Sergiu,
On 04/01/2011 03:53 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2011-04-01 02:53:38 +0200 (Fri, 01 Apr 2011)
> New Revision: 36234
>
> Modified:
> platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/image/ImagePlugin.java
> Log:
> XWIKI-6212: Images not displayed in the administration of xwiki 3.0
> Trying a workaround
>
> Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/image/ImagePlugin.java
> ===================================================================
> --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/image/ImagePlugin.java 2011-03-31 23:39:50 UTC (rev 36233)
> +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/image/ImagePlugin.java 2011-04-01 00:53:38 UTC (rev 36234)
> @@ -202,7 +202,12 @@
> @Override
> public XWikiAttachment downloadAttachment(XWikiAttachment attachment, XWikiContext context)
> {
> - if (!this.imageProcessor.isMimeTypeSupported(attachment.getMimeType(context))) {
> + try {
> + if (!this.imageProcessor.isMimeTypeSupported(attachment.getMimeType(context))) {
> + return attachment;
> + }
> + } catch (NoClassDefFoundError ex) {
> + // Happens on certain systems where the javax.imageio package is not available
I'd like to more the try/catch inside the isMimeTypeSupported method. If
javax.imageio.ImageIO is missing I don't think we can process the image
anyway. WDYT?
Thanks,
Marius
> return attachment;
> }
>
>
> _______________________________________________
> notifications mailing list
> notifications(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/notifications
Hi everyone, I have submit the proposor of GSoC for idea "Auto Completion in
Content Editors", hope you can give me some advice so that I can improve my
proposor, thank you very much.
--
Best wishes,
许凌志(Jame Xu)
MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University
Department of Computer Science and Technology, Xi’an Jiaotong University
fyi
-Vincent
Begin forwarded message:
> From: Grant Ingersoll <gsingers(a)apache.org>
> Date: March 31, 2011 8:46:04 PM GMT+02:00
> To: announce(a)apache.org, java-user(a)lucene.apache.org, general list <general(a)lucene.apache.org>, dev(a)lucene.apache.org
> Subject: Apache Lucene 3.1.0
>
> March 2011, Apache Lucene 3.1 available
> The Lucene PMC is pleased to announce the release of Apache Lucene 3.1.
>
> This release contains numerous bug fixes, optimizations, and
> improvements, some of which are highlighted below. The release
> is available for immediate download at http://www.apache.org/dyn/closer.cgi/lucene/java (see note below).
> See the CHANGES.txt
> file included with the release for a full list of details.
>
> Lucene 3.1 Release Highlights
>
> * Numerous performance improvements: faster exact PhraseQuery; merging
> favors segments with deletions; primary key lookup is faster;
> IndexWriter.addIndexes(Directory[]) uses file copy instead of
> merging; various Directory performance improvements; compound file
> is dynamically turned off for large segments; fully deleted segments
> are dropped on commit; faster snowball analyzers (in contrib);
> ConcurrentMergeScheduler is more careful about setting priority of
> merge threads.
>
> * ReusableAnalyzerBase makes it easier to reuse TokenStreams
> correctly.
>
> * Improved Analysis capabilities: Improved Unicode support, including
> Unicode 4, more friendly term handling (CharTermAttribute), easier
> object reuse and better support for protected words in lossy token
> filters (e.g. stemmers).
>
> * ConstantScoreQuery now allows directly wrapping a Query.
>
> * IndexWriter is now configured with a new separate builder API,
> IndexWriterConfig. You can now control IndexWriter's previously
> fixed internal thread limit by calling setMaxThreadStates.
>
> * IndexWriter.getReader is replaced by IndexReader.open(IndexWriter).
> In addition you can now specify whether deletes should be resolved
> when you open an NRT reader.
>
> * MultiSearcher is deprecated; ParallelMultiSearcher has been
> absorbed directly into IndexSearcher.
>
> * On 64bit Windows and Solaris JVMs, MMapDirectory is now the
> default implementation (returned by FSDirectory.open).
> MMapDirectory also enables unmapping if the JVM supports it.
>
> * New TotalHitCountCollector just counts total number of hits.
>
> * ReaderFinishedListener API enables external caches to evict entries
> once a segment is finished.
>
> Note: The Apache Software Foundation uses an extensive mirroring network for distributing releases. It is possible that the mirror you are using may not have replicated the release yet. If that is the case, please try another mirror. This also goes for Maven access.
>
> --------------------------
> Grant Ingersoll
> Lucene Revolution -- Lucene and Solr User Conference
> May 25-26 in San Francisco
> www.lucenerevolution.org
>
fyi. At some point we'll need to use some search fwk that sits on top of Lucene.
-Vincent
Begin forwarded message:
> From: Grant Ingersoll <gsingers(a)apache.org>
> Date: March 31, 2011 8:45:18 PM GMT+02:00
> To: announce(a)apache.org, dev(a)lucene.apache.org, solr-user(a)lucene.apache.org, general list <general(a)lucene.apache.org>
> Subject: Apache Solr 3.1.0
>
> March 2011, Apache Solr 3.1 available
>
> The Lucene PMC is pleased to announce the release of Apache Solr 3.1.
>
> This release contains numerous bug fixes, optimizations, and
> improvements, some of which are highlighted below. The release is
> available for immediate download at http://www.apache.org/dyn/closer.cgi/lucene/solr (see note below).
> See the CHANGES.txt file included with the release for a full list of
> details as well as instructions on upgrading.
>
> What's in a Version?
>
> The version number for Solr 3.1 was chosen to reflect the merge of
> development with Lucene, which is currently also on 3.1. Going
> forward, we expect the Solr version to be the same as the Lucene
> version. Solr 3.1 contains Lucene 3.1 and is the release after Solr 1.4.1.
>
> Solr 3.1 Release Highlights
>
> * Numeric range facets (similar to date faceting).
>
> * New spatial search, including spatial filtering, boosting and sorting capabilities.
>
> * Example Velocity driven search UI at http://localhost:8983/solr/browse
>
> * A new termvector-based highlighter
>
> * Extend dismax (edismax) query parser which addresses some
> missing features in the dismax query parser along with some
> extensions.
>
> * Several more components now support distributed mode:
> TermsComponent, SpellCheckComponent.
>
> * A new Auto Suggest component.
>
> * Ability to sort by functions.
>
> * JSON document indexing
>
> * CSV response format
>
> * Apache UIMA integration for metadata extraction
>
> * Leverages Lucene 3.1 and it's inherent optimizations and bug fixes
> as well as new analysis capabilities.
>
> * Numerous improvements, bug fixes, and optimizations.
>
> Note: The Apache Software Foundation uses an extensive mirroring network for distributing releases. It is possible that the mirror you are using may not have replicated the release yet. If that is the case, please try another mirror. This also goes for Maven access.
Hi devs,
I'd like to propose to deprecate the "value" and "hints" fields of @Component and instead use the @Named annotation (and @Qualifier annotations later on).
The rationale is to align with JSR330's @Named annotation at injection points and also to start going in the direction of CDI (JSR299) since CDI uses @Named for beans too.
Example before:
@Component("hint")
public class MyComponent...
After:
@Component
@Named("hint")
public class MyComponent
Here's my +1
Thanks
-Vincent