luck for the finals!
When you're back in business, you may want to take a look at the new
servlet classes in jackrabbit-servlet. See my response to Pavel for
more details.
BR,
Jukka Zitting
Hi,
On 6/6/07, Christophe Lombart <[EMAIL PROTECTED]> wrote:
On 6/6/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> All the above components pass at least my informal code and design quality
> metrics for inclusion in Jackrabbit releases.
I'm very interesting to have more
e.SearchIndex) ignores the
virtual filesystem configuration and always stores the index in the
local filesystem for performance reasons.
BR,
Jukka Zitting
Hi,
On 6/4/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Jackrabbit 1.3.1 will be a patch release with selected bug fixes from
the svn trunk. No features or other improvements will be included in
1.3.1. I will soon start grooming the issue tracker for the release
and merging the selected
esume. :-)
[1] http://www.apache.org/dev/pmc.html#chair
BR,
Jukka Zitting
s more important?
Agreed. I think we can (at least for now) focus on a local client as
the SPI work is already trying to solve the remote access and batching
mechanisms. I guess we eventually need to produce some sort of
synthesis of SPI and NGP (or another future persistence architecture),
but I guess that would be something for Jackrabbit 4.0 or 5.0...
BR,
Jukka Zitting
should we just start pinging other projects to gauge interest?
BR,
Jukka Zitting
The blob is then turned into a BLOBFileValue that
automatically spools the binary stream into a local temporary file.
:-(
This is one of the problems I'm trying to address with JCR-926.
BR,
Jukka Zitting
UTF-8
and for retrieving the encoded string value in case it is. It should
be easy to do the UTF-8 validation with almost zero overhead while the
binary stream is being imported.
Together with the above inline mechanism we should in fact be able to
make no distinction between binary and string values i
ects cases
where you have blobs stored in the database instead of the local file
system.
BR,
Jukka Zitting
we can release the feature. Such tools will be very useful also
for number of other purposes, but it is not yet clear when we will
have them.
BR,
Jukka Zitting
lValueLong and so on. And/or use a cache for the most commonly
used objects (integer 0-1000, empty String, boolean true/false).
+1
But that's another discussion.
Let's follow up on taht. :-)
BR,
Jukka Zitting
nting the
Global Data Store.
Thanks. I'll upload my latest code in JCR-926.
BR,
Jukka Zitting
ere each
workspace and the versioning store have their own independent backend
stores. It would be interesting to explore how far we can go with
incremental changes.
BR,
Jukka Zitting
Hi,
Anyone fancying a trip to Hong Kong? See below for an opportunity to
present Jackrabbit and JCR in OS Summit Asia 2007.
BR,
Jukka Zitting
Call for Papers Opens for OS Summit Asia 2007
The call for papers is now open for OS Summit Asia, to be held
November
it and Lucene, but it would be nice to see what we could
achieve in case there's interest within both projects.
BR,
Jukka Zitting
mplementing the changes and
new features required to make Jackrabbit 2.0 the reference
implementation of JSR 283.
----
BR,
Jukka Zitting
sactions and all. The hard part is getting to
that state without a major revolution in Jackrabbit internals, so I
quite like your line of thinking in that it seems to offer a more
evolutionary path towards that goal. :-)
BR,
Jukka Zitting
elease?
It would be nice to have OCM included in our Continuum installation at
http://jackrabbit.zones.apache.org/. Do you mind if I do the required
POM updates (mostly entries)?
BR,
Jukka Zitting
of stateless operations to be applied
on those resources. Such an approach is very "web-friendly".
BR,
Jukka Zitting
Hi,
On 6/20/07, Christophe Lombart <[EMAIL PROTECTED]> wrote:
On 6/20/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> Do you want to make a standalone OCM release,
> or should we include it as a component in the Jackrabbit 1.4 release?
It should nice to see it as a component
y wait at least until Jackrabbit 2.0 before we
take that road, but it's certainly possible to do isolated component
releases already before that.
BR,
Jukka Zitting
e current
set of constraints available in Jackrabbit is somewhat limited, but
that's a good case for filing improvement requests instead of
implementing extra constraints in application code.
BR,
Jukka Zitting
ike it could be a problem in how same name siblings are
handled in NodeState. If this is the case and someone can further
qualify the issue and fix it in a short timeframe, I would very much
like to have the fix included in 1.3.1.
BR,
Jukka Zitting
at the jcr:deref()
mechanism available in XPath.
BR,
Jukka Zitting
pache.org/mod_mbox/incubator-graffito-dev/200702.mbox/[EMAIL
PROTECTED]
BR,
Jukka Zitting
nology preview".
See http://jackrabbit.apache.org/doc/building.html for instructions on
how to checkout and build the svn trunk.
BR,
Jukka Zitting
nted, but even having the
feedback in the first place is very important and healthy for the
project. Such feedback is IMHO much more important in driving the
project than architectural visions of how things should be.
[1] blue line in http://people.apache.org/~coar/users_jackrabbit_apache_org.png
BR,
Jukka Zitting
what the incorrect line is.
Moreover, this really doesn't look like a Jackrabbit issue as your
stack traces contain no org.apache.jackrabbit classes. I suspect you
simply have an error in your code. Check out what you have on line 171
and trace back all the references used on that line.
BR,
return queryResultNodeIterator.nextNode();
} else {
throw new BlogEntryNotFoundException();
}
BR,
Jukka Zitting
like this (AFAIK
concurrent normal workspace access doesn't interfere with versioning):
synchronized (repository) {
// versioning operations
}
It would be very nice if we could drop those synchronization block.
BR,
Jukka Zitting
Hi,
On 6/25/07, Jukka Zitting (JIRA) <[EMAIL PROTECTED]> wrote:
Jukka Zitting updated JCR-18:
-
Comment: was deleted
Hmm, that isn't very descriptive... To anyone who's wondering, I
removed a confusingly self-referencing comment "This issue
Hi,
On 6/25/07, Marcel Reutegger <[EMAIL PROTECTED]> wrote:
Jukka Zitting wrote:
> What's the general feeling about concurrent versioning? Do we have
> light at the end of the tunnel? I guess reviewing whether JCR-18 is
> still relevant would make sense
I'm currently
ks for the reminder. I'll get it set up in Continuum so we'll get
snapshots automatically deployed to the snapshot repository.
BR,
Jukka Zitting
Hi,
On 6/27/07, [EMAIL PROTECTED] wrote:
will [JCR-929] be included in 1.3.1 ?
Not yet decided, as I'm not sure how risky the change is. Dominique,
what do you think?
BR,
Jukka Zitting
ory or something like
that) with the Jira installation earlier today. After a restart things
are apparently OK.
BR,
Jukka Zitting
definitely be a good reason
for doing a press release, but I'm wondering if we should also do a
press release for Jackrabbit 1.4 later this year. It seems like 1.4 is
becoming our coolest release since Jackrabbit 1.0 and the timing would
coincide nicely with ApacheCon US.
WDYT?
BR,
Jukka Zitting
e my point of
view, whether you want it or not ;)
Your feedback is definitely very valuable! In fact I value it equally
or even more than input from the same frame of reference that I come
from. Diversity of opinions and needs is vital for growing and
sustaining a vibrant open source community.
BR,
Jukka Zitting
oys or girls! :-)
BR,
Jukka Zitting
n that was
guaranteed to be backwards compatible was the repository home
directory. :-)
I guess even if we do nothing else about this it would still be good
to keep in mind that the internal interfaces we have now are nothing
more than internal design decisions that may or many not be valid
anymore.
hard, it is also hard to change the interfaces that are being
configured.
I think you are right in raising the configuration model as a key question.
BR,
Jukka Zitting
Hi,
On 6/27/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
On 6/27/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Jukka, how about adding the OCM to the Jackrabbit continuum ?
Thanks for the reminder. I'll get it set up in Continuum so we'll get
snapshots auto
onent.
BR,
Jukka Zitting
nt in case it already shows a marked performance improvement
over JCR RMI.
BR,
Jukka Zitting
ry. :-)
BR,
Jukka Zitting
i" idea withdrawn until I come up with a more convincing
rationale or roadmap in a separate thread.
BR,
Jukka Zitting
y entering the Apache
Incubator, see http://wiki.apache.org/incubator/JrsProposal.
BR,
Jukka Zitting
Hi,
On 7/13/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
On 7/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Log:
> JCR-848: javacc-maven-plugin version in jackrabbit-core pom file
> [...]
> SKIP : {
> - <<_WHITESPACE>>
> + < <_WHITESPA
Hi,
On 7/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Log:
JCR-848: javacc-maven-plugin version in jackrabbit-core pom file
[...]
SKIP : {
- <<_WHITESPACE>>
+ < <_WHITESPACE>>
}
Weird, incorrect syntax?
BR,
Jukka Zitting
Hi,
On 7/13/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
I've added SPI in our Continuum setup at
http://jackrabbit.zones.apache.org/continuum/. I'm still not totally
sure about the email notification setup, but at least the setup will
now automatically deploy the latest SPI a
tory/.
BR,
Jukka Zitting
e the latest patch a look and get back to you on the best way forward.
BR,
Jukka Zitting
are cast.
[ ] +1 Release the packages as Apache Jackrabbit 1.3.1
[ ] -1 Do not release the packages because...
Here's my +1, compiled and tested on Ubuntu Linux with Java 5 and on
Windows XP with Java 6.
BR,
Jukka Zitting
Hi,
On 7/21/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Please vote on releasing these packages as Apache Jackrabbit 1.3.1.
Thanks to Alexandre and Bertrand for voting! However, we still need
two +1 votes from Jackrabbit PMC members to put the release out. I
guess quite a few are on va
functionality on the SPI implementation side, it might be necessary to
push that functionality down to spi-commons.
WDYT?
BR,
Jukka Zitting
team!
BR,
Jukka Zitting
Hi,
On 7/27/07, Julian Reschke <[EMAIL PROTECTED]> wrote:
> Jukka Zitting wrote:
> > People have been asking about the recent unstability of the ASF Jira.
> > It seems like the culprit is some external client that keeps
> > requesting huge query results. The infra
, which should restore things back to normal.
BR,
Jukka Zitting
ug fix. I try to put only bug fixes in
patch releases, so JCR-889 is scheduled for the 1.4 release.
BR,
Jukka Zitting
duction environments, but I wouldn't
recommend going that far.
BR,
Jukka Zitting
ing to act
strangely. The latest news on infrastructure@ is that the Jira
installation should get upgraded tomorrow, after which things will
hopefully return to normal.
BR,
Jukka Zitting
le JCR-367) but those fixes were never applied to the test cases.
I don't have a Mac to play with so I can't dig deeper.
If my reasoning is correct, I would treat the issue as a test case bug
to be fixed in a future release, and not a blocker to 1.3.1.
BR,
Jukka Zitting
ve to wait a while (unless someone wants to take over managing
the release).
BR,
Jukka Zitting
Hi,
On 7/21/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> Please vote on releasing these packages as Apache Jackrabbit 1.3.1.
The vote passes with the following votes (* is member of the Jackrabbit PMC):
+1 Jukka Zitting (*)
+1 Alexandre Martins
+1 Bertrand Delacretaz
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit version 1.3.1. The release is available for download
at:
http://jackrabbit.apache.org/downloads.cgi
Release Notes -- Apache Jackrabbit -- Version 1.3.1
Introduction
Apache Jackrabbit is a fu
would lessen the categorization metadata on
jackrabbit-core issues but increase metadata on other components. If
we want to keep the finer granularity, we could use an prefix
mechanism like core:query, core:xml, etc.
BR,
Jukka Zitting
contrib
contrib PMs
jackrabbit-api
Jackrabbi
stuff to figure
out, but otherwise I think this would be the cleanest approach.
BR,
Jukka Zitting
focusing on the real JCR 2.0 interfaces for
the Jackrabbit 2.0 release.
BR,
Jukka Zitting
ke nobody being able to review too big release candidates)
gets too big.
BR,
Jukka Zitting
way we would
keep a simple mapping between releases and Jira projects.
BR,
Jukka Zitting
compatible changes in the 1.4
release, and Jackrabbit 2.0 will most likely require a more complex
upgrade process, so we do have a few good windows of opportunity
coming up for reindexing or other such changes.
BR,
Jukka Zitting
dentation.
> In fact, AFAIK, Jackrabbit does not have any nested projects (any more),
> right ?
Only in contrib. All the release subprojects are directly below trunk.
BR,
Jukka Zitting
something like that could
be implemented already now as a Jackrabbit-specific extension?
It would be nice if we had a patch that implements this in current
Jackrabbit so we could see how useful it is in practice before
including it in the spec.
BR,
Jukka Zitting
Hi,
On 8/16/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
> On 8/16/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> > Have you considered how something like that could
> > be implemented already now as a Jackrabbit-specific extension?...
>
> One idea (
Hi,
On 8/16/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Am Donnerstag, den 16.08.2007, 15:01 +0300 schrieb Jukka Zitting:
> > For now I'd just put the extra methods directly on the SessionImpl and
> > EventImpl classes. We can formalize them in a jackrabbit-api
don't want Jackrabbit using a database, I want Jackrabbit *being*
the database!
BR,
Jukka Zitting
cases.
How is the total size question typically solved in cases where an
application pages through a large database result set? I recall
sometimes using a separate COUNT(*) query for that, but there may be
more efficient alternatives.
BR,
Jukka Zitting
,
Jukka Zitting
, I don't want us in a
situation where we need to change the whole underlying architecture to
reach real performance gains.
BR,
Jukka Zitting
a solution that didn't require explicit synchronization.
BR,
Jukka Zitting
}
} finally {
connection.close();
}
}
Any reasonable connection pool will pool also the prepared statements,
so the above code would normally only require an extra hash lookup and
some bookkeeping overhead.
BR,
Jukka Zitting
> needs to be tested.
At least commons-dbcp (what I'm most familiar with) returns a prepared
statement back to a pool (instead of really closing it) when the
close() method is called.
BR,
Jukka Zitting
ink the correct behaviour would be for the node iterator to throw
an exception (unfortunately I guess only a RuntimeException would work
here) instead of ignoring such internal errors.
BR,
Jukka Zitting
mething we may want to take up in JSR 283, perhaps
even going as far as adding a RepositoryException to nextNode()...
BR,
Jukka Zitting
g
[2] http://wiki.apache.org/jackrabbit/SlingProposal
[3]
http://incubator.apache.org/incubation/Incubation_Policy.html#Entry+to+Incubation
[4] http://incubator.apache.org/incubation/Incubation_Policy.html
[5]
http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Sponsor
BR,
Juk
Hi,
On 8/27/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> As described in [3], I'd like to call the Jackrabbit PMC to vote on
> sponsoring the Sling project and approving it for incubation. The vote
> is open for the next 72 hours and only votes from the Jackrabbit PMC
> m
Hi,
On 8/24/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> On 8/22/07, Martijn Hendriks <[EMAIL PROTECTED]> wrote:
> > The current implementation of the LazyScoreNodeIterator is such to
> > ignore all RepositoryExceptions that might be thrown while loading the
>
o the Apache Incubator. Assuming no
objections are raised, I believe this will happen by the end of the
week. I'll follow up with more details about your account request
then.
BR,
Jukka Zitting
Hi,
Just came across this:
http://jackrabbit.scalableinformatics.com/
Not sure yet what, if anything, to do about it.
BR,
Jukka Zitting
Hi,
On 8/29/07, Stefan Guggisberg <[EMAIL PROTECTED]> wrote:
> On 8/28/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> > A thought just crossed my mind... As mentioned in another thread a few
> > days ago, we could make NodeImpl to load the underlying node states
>
y retrieve the child node states when performing calls like
Node.getNodes() or Node.getNodes(Strin pattern).
BR,
Jukka Zitting
e node = sessionA.getRootNode().getNode("path/to/node");
sessionB.getRootNode().getNode("path/to/node").remove();
sessionB.save();
node.getProperty(...);
BR,
Jukka Zitting
bug in the search index
update code for deleting entries? Something like that could easily
have been ignored so far if the only effect is a warning in the log
due to the current approach of simply dropping the results for which
an exception is thrown.
BR,
Jukka Zitting
Hi,
On 8/27/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> As described in [3], I'd like to call the Jackrabbit PMC to vote on
> sponsoring the Sling project and approving it for incubation. The vote
> is open for the next 72 hours and only votes from the Jackrabbit PMC
> m
Hi,
On 9/8/07, Jukka Zitting (JIRA) <[EMAIL PROTECTED]> wrote:
> Jukka Zitting updated JCR-940:
> --
> Comment: was deleted
Sorry for the noise. Deleted all the autoresponder spam from the issue
to keep it browseable.
BR,
Jukka Zitting
revious message, but
I've been quite busy travelling the last few days so I didn't yet have
time to respond.
BR,
Jukka Zitting
sts. I don't know how we can
> avoid this situation. still thinking about that ...
Something like jackrabbit-jcr-tests? Or simply you put all mapper
implementations inside the core project as suggested above.
BR,
Jukka Zitting
Hi,
On 9/11/07, Christophe Lombart <[EMAIL PROTECTED]> wrote:
> > Sounds good. Would you mind doing JCR-995 (moving the core part
> > outside contrib) as well while you're at it?
>
> I would like to finalise the annotation support before moving outside the
> contrib. Just to be sure to have someth
in to Confluence also for the less official Jackrabbit wiki
where everyone has edit rights.
BR,
Jukka Zitting
within an IDE as well.
BR,
Jukka Zitting
501 - 600 of 2039 matches
Mail list logo
