You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Roy Russo <ro...@jboss.com> on 2005/06/07 03:54:30 UTC
ORM-based persistence contrib build problems
Hi all,
I'm experiencing a problem trying to get the orm-persistence sources in
/contrib to build on 'maven clean'. Its failing on trying to retrieve
jackrabbit jar from day software:
Attempting to download jackrabbit-0.16.4-dev.jar.
Error retrieving artifact from
[http://www.day.com/maven/jackrabbit/jars/jackrabbit-0.16.4-dev.jar]:
java.io.IOException: Forbidden.
WARNING: Failed to download jackrabbit-0.16.4-dev.jar.
Obviously, I have this locally after building the parent project, but do
not know how to point maven to use that instead.
Regards,
Roy Russo
Jboss Portal Developer
Re: Workspace name and code was: ORM-based persistence contrib build problems
Posted by Stefan Guggisberg <st...@gmail.com>.
On 6/10/05, Serge Huber <sh...@jahia.com> wrote:
> Edgar Poce wrote:
>
> >>I noticed that in your JDBC implementation you chose to map workspaces
> >>to databases. What do you think is better between that and using an
> >>extra workspace column ?
> >>
> >>
> >I still had no time to make the changes, but I'll use a single db for
> >al the workspaces. If each workspace is mapped to a db, on workspace
> >creation the PM should create a new db.
> >
> >
> Hmm... I'm having another problem now. You suggested the use of a param
> to set the name of the workspace. From the PM, how do I access this ? In
> the PMContext class I only have accessors to things like the HomeDir,
> FileSystem, NameSpaceRegistry, NodeTypeRegistry and RootNodeUUID. I
> didn't see anything related to parameters. Has this been removed in the
> current code ? Or are the settings set through setter and reflection API ?
the latter...
>
> Regards,
> Serge Huber.
>
>
Re: Workspace name and code was: ORM-based persistence contrib build
problems
Posted by Serge Huber <sh...@jahia.com>.
Hi all,
Still thinking about this implementation, I think I found a small
limitation in the current implementation. If I create a "code" for a
workspace name, and let's say a new workspace is created using the
Workspace.createWorkspace or Session.createWorkspace methods, I will
then associate a new code with the new workspace. Up to there all is
fine. Now it seems that Jackrabbit does not (yet?) manage the full
lifecycle of workspaces, or I haven't been able to find methods that
delete workspaces. The problem is that the PM should be notified of
this, otherwise there will be left-over data in the back-end. As far as
I could tell this problem would also arise with Filesystem-based PMs.
For the moment, if I understand this correctly, in the default
implementation and configuration, new workspaces will be created in the
repository/ directory. When using FS-based implementation, deleting a
workspace is trivial, you could simply shutdown Jackrabbit, delete the
workspace directory and all would be well (from what I read we might
also be able to "dispose" of a workspace, but I don't know if this is
correct) and then remove the files. Of course this is a bit manual and
not ideal for scenarios where the repository must have good uptimes.
In the case of a "disconnected" back-end such as a database, this
operation has to be done through the PM.
I should emphasis that I know this is not part of JCR, I'm only looking
at this from a Jackrabbit point of view. The other interim solution
would simply to let the data rot in the DB, in a disconnected state, but
that's not ideal either. The one nice thing about using different
database schemas mapped to workspaces is that disposing of a workspace
is easily done by a DB admin, but there is no SQL standard for managing
schemas.
Any corrections/input on this would be more than welcome !
Regards,
Serge Huber.
Edgar Poce wrote:
>>Hmm... I'm having another problem now. You suggested the use of a param
>>to set the name of the workspace. From the PM, how do I access this ? In
>>the PMContext class I only have accessors to things like the HomeDir,
>>FileSystem, NameSpaceRegistry, NodeTypeRegistry and RootNodeUUID. I
>>didn't see anything related to parameters. Has this been removed in the
>>current code ? Or are the settings set through setter and reflection API ?
>>
>>
>It uses javabean convention, see
>http://incubator.apache.org/jackrabbit/apidocs/index.html
>
>BR,
>edgar
>
>
>>Regards,
>> Serge Huber.
>>
>>
>>
>>
>
>
>
Re: Workspace name and code was: ORM-based persistence contrib build problems
Posted by Edgar Poce <ed...@gmail.com>.
> Hmm... I'm having another problem now. You suggested the use of a param
> to set the name of the workspace. From the PM, how do I access this ? In
> the PMContext class I only have accessors to things like the HomeDir,
> FileSystem, NameSpaceRegistry, NodeTypeRegistry and RootNodeUUID. I
> didn't see anything related to parameters. Has this been removed in the
> current code ? Or are the settings set through setter and reflection API ?
It uses javabean convention, see
http://incubator.apache.org/jackrabbit/apidocs/index.html
BR,
edgar
>
> Regards,
> Serge Huber.
>
>
Re: Workspace name and code was: ORM-based persistence contrib build
problems
Posted by Serge Huber <sh...@jahia.com>.
Edgar Poce wrote:
>>I noticed that in your JDBC implementation you chose to map workspaces
>>to databases. What do you think is better between that and using an
>>extra workspace column ?
>>
>>
>I still had no time to make the changes, but I'll use a single db for
>al the workspaces. If each workspace is mapped to a db, on workspace
>creation the PM should create a new db.
>
>
Hmm... I'm having another problem now. You suggested the use of a param
to set the name of the workspace. From the PM, how do I access this ? In
the PMContext class I only have accessors to things like the HomeDir,
FileSystem, NameSpaceRegistry, NodeTypeRegistry and RootNodeUUID. I
didn't see anything related to parameters. Has this been removed in the
current code ? Or are the settings set through setter and reflection API ?
Regards,
Serge Huber.
Re: ORM-based persistence contrib build problems
Posted by Edgar Poce <ed...@gmail.com>.
On 6/10/05, Serge Huber <sh...@jahia.com> wrote:
> On another point : am I right assuming that there is one instance of a
> PM for every workspace, or did I understand it wrong ?
AFAIK you are right.
>
> I noticed that in your JDBC implementation you chose to map workspaces
> to databases. What do you think is better between that and using an
> extra workspace column ?
I still had no time to make the changes, but I'll use a single db for
al the workspaces. If each workspace is mapped to a db, on workspace
creation the PM should create a new db.
>
> Regards,
> Serge Huber.
>
Re: ORM-based persistence contrib build problems
Posted by Serge Huber <sh...@jahia.com>.
Hi Edgar,
Thanks for the resource.
On another point : am I right assuming that there is one instance of a
PM for every workspace, or did I understand it wrong ?
I noticed that in your JDBC implementation you chose to map workspaces
to databases. What do you think is better between that and using an
extra workspace column ?
Regards,
Serge Huber.
Edgar Poce wrote:
>Hi serge
>
>I guess both frameworks provide a mechanism to assign unique values
>for primary keys. see
>http://db.apache.org/ojb/docu/guides/sequencemanager.html.
>
>BR,
>edgar
>
>On 6/10/05, Serge Huber <sh...@jahia.com> wrote:
>
>
>>Hi Edgar,
>>
>>Do you have any suggestions onto the format of the code ? Some UUID of
>>some sort ?
>>
>>Regards,
>> Serge Huber.
>>
>>Edgar Poce wrote:
>>
>>
>>
>>>Hi Serge
>>>
>>>On 6/9/05, Serge Huber <sh...@jahia.com> wrote:
>>>
>>>
>>>
>>>
>>>>I didn't have time yesterday to look at the problems. I submitted a
>>>>quick patch in order for everything to compile, and noticed the test
>>>>failures but didn't have the time to investigate further. Would you be
>>>>able to sum up the required changes in order to support this ? Does this
>>>>mean that each node/property needs an extra workspace name column ?
>>>>
>>>>
>>>>
>>>>
>>>Just a thought. Given that all the workspaces share the uuid of the
>>>root node, I think that every table needs an extra column. I'd use a
>>>code rather than the workspace name. When initialized the PM should
>>>get or create (if necessary) the code for the given workspace from a
>>>table or from the FS.
>>>The workspace name can be passed to the PM through config, e.g. <param
>>>name="name" value="${wsp.name}"/>
>>>
>>>BR,
>>>edgar
>>>
>>>
>>>
>>>
>>>
>>>>Regards,
>>>> Serge Huber.
>>>>
>>>>Edgar Poce wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Hi serge
>>>>>
>>>>>I gave a try to the orm PM and found that it stores the data
>>>>>disregarding the workspace name, which means that the data stored in
>>>>>one workspace is accessible from any other.
>>>>>IMHO we should wait to commit the changes until this problem is
>>>>>solved and both PMs, hibernate and OJB, pass all the tests. WDYT?
>>>>>
>>>>>BR,
>>>>>edgar
>>>>>
>>>>>if you want to reproduce the error run the following code, it will
>>>>>fail the second time.
>>>>>
>>>>>String newNodeName = "ormtest" ;
>>>>>// Default workspace
>>>>>Session defaultSession = helper.getReadWriteSession("default") ;
>>>>>Node defaultRoot = defaultSession.getRootNode() ;
>>>>>assertFalse(defaultRoot.hasNode(newNodeName));
>>>>>defaultSession.logout() ;
>>>>>
>>>>>// Add a new node in workspace test
>>>>>Session testSession = helper.getReadWriteSession("test") ;
>>>>>Node testRoot = testSession.getRootNode() ;
>>>>>testRoot.addNode(newNodeName) ;
>>>>>testSession.save() ;
>>>>>testSession.logout() ;
>>>>>
>>>>>
>>>>>Serge Huber wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Ok I've done a quick patch to allow for compilation of the
>>>>>>contribution. Thank you for committing it as soon as possible. You
>>>>>>can find it as an attachement to issue :
>>>>>>http://issues.apache.org/jira/browse/JCR-129$
>>>>>>
>>>>>>I also saw that there are some test failures, probably due to new
>>>>>>tests. I'll try to work on that asap.
>>>>>>
>>>>>>Regards,
>>>>>>Serge...
>>>>>>
>>>>>>Serge Huber wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>I was afraid this would happen. I haven't had the time to work on
>>>>>>>Jackrabbit recently. I'll see if I can find some free time to get it
>>>>>>>up to speed. There was also a patch I supplied a while ago, I don't
>>>>>>>know if it had been applied.
>>>>>>>
>>>>>>>Regards,
>>>>>>>Serge Huber.
>>>>>>>
>>>>>>>Edgar Poce wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Hi roy
>>>>>>>>ORM-based persistence managers are out of synch with the latest
>>>>>>>>changes of the api. I've just created a jira issue. Thanks for
>>>>>>>>reporting it.
>>>>>>>>
>>>>>>>>BR,
>>>>>>>>edgar
>>>>>>>>
>>>>>>>>Roy Russo wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Hi all,
>>>>>>>>>
>>>>>>>>>I'm experiencing a problem trying to get the orm-persistence
>>>>>>>>>sources in
>>>>>>>>>/contrib to build on 'maven clean'. Its failing on trying to retrieve
>>>>>>>>>jackrabbit jar from day software:
>>>>>>>>>
>>>>>>>>>Attempting to download jackrabbit-0.16.4-dev.jar.
>>>>>>>>>Error retrieving artifact from
>>>>>>>>>[http://www.day.com/maven/jackrabbit/jars/jackrabbit-0.16.4-dev.jar]:
>>>>>>>>>java.io.IOException: Forbidden.
>>>>>>>>>WARNING: Failed to download jackrabbit-0.16.4-dev.jar.
>>>>>>>>>
>>>>>>>>>Obviously, I have this locally after building the parent project,
>>>>>>>>>but do
>>>>>>>>>not know how to point maven to use that instead.
>>>>>>>>>
>>>>>>>>>Regards,
>>>>>>>>>Roy Russo
>>>>>>>>>Jboss Portal Developer
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
>
Re: ORM-based persistence contrib build problems
Posted by Edgar Poce <ed...@gmail.com>.
Hi serge
I guess both frameworks provide a mechanism to assign unique values
for primary keys. see
http://db.apache.org/ojb/docu/guides/sequencemanager.html.
BR,
edgar
On 6/10/05, Serge Huber <sh...@jahia.com> wrote:
>
> Hi Edgar,
>
> Do you have any suggestions onto the format of the code ? Some UUID of
> some sort ?
>
> Regards,
> Serge Huber.
>
> Edgar Poce wrote:
>
> >Hi Serge
> >
> >On 6/9/05, Serge Huber <sh...@jahia.com> wrote:
> >
> >
> >>I didn't have time yesterday to look at the problems. I submitted a
> >>quick patch in order for everything to compile, and noticed the test
> >>failures but didn't have the time to investigate further. Would you be
> >>able to sum up the required changes in order to support this ? Does this
> >>mean that each node/property needs an extra workspace name column ?
> >>
> >>
> >
> >Just a thought. Given that all the workspaces share the uuid of the
> >root node, I think that every table needs an extra column. I'd use a
> >code rather than the workspace name. When initialized the PM should
> >get or create (if necessary) the code for the given workspace from a
> >table or from the FS.
> >The workspace name can be passed to the PM through config, e.g. <param
> >name="name" value="${wsp.name}"/>
> >
> >BR,
> >edgar
> >
> >
> >
> >>Regards,
> >> Serge Huber.
> >>
> >>Edgar Poce wrote:
> >>
> >>
> >>
> >>>Hi serge
> >>>
> >>> I gave a try to the orm PM and found that it stores the data
> >>>disregarding the workspace name, which means that the data stored in
> >>>one workspace is accessible from any other.
> >>> IMHO we should wait to commit the changes until this problem is
> >>>solved and both PMs, hibernate and OJB, pass all the tests. WDYT?
> >>>
> >>>BR,
> >>>edgar
> >>>
> >>>if you want to reproduce the error run the following code, it will
> >>>fail the second time.
> >>>
> >>>String newNodeName = "ormtest" ;
> >>>// Default workspace
> >>>Session defaultSession = helper.getReadWriteSession("default") ;
> >>>Node defaultRoot = defaultSession.getRootNode() ;
> >>>assertFalse(defaultRoot.hasNode(newNodeName));
> >>>defaultSession.logout() ;
> >>>
> >>>// Add a new node in workspace test
> >>>Session testSession = helper.getReadWriteSession("test") ;
> >>>Node testRoot = testSession.getRootNode() ;
> >>>testRoot.addNode(newNodeName) ;
> >>>testSession.save() ;
> >>>testSession.logout() ;
> >>>
> >>>
> >>>Serge Huber wrote:
> >>>
> >>>
> >>>
> >>>>Ok I've done a quick patch to allow for compilation of the
> >>>>contribution. Thank you for committing it as soon as possible. You
> >>>>can find it as an attachement to issue :
> >>>>http://issues.apache.org/jira/browse/JCR-129$
> >>>>
> >>>>I also saw that there are some test failures, probably due to new
> >>>>tests. I'll try to work on that asap.
> >>>>
> >>>>Regards,
> >>>> Serge...
> >>>>
> >>>>Serge Huber wrote:
> >>>>
> >>>>
> >>>>
> >>>>>I was afraid this would happen. I haven't had the time to work on
> >>>>>Jackrabbit recently. I'll see if I can find some free time to get it
> >>>>>up to speed. There was also a patch I supplied a while ago, I don't
> >>>>>know if it had been applied.
> >>>>>
> >>>>>Regards,
> >>>>> Serge Huber.
> >>>>>
> >>>>>Edgar Poce wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Hi roy
> >>>>>> ORM-based persistence managers are out of synch with the latest
> >>>>>>changes of the api. I've just created a jira issue. Thanks for
> >>>>>>reporting it.
> >>>>>>
> >>>>>>BR,
> >>>>>>edgar
> >>>>>>
> >>>>>>Roy Russo wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>Hi all,
> >>>>>>>
> >>>>>>>I'm experiencing a problem trying to get the orm-persistence
> >>>>>>>sources in
> >>>>>>>/contrib to build on 'maven clean'. Its failing on trying to retrieve
> >>>>>>>jackrabbit jar from day software:
> >>>>>>>
> >>>>>>>Attempting to download jackrabbit-0.16.4-dev.jar.
> >>>>>>>Error retrieving artifact from
> >>>>>>>[http://www.day.com/maven/jackrabbit/jars/jackrabbit-0.16.4-dev.jar]:
> >>>>>>>java.io.IOException: Forbidden.
> >>>>>>>WARNING: Failed to download jackrabbit-0.16.4-dev.jar.
> >>>>>>>
> >>>>>>>Obviously, I have this locally after building the parent project,
> >>>>>>>but do
> >>>>>>>not know how to point maven to use that instead.
> >>>>>>>
> >>>>>>>Regards,
> >>>>>>>Roy Russo
> >>>>>>>Jboss Portal Developer
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>
> >>
> >
> >
> >
>
>
Re: ORM-based persistence contrib build problems
Posted by Serge Huber <sh...@jahia.com>.
Hi Edgar,
Do you have any suggestions onto the format of the code ? Some UUID of
some sort ?
Regards,
Serge Huber.
Edgar Poce wrote:
>Hi Serge
>
>On 6/9/05, Serge Huber <sh...@jahia.com> wrote:
>
>
>>I didn't have time yesterday to look at the problems. I submitted a
>>quick patch in order for everything to compile, and noticed the test
>>failures but didn't have the time to investigate further. Would you be
>>able to sum up the required changes in order to support this ? Does this
>>mean that each node/property needs an extra workspace name column ?
>>
>>
>
>Just a thought. Given that all the workspaces share the uuid of the
>root node, I think that every table needs an extra column. I'd use a
>code rather than the workspace name. When initialized the PM should
>get or create (if necessary) the code for the given workspace from a
>table or from the FS.
>The workspace name can be passed to the PM through config, e.g. <param
>name="name" value="${wsp.name}"/>
>
>BR,
>edgar
>
>
>
>>Regards,
>> Serge Huber.
>>
>>Edgar Poce wrote:
>>
>>
>>
>>>Hi serge
>>>
>>> I gave a try to the orm PM and found that it stores the data
>>>disregarding the workspace name, which means that the data stored in
>>>one workspace is accessible from any other.
>>> IMHO we should wait to commit the changes until this problem is
>>>solved and both PMs, hibernate and OJB, pass all the tests. WDYT?
>>>
>>>BR,
>>>edgar
>>>
>>>if you want to reproduce the error run the following code, it will
>>>fail the second time.
>>>
>>>String newNodeName = "ormtest" ;
>>>// Default workspace
>>>Session defaultSession = helper.getReadWriteSession("default") ;
>>>Node defaultRoot = defaultSession.getRootNode() ;
>>>assertFalse(defaultRoot.hasNode(newNodeName));
>>>defaultSession.logout() ;
>>>
>>>// Add a new node in workspace test
>>>Session testSession = helper.getReadWriteSession("test") ;
>>>Node testRoot = testSession.getRootNode() ;
>>>testRoot.addNode(newNodeName) ;
>>>testSession.save() ;
>>>testSession.logout() ;
>>>
>>>
>>>Serge Huber wrote:
>>>
>>>
>>>
>>>>Ok I've done a quick patch to allow for compilation of the
>>>>contribution. Thank you for committing it as soon as possible. You
>>>>can find it as an attachement to issue :
>>>>http://issues.apache.org/jira/browse/JCR-129$
>>>>
>>>>I also saw that there are some test failures, probably due to new
>>>>tests. I'll try to work on that asap.
>>>>
>>>>Regards,
>>>> Serge...
>>>>
>>>>Serge Huber wrote:
>>>>
>>>>
>>>>
>>>>>I was afraid this would happen. I haven't had the time to work on
>>>>>Jackrabbit recently. I'll see if I can find some free time to get it
>>>>>up to speed. There was also a patch I supplied a while ago, I don't
>>>>>know if it had been applied.
>>>>>
>>>>>Regards,
>>>>> Serge Huber.
>>>>>
>>>>>Edgar Poce wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Hi roy
>>>>>> ORM-based persistence managers are out of synch with the latest
>>>>>>changes of the api. I've just created a jira issue. Thanks for
>>>>>>reporting it.
>>>>>>
>>>>>>BR,
>>>>>>edgar
>>>>>>
>>>>>>Roy Russo wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Hi all,
>>>>>>>
>>>>>>>I'm experiencing a problem trying to get the orm-persistence
>>>>>>>sources in
>>>>>>>/contrib to build on 'maven clean'. Its failing on trying to retrieve
>>>>>>>jackrabbit jar from day software:
>>>>>>>
>>>>>>>Attempting to download jackrabbit-0.16.4-dev.jar.
>>>>>>>Error retrieving artifact from
>>>>>>>[http://www.day.com/maven/jackrabbit/jars/jackrabbit-0.16.4-dev.jar]:
>>>>>>>java.io.IOException: Forbidden.
>>>>>>>WARNING: Failed to download jackrabbit-0.16.4-dev.jar.
>>>>>>>
>>>>>>>Obviously, I have this locally after building the parent project,
>>>>>>>but do
>>>>>>>not know how to point maven to use that instead.
>>>>>>>
>>>>>>>Regards,
>>>>>>>Roy Russo
>>>>>>>Jboss Portal Developer
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>
>>
>
>
>
Re: ORM-based persistence contrib build problems
Posted by Edgar Poce <ed...@gmail.com>.
Hi Serge
On 6/9/05, Serge Huber <sh...@jahia.com> wrote:
> I didn't have time yesterday to look at the problems. I submitted a
> quick patch in order for everything to compile, and noticed the test
> failures but didn't have the time to investigate further. Would you be
> able to sum up the required changes in order to support this ? Does this
> mean that each node/property needs an extra workspace name column ?
Just a thought. Given that all the workspaces share the uuid of the
root node, I think that every table needs an extra column. I'd use a
code rather than the workspace name. When initialized the PM should
get or create (if necessary) the code for the given workspace from a
table or from the FS.
The workspace name can be passed to the PM through config, e.g. <param
name="name" value="${wsp.name}"/>
BR,
edgar
>
> Regards,
> Serge Huber.
>
> Edgar Poce wrote:
>
> > Hi serge
> >
> > I gave a try to the orm PM and found that it stores the data
> > disregarding the workspace name, which means that the data stored in
> > one workspace is accessible from any other.
> > IMHO we should wait to commit the changes until this problem is
> > solved and both PMs, hibernate and OJB, pass all the tests. WDYT?
> >
> > BR,
> > edgar
> >
> > if you want to reproduce the error run the following code, it will
> > fail the second time.
> >
> > String newNodeName = "ormtest" ;
> > // Default workspace
> > Session defaultSession = helper.getReadWriteSession("default") ;
> > Node defaultRoot = defaultSession.getRootNode() ;
> > assertFalse(defaultRoot.hasNode(newNodeName));
> > defaultSession.logout() ;
> >
> > // Add a new node in workspace test
> > Session testSession = helper.getReadWriteSession("test") ;
> > Node testRoot = testSession.getRootNode() ;
> > testRoot.addNode(newNodeName) ;
> > testSession.save() ;
> > testSession.logout() ;
> >
> >
> > Serge Huber wrote:
> >
> >>
> >> Ok I've done a quick patch to allow for compilation of the
> >> contribution. Thank you for committing it as soon as possible. You
> >> can find it as an attachement to issue :
> >> http://issues.apache.org/jira/browse/JCR-129$
> >>
> >> I also saw that there are some test failures, probably due to new
> >> tests. I'll try to work on that asap.
> >>
> >> Regards,
> >> Serge...
> >>
> >> Serge Huber wrote:
> >>
> >>>
> >>> I was afraid this would happen. I haven't had the time to work on
> >>> Jackrabbit recently. I'll see if I can find some free time to get it
> >>> up to speed. There was also a patch I supplied a while ago, I don't
> >>> know if it had been applied.
> >>>
> >>> Regards,
> >>> Serge Huber.
> >>>
> >>> Edgar Poce wrote:
> >>>
> >>>> Hi roy
> >>>> ORM-based persistence managers are out of synch with the latest
> >>>> changes of the api. I've just created a jira issue. Thanks for
> >>>> reporting it.
> >>>>
> >>>> BR,
> >>>> edgar
> >>>>
> >>>> Roy Russo wrote:
> >>>>
> >>>>> Hi all,
> >>>>>
> >>>>> I'm experiencing a problem trying to get the orm-persistence
> >>>>> sources in
> >>>>> /contrib to build on 'maven clean'. Its failing on trying to retrieve
> >>>>> jackrabbit jar from day software:
> >>>>>
> >>>>> Attempting to download jackrabbit-0.16.4-dev.jar.
> >>>>> Error retrieving artifact from
> >>>>> [http://www.day.com/maven/jackrabbit/jars/jackrabbit-0.16.4-dev.jar]:
> >>>>> java.io.IOException: Forbidden.
> >>>>> WARNING: Failed to download jackrabbit-0.16.4-dev.jar.
> >>>>>
> >>>>> Obviously, I have this locally after building the parent project,
> >>>>> but do
> >>>>> not know how to point maven to use that instead.
> >>>>>
> >>>>> Regards,
> >>>>> Roy Russo
> >>>>> Jboss Portal Developer
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
>
>
Re: ORM-based persistence contrib build problems
Posted by Serge Huber <sh...@jahia.com>.
Hi Edgar,
So that's what's wrong with it :)
I didn't have time yesterday to look at the problems. I submitted a
quick patch in order for everything to compile, and noticed the test
failures but didn't have the time to investigate further. Would you be
able to sum up the required changes in order to support this ? Does this
mean that each node/property needs an extra workspace name column ?
Regards,
Serge Huber.
Edgar Poce wrote:
> Hi serge
>
> I gave a try to the orm PM and found that it stores the data
> disregarding the workspace name, which means that the data stored in
> one workspace is accessible from any other.
> IMHO we should wait to commit the changes until this problem is
> solved and both PMs, hibernate and OJB, pass all the tests. WDYT?
>
> BR,
> edgar
>
> if you want to reproduce the error run the following code, it will
> fail the second time.
>
> String newNodeName = "ormtest" ;
> // Default workspace
> Session defaultSession = helper.getReadWriteSession("default") ;
> Node defaultRoot = defaultSession.getRootNode() ;
> assertFalse(defaultRoot.hasNode(newNodeName));
> defaultSession.logout() ;
>
> // Add a new node in workspace test
> Session testSession = helper.getReadWriteSession("test") ;
> Node testRoot = testSession.getRootNode() ;
> testRoot.addNode(newNodeName) ;
> testSession.save() ;
> testSession.logout() ;
>
>
> Serge Huber wrote:
>
>>
>> Ok I've done a quick patch to allow for compilation of the
>> contribution. Thank you for committing it as soon as possible. You
>> can find it as an attachement to issue :
>> http://issues.apache.org/jira/browse/JCR-129$
>>
>> I also saw that there are some test failures, probably due to new
>> tests. I'll try to work on that asap.
>>
>> Regards,
>> Serge...
>>
>> Serge Huber wrote:
>>
>>>
>>> I was afraid this would happen. I haven't had the time to work on
>>> Jackrabbit recently. I'll see if I can find some free time to get it
>>> up to speed. There was also a patch I supplied a while ago, I don't
>>> know if it had been applied.
>>>
>>> Regards,
>>> Serge Huber.
>>>
>>> Edgar Poce wrote:
>>>
>>>> Hi roy
>>>> ORM-based persistence managers are out of synch with the latest
>>>> changes of the api. I've just created a jira issue. Thanks for
>>>> reporting it.
>>>>
>>>> BR,
>>>> edgar
>>>>
>>>> Roy Russo wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I'm experiencing a problem trying to get the orm-persistence
>>>>> sources in
>>>>> /contrib to build on 'maven clean'. Its failing on trying to retrieve
>>>>> jackrabbit jar from day software:
>>>>>
>>>>> Attempting to download jackrabbit-0.16.4-dev.jar.
>>>>> Error retrieving artifact from
>>>>> [http://www.day.com/maven/jackrabbit/jars/jackrabbit-0.16.4-dev.jar]:
>>>>> java.io.IOException: Forbidden.
>>>>> WARNING: Failed to download jackrabbit-0.16.4-dev.jar.
>>>>>
>>>>> Obviously, I have this locally after building the parent project,
>>>>> but do
>>>>> not know how to point maven to use that instead.
>>>>>
>>>>> Regards,
>>>>> Roy Russo
>>>>> Jboss Portal Developer
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>
Re: ORM-based persistence contrib build problems
Posted by Edgar Poce <ed...@gmail.com>.
Hi serge
I gave a try to the orm PM and found that it stores the data
disregarding the workspace name, which means that the data stored in one
workspace is accessible from any other.
IMHO we should wait to commit the changes until this problem is solved
and both PMs, hibernate and OJB, pass all the tests. WDYT?
BR,
edgar
if you want to reproduce the error run the following code, it will fail
the second time.
String newNodeName = "ormtest" ;
// Default workspace
Session defaultSession = helper.getReadWriteSession("default") ;
Node defaultRoot = defaultSession.getRootNode() ;
assertFalse(defaultRoot.hasNode(newNodeName));
defaultSession.logout() ;
// Add a new node in workspace test
Session testSession = helper.getReadWriteSession("test") ;
Node testRoot = testSession.getRootNode() ;
testRoot.addNode(newNodeName) ;
testSession.save() ;
testSession.logout() ;
Serge Huber wrote:
>
> Ok I've done a quick patch to allow for compilation of the contribution.
> Thank you for committing it as soon as possible. You can find it as an
> attachement to issue : http://issues.apache.org/jira/browse/JCR-129$
>
> I also saw that there are some test failures, probably due to new tests.
> I'll try to work on that asap.
>
> Regards,
> Serge...
>
> Serge Huber wrote:
>
>>
>> I was afraid this would happen. I haven't had the time to work on
>> Jackrabbit recently. I'll see if I can find some free time to get it
>> up to speed. There was also a patch I supplied a while ago, I don't
>> know if it had been applied.
>>
>> Regards,
>> Serge Huber.
>>
>> Edgar Poce wrote:
>>
>>> Hi roy
>>> ORM-based persistence managers are out of synch with the latest
>>> changes of the api. I've just created a jira issue. Thanks for
>>> reporting it.
>>>
>>> BR,
>>> edgar
>>>
>>> Roy Russo wrote:
>>>
>>>> Hi all,
>>>>
>>>> I'm experiencing a problem trying to get the orm-persistence sources in
>>>> /contrib to build on 'maven clean'. Its failing on trying to retrieve
>>>> jackrabbit jar from day software:
>>>>
>>>> Attempting to download jackrabbit-0.16.4-dev.jar.
>>>> Error retrieving artifact from
>>>> [http://www.day.com/maven/jackrabbit/jars/jackrabbit-0.16.4-dev.jar]:
>>>> java.io.IOException: Forbidden.
>>>> WARNING: Failed to download jackrabbit-0.16.4-dev.jar.
>>>>
>>>> Obviously, I have this locally after building the parent project,
>>>> but do
>>>> not know how to point maven to use that instead.
>>>>
>>>> Regards,
>>>> Roy Russo
>>>> Jboss Portal Developer
>>>>
>>>>
>>>
>>
>>
>
>
Re: ORM-based persistence contrib build problems
Posted by Serge Huber <sh...@jahia.com>.
Ok I've done a quick patch to allow for compilation of the contribution.
Thank you for committing it as soon as possible. You can find it as an
attachement to issue : http://issues.apache.org/jira/browse/JCR-129$
I also saw that there are some test failures, probably due to new tests.
I'll try to work on that asap.
Regards,
Serge...
Serge Huber wrote:
>
> I was afraid this would happen. I haven't had the time to work on
> Jackrabbit recently. I'll see if I can find some free time to get it
> up to speed. There was also a patch I supplied a while ago, I don't
> know if it had been applied.
>
> Regards,
> Serge Huber.
>
> Edgar Poce wrote:
>
>> Hi roy
>> ORM-based persistence managers are out of synch with the latest
>> changes of the api. I've just created a jira issue. Thanks for
>> reporting it.
>>
>> BR,
>> edgar
>>
>> Roy Russo wrote:
>>
>>> Hi all,
>>>
>>> I'm experiencing a problem trying to get the orm-persistence sources in
>>> /contrib to build on 'maven clean'. Its failing on trying to retrieve
>>> jackrabbit jar from day software:
>>>
>>> Attempting to download jackrabbit-0.16.4-dev.jar.
>>> Error retrieving artifact from
>>> [http://www.day.com/maven/jackrabbit/jars/jackrabbit-0.16.4-dev.jar]:
>>> java.io.IOException: Forbidden.
>>> WARNING: Failed to download jackrabbit-0.16.4-dev.jar.
>>>
>>> Obviously, I have this locally after building the parent project,
>>> but do
>>> not know how to point maven to use that instead.
>>>
>>> Regards,
>>> Roy Russo
>>> Jboss Portal Developer
>>>
>>>
>>
>
>
Re: ORM-based persistence contrib build problems
Posted by Serge Huber <sh...@jahia.com>.
I was afraid this would happen. I haven't had the time to work on
Jackrabbit recently. I'll see if I can find some free time to get it up
to speed. There was also a patch I supplied a while ago, I don't know if
it had been applied.
Regards,
Serge Huber.
Edgar Poce wrote:
> Hi roy
> ORM-based persistence managers are out of synch with the latest
> changes of the api. I've just created a jira issue. Thanks for
> reporting it.
>
> BR,
> edgar
>
> Roy Russo wrote:
>
>> Hi all,
>>
>> I'm experiencing a problem trying to get the orm-persistence sources in
>> /contrib to build on 'maven clean'. Its failing on trying to retrieve
>> jackrabbit jar from day software:
>>
>> Attempting to download jackrabbit-0.16.4-dev.jar.
>> Error retrieving artifact from
>> [http://www.day.com/maven/jackrabbit/jars/jackrabbit-0.16.4-dev.jar]:
>> java.io.IOException: Forbidden.
>> WARNING: Failed to download jackrabbit-0.16.4-dev.jar.
>>
>> Obviously, I have this locally after building the parent project, but do
>> not know how to point maven to use that instead.
>>
>> Regards,
>> Roy Russo
>> Jboss Portal Developer
>>
>>
>
Re: ORM-based persistence contrib build problems
Posted by Edgar Poce <ed...@gmail.com>.
Hi roy
ORM-based persistence managers are out of synch with the latest
changes of the api. I've just created a jira issue. Thanks for reporting it.
BR,
edgar
Roy Russo wrote:
> Hi all,
>
> I'm experiencing a problem trying to get the orm-persistence sources in
> /contrib to build on 'maven clean'. Its failing on trying to retrieve
> jackrabbit jar from day software:
>
> Attempting to download jackrabbit-0.16.4-dev.jar.
> Error retrieving artifact from
> [http://www.day.com/maven/jackrabbit/jars/jackrabbit-0.16.4-dev.jar]:
> java.io.IOException: Forbidden.
> WARNING: Failed to download jackrabbit-0.16.4-dev.jar.
>
> Obviously, I have this locally after building the parent project, but do
> not know how to point maven to use that instead.
>
> Regards,
> Roy Russo
> Jboss Portal Developer
>
>