Unger Richard wrote:
[snip]
Well, the idea on my part was to keep compatibility with the slide concept
that every node in the stucture is associated with a role. Thus it is still
possible to get a SlideToken for an arbitrary node on the filesystem, and
use it for access. It makes it possible, for example, to have a
WorkflowNode, with roles, or something like that. I have to admit I never
fully understood the necesity for every node to have a role, but I went with
it.
Okay. If you (or anyone else) could come up with a better name than RoleContainer, that'd be nice ;-)

Otherwise I'm still not sure why we don't just put it in ObjectNode directly. Slide doesn't have much of a tradition of using interfaces for this kind of thing IMHO.

[snip]
PS: Who is using Java 1.4, Java 1.3, or Java 1.2.2? Basically, I guess my
question is can Slide 2.0 be designed for Java 1.4, or do we have to support
1.3 or (gasp) 1.2.2? Basically, I am using very little 1.4 functionality
(regular expressions), but I use the new collection classes extensively
HashMap, Iterator, ArrayList etc, instead of Hashtable, Enumeration,
Vector... Is this a problem?
Okay, in general the Jakarta projects are JDK 1.2 compatible, very few are even 1.1 compatible, and a couple require JDK 1.3. Slide belongs to the first category -- at least in theory, I can't say that I've tested compiling/running on 1.2 recently. Using the Java 2 Collections API is okay, even though the old collection classes (Vector, Enumeration, Hashtable) are still used all over the place in Slide.

Using a 1.4 feature like logging or regexp is *not* okay. What do you need regexp for anyway?

PPS: Synchronization: I wanted some advice about the transaction stuff,
without digging in the code... Does using the transaction.begin() and end()
methods synchronize different threads on the transaction, or should I
synchronize access to the userdatabase explicitly myself? Is there anything
to watch out for when using the transaction stuff, or is it really as simple
as just calls to begin() and end()?
Can't really help you on this one... though I think using NAT.begin()/NAT.commit()/NAT.rollback() is sufficient.

--
Christopher Lenz
/=/ cmlenz at gmx.de


--
To unsubscribe, e-mail: <mailto:slide-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:slide-dev-help@;jakarta.apache.org>



Reply via email to