Help: Sometimes jackrabbit don't found jcr node by identifier

[Daniele Cherchi <da...@gmail.com>]

Hi, I use jackrabbit 2.1.1 and mysql. Sometime i have a problem when i get a
node by node identifier. In my application i saved on my table the
identifier of jcr node to rapid extraction without long search. This nodes
are my particular documents node.
The nodes exist on DB, and if i manualy search I found it, but if i get the
nodes with the specific function,  sometime this node don't found and
sometimes yes....

Where is the problem? Is lucene the problem? Is node identifier a strong
solution to get always the nodes?

Help please
Thanks
Daniele

Re: Help: Sometimes jackrabbit don't found jcr node by identifier

[Daniele Cherchi <da...@gmail.com>]

Hi, yes i used Session.getNodeByIdentifier(), but now it's work correctly...
I'm trying to reply the error, and I'll post logs asap.

I hope that the cause of error is that I run my application (dynamic web
project) by eclipse's tomcat. Sometimes it hasn't automatic refreshing of
project's data

Thank you
Daniele



2010/10/21 Jukka Zitting <ju...@gmail.com>

> Hi,
>
> On Thu, Oct 21, 2010 at 1:34 AM, Daniele Cherchi <da...@gmail.com>
> wrote:
> > Where is the problem? Is lucene the problem? Is node identifier a strong
> > solution to get always the nodes?
>
> You're using Session.getNodeByIdentifier(), right? Its implementation
> is no tied to the search index, and it should always give you the node
> you're looking for as long as the node actually exists. If not, it's a
> bug in either Jackrabbit or your code.
>
> Can you reproduce the problem with a simple test case?
>
> BR,
>
> Jukka Zitting
>

Re: Help: Sometimes jackrabbit don't found jcr node by identifier

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Thu, Oct 21, 2010 at 1:34 AM, Daniele Cherchi <da...@gmail.com> wrote:
> Where is the problem? Is lucene the problem? Is node identifier a strong
> solution to get always the nodes?

You're using Session.getNodeByIdentifier(), right? Its implementation
is no tied to the search index, and it should always give you the node
you're looking for as long as the node actually exists. If not, it's a
bug in either Jackrabbit or your code.

Can you reproduce the problem with a simple test case?

BR,

Jukka Zitting