juergen 2003/11/04 00:23:09
Modified:testsuite/testsuite/junit/xmltestcases/DeltaV/additionalUseCases/move
ChoutMveChIn.xml ChoutMvePutUnckout.xml
VcMveDelPutMveVc.xml VcMveDelVcMve.xml
VcMveDelVcMvePut.xml
juergen 2003/11/04 00:23:26
Modified:testsuite/testsuite/junit/xmltestcases/DeltaV/compatability/LockC
Checkin.xml Checkout.xml Label.xml Mkworkspace.xml
Report.xml Update.xml Versioncontrol.xml
Hi Colin, hi Ashok, hi all!
If you reposted and donated the latest version of your code I will
promise to do my best to merge it with the other versions / branches.
This could be good for us all, as our efforts can be combined!
Anyway (just observations / questions, no exposing or anything
Christophe Lombart [EMAIL PROTECTED] writes:
I'm trying to use J2EEStore with MySql (with adapter :-)) ). I also
modifed this store in order to support DBCP.
Did you use MySql 4? MySql 3 has not transaction support, which is required
for slide.
Martin
4.0.15 standard - InnoDB
It strange because dealocks occurs only on delete statments.
Sometime, the Slide RDBMS Adapter delete rows without using primary key.
Do you think that MySql locks more rows in this case ?
Christophe
-Original Message-
From: Martin Holz [mailto:[EMAIL
juergen 2003/11/04 03:45:30
Modified:
testsuite/testsuite/junit/xmltestcases/ACL/functional/AccessControlExisitingMethods
OptionsAccess-ControlHeader.xml
testsuite/testsuite/junit/xmltestcases/ACL/functional/AccessControlMethods/ACLExamples
juergen 2003/11/04 03:45:41
Modified:
testsuite/testsuite/junit/xmltestcases/ACL/groupFunctional/AccessControlMethods/ACLExamples
01_ACL2DenyAllForGroupGrantRead.xml
02_ACL2DenyAllForGroupGrantWrite.xml
juergen 2003/11/04 04:09:17
Modified:testsuite/testsuite/junit/xmltestcases/BIND/functional
binddir.xml bindfile.xml
testsuite/testsuite/junit/xmltestcases/BIND/functional/Unbind
unbindCollectionFile_1.xml
Hello, Peter,
thanks for letting us participate :)
Nevermann, Dr., Peter wrote:
1) User group relationships will not be mapped anymore to the URI
hierarchy
Instead, the DAV:group-member-set and DAV:group-membership properties are
used which allows for many-to-many relationships between users
1.) There is this closing of resources issue:
If you take a closes look you will see statement will not be closed
when
res.close() rises an exception. Admittedly, this is unlikely, but why
risking this? Maybe it is fixed in your code, already? I know it is
ugly, but maybe like this:
Agreed
Oliver Zeigermann wrote:
Hello, Peter,
thanks for letting us participate :)
Nevermann, Dr., Peter wrote:
1) User group relationships will not be mapped anymore to
the URI hierarchy
Instead, the DAV:group-member-set and DAV:group-membership
properties are used which allows for
[EMAIL PROTECTED] wrote:
2.) Why do you think the approach in org.apache.slide.store.impl.rdbms
is better than yours? Why is there an adapter? Also, where do you see a
nicer Java approach?
Well with the adaptor then different DB optimizations maybe more easily
accommodated.
Also I prefer more
Martin Dulisch wrote:
In WebDAV principals are also represented as resources. These
have the properties. You can find a detailed description here:
http://www.webdav.org/acl/protocol/draft-ietf-webdav-acl-12.htm#_Toc53484905
Thanks Martin, this makes things clear to me. I am not very good in
Hello all!
In my opinion, both approaches do have their pros and cons.
One difference between doing the db-optimization by using the adapter-concept
or doing it by subclassing will appear in the domain.xml-configuration:
The use of the adapter is a little bit more complicated, because the user
Hi All
Resubmitting the latest J2EEStore related classes from our CVS. I have
incorporated the point(1) raised by Oliver. Now we have nested
try..final blocks for each.
Include the SQLServer Schema with and with out foreign key relations and
the sample domain.xml
Ashok
-Original
Nevermann, Dr., Peter wrote:
1) User group relationships will not be mapped anymore to the URI
hierarchy
Instead, the DAV:group-member-set and DAV:group-membership
properties are
used which allows for many-to-many relationships between
users and groups.
Just for my understanding.
Given the obervations above and my *personal* impression your store
seems to be the most mature, so it would be of great help if you donated
the latest version of your code!
Oliver (and others),
Be warned that NONE of the JDBC/J2EE based stores can be safely used
with access control, unless
Servlet API lacking?
Brief examination of the source for Tomcat 4.1 leads me to believe that
though sendError(int) does provide a way for communicating informational
responses in the 1xx range -- which incidently aren't error conditions
-- that later attempts to
Michael Smith wrote:
Be warned that NONE of the JDBC/J2EE based stores can be safely used
with access control, unless you take care to never set an ACL with more
than one ACE. See the discussion of this a few months back as to why
(fixing it requires minor db schema changes).
Ahhh. Thanks for
Oliver Zeigermann wrote:
Michael Smith wrote:
Be warned that NONE of the JDBC/J2EE based stores can be safely used
with access control, unless you take care to never set an ACL with
more than one ACE. See the discussion of this a few months back as to
why (fixing it requires minor db schema
20 matches
Mail list logo
