On 2015-02-19 10:15, Stefan Thieme wrote:
Gesendet: Mittwoch, 18. Februar 2015 um 16:51 Uhr
Von: Julian Reschke julian.resc...@gmx.de
An: Stefan Thieme stefan.thi...@gmx.ch
Cc: oak-dev@jackrabbit.apache.org
Betreff: Re: Aw: Re: [PATCH] [OAK-1914] RDB: Oracle support
On 2015-02-18 16:07, Stefan
Gesendet: Mittwoch, 18. Februar 2015 um 16:51 Uhr
Von: Julian Reschke julian.resc...@gmx.de
An: Stefan Thieme stefan.thi...@gmx.ch
Cc: oak-dev@jackrabbit.apache.org
Betreff: Re: Aw: Re: [PATCH] [OAK-1914] RDB: Oracle support
On 2015-02-18 16:07, Stefan Thieme wrote:
(resend as text mail)
Dear
Hi,
On 18/02/15 16:51, Julian Reschke julian.resc...@gmx.de wrote:
b) MAX_ID_VALUE=; in NodeDocument triggers a SQL Error on Oracle DB,
changing to MAX_ID_VALUE=a as in ClusterNodeInfoDocument.
I understand that ; is an ASCII char just above digits 0-9, IMHO even
: would suffice for this
Hi,
I'd like to create an Oak 1.0.12 release early next week with a few
important fixes that were implemented since 1.0.11.
We also have the RDB support for the DocumentMK back-ported to the 1.0
branch. @Julian, as far as I see this is finished, right?
Please reschedule issues currently set to
On 2015-02-19 06:11, Chetan Mehrotra wrote:
Hi Tommaso,
On Wed, Feb 18, 2015 at 10:42 PM, tomm...@apache.org wrote:
+} else {
+if (log.isWarnEnabled()) {
+log.warn(cannot create Solr query index as SolrServer {}Â is
unreachable, solrServer);
+
thanks guys.
@Chetan right, it's on my todo list to remove such guards soon, as I had
already realized it's not much helpful in most of the cases.
@Julian I'll look for the non ASCII char (no idea how it got into the
commit though...).
Regards,
Tommaso
2015-02-19 11:30 GMT+01:00 Julian Reschke
On 2015-02-19 22:19, Marcel Reutegger wrote:
Hi,
I'd like to create an Oak 1.0.12 release early next week with a few
important fixes that were implemented since 1.0.11.
We also have the RDB support for the DocumentMK back-ported to the 1.0
branch. @Julian, as far as I see this is finished,
Hi devs,
I'm using the following code snippet to update the content of a node:
vm.checkout(fileNode.getPath());
Binary binary = session.getValueFactory().createBinary(new
ByteArrayInputStream(data));
content.setProperty(jcr:data, binary);
session.save();
Version newVersion =
I’ve come up with something unexpected, and would like some clarification.
I’ve registered an event listener for property changes on nodes that are
mix:versionable. As expected, an event is fired whenever a node with property
changes is saved. However, the event frequently fires before the
