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 <[EMAIL PROTECTED]> 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
