gmane.comp.apache.jackrabbit.devel

Created: (JCR-1721) make collection element names configureable

make collection element names configureable
-------------------------------------------

                 Key: JCR-1721
                 URL: https://issues.apache.org/jira/browse/JCR-1721
             Project: Jackrabbit
          Issue Type: New Feature
          Components: jackrabbit-ocm
            Reporter: Oliver Lietz
            Priority: Minor
         Attachments: jcrElementName.diff

- add jcrElementName to CollectionDescriptor and Collection annotation
- make COLLECTION_ELEMENT_NAME protected instead of private

headers

angela (JIRA | 20 Aug 12:03

Created: (JCR-1720) Jcr2Spi: configuration entry for size of ItemCache

Jcr2Spi: configuration entry for size of ItemCache
--------------------------------------------------

                 Key: JCR-1720
                 URL: https://issues.apache.org/jira/browse/JCR-1720
             Project: Jackrabbit
          Issue Type: Improvement
          Components: jackrabbit-jcr2spi
            Reporter: angela
            Assignee: angela
            Priority: Trivial

in order to make the size of the ItemCache configurable (see TODO in jcr2spi SessionImpl) i'd like to extend
the jcr2spi RepositoryConfig and have a default value being provided with AbstractRepositoryConfig in
the tests section.

headers

Rory Douglas (JIRA | 19 Aug 17:08

Created: (JCR-1719) Make the extraction of Session UserIDs from Subjects configurable

Make the extraction of Session UserIDs from Subjects configurable
-----------------------------------------------------------------

                 Key: JCR-1719
                 URL: https://issues.apache.org/jira/browse/JCR-1719
             Project: Jackrabbit
          Issue Type: New Feature
          Components: jackrabbit-core, security
    Affects Versions: core 1.4.5, 1.5
            Reporter: Rory Douglas
            Priority: Minor

The SessionImpl class must extract a string name from the Prinicpals in a Subject to use as the Session
userID.  In 1.4 the SessionImpl class directly selects the first available Principal.  In 1.5, this is
delegated to the SecurityManager, which chooses the first  non-group principal.

It would be useful to be able to configure specific selection criteria for the Principal used for the
Session userID.  A simple mechanism would involve specifying a Principal implementation classname in
the configuration, and the first instance of that class found in the Subject would be used for the userID. 
One way to implement this in 1.4 would be to extend AuthContext to include a method getSessionPrincipal()
which encapsulates the selection logic, and adding an option the LoginModuleConfig to specify the class
name of the Principal to select.

A particular use case is using the LDAP LoginModule from Sun JDK 6 with the repository.  The first Principal
LdapLoginModule populates into the Subject is an instance of LdapPrincipal, which renders the userID as
the full DN of the user.  The LoginModule also adds an instance of UserPrincipal, whose name is the simple
username/uid attribute, which would be more appropriate as the Session userId since it corresponds to
the username provided by the user to application authentication mechanisms (the provided username is
expanded into the full DN prior to authentication by the login module).  If the above configuration
mechanism were available, one could configure the LdapLoginModule, and specify that the userID be

(Continue reading)

headers

jira | 17 Aug 08:19

Subscription: open issues

Issue Subscription
Filter: open issues (286 issues)
Open Issues for Apache Jackrabbit
Subscriber: jackrabbitdev

Key         Summary
JCR-1718    repository-1.5.dtd: change order of main elements
            https://issues.apache.org/jira/browse/JCR-1718
JCR-1715    Prevent excessive Path.Element instances
            https://issues.apache.org/jira/browse/JCR-1715
JCR-1712    JSR 283: JCR Names
            https://issues.apache.org/jira/browse/JCR-1712
JCR-1711    Download: improve user experience
            https://issues.apache.org/jira/browse/JCR-1711
JCR-1708    Impossible to import a string containing _x0020_  with Session.importXml
            https://issues.apache.org/jira/browse/JCR-1708
JCR-1707    Node.setProperty(String, String, PropertyType.UNDEFINED) might fail unexpectedly for
multiple prop. defs
            https://issues.apache.org/jira/browse/JCR-1707
JCR-1705    Reduce memory usage of transient nodes
            https://issues.apache.org/jira/browse/JCR-1705
JCR-1703    Oracle JNDI DataSource support
            https://issues.apache.org/jira/browse/JCR-1703
JCR-1702    Unable to create/lock Node in one Transaction
            https://issues.apache.org/jira/browse/JCR-1702
JCR-1695    Improve and promote spi-logger
            https://issues.apache.org/jira/browse/JCR-1695
JCR-1694    System properties does not get replaced in a Cluster configuration
            https://issues.apache.org/jira/browse/JCR-1694
JCR-1693    JNDIDatabaseJournal doesn't work with "oracle" schema (or: unable to use

(Continue reading)

headers

Thomas Mueller (JIRA | 13 Aug 22:24

Created: (JCR-1718) repository-1.5.dtd: change order of main elements

repository-1.5.dtd: change order of main elements
-------------------------------------------------

                 Key: JCR-1718
                 URL: https://issues.apache.org/jira/browse/JCR-1718
             Project: Jackrabbit
          Issue Type: Improvement
          Components: jackrabbit-core
            Reporter: Thomas Mueller
            Assignee: Thomas Mueller
            Priority: Minor

Currently the order of elements in repository.xml is:
<!ELEMENT Repository (FileSystem,Security,Workspaces,Workspace,Versioning,SearchIndex?,Cluster?,DataStore?)>

I would like to change it to
<!ELEMENT Repository (Cluster?,FileSystem,DataStore?,Security,Workspaces,Workspace,Versioning,SearchIndex?)>
because I think that makes more sense.

Currently XML validation is disabled, and therefore the order of elements in the DTD does not need to match
the repository.xml file. However as soon as XML validation is enabled, repository.xml files that use the
wrong order will no longer work (the repository can not be started).

There is a request to enable XML validation at http://issues.apache.org/jira/browse/JCR-1462

headers

Oleg Alexeyev (JIRA | 11 Aug 15:34

Commented: (JCR-134) Unreferenced VersionHistory should be deleted automatically.


    [
https://issues.apache.org/jira/browse/JCR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621448#action_12621448
] 

Oleg Alexeyev commented on JCR-134:
-----------------------------------

IMO, this covers at least the most important use case.

Actually, "node.remove() after all versions (except the root version) have been deleted" is not possible
as the node refers to one of the versions. So, we tried to clean up VH, we used node.remove() and then
VH.removeVersion() for each Version returned by getAllVersions() enumeration except the root one.
This approach works, but leaves VH and root version nodes.

Thanks for approaching this issue! :)

> Unreferenced VersionHistory should be deleted automatically.
> ------------------------------------------------------------
>
>                 Key: JCR-134
>                 URL: https://issues.apache.org/jira/browse/JCR-134
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: versioning
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>            Priority: Minor
>         Attachments: jackrabbit-1.4.x-JCR-134-first-try-2008-08-11.patch
>

(Continue reading)

headers

Sébastien Launay | 11 Aug 15:22

Updated: (JCR-134) Unreferenced VersionHistory should be deleted automatically.


     [
https://issues.apache.org/jira/browse/JCR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sébastien Launay updated JCR-134:
---------------------------------

    Attachment: jackrabbit-1.4.x-JCR-134-first-try-2008-08-11.patch

As no one reply to my thread for fixing this issue:
http://markmail.org/message/7boajk2b2mnhe4xf
i will try to submit a fix :).

The solution that i propose is based on the following facts:
- if there is no references to the VersionHistory node then no one node is alive.
- if the VersionHistory node has only two children (root version and version labels) then there is no
version for restoring the content.

These tests are computed in InternalVersionHistoryImpl#removeVersion(Name).

The following use cases are supported:
- committed node.remove() followed by multiple versionHistory.removeVersion(..)
the version history is then deleted in the same time as the last version is removed.

The following use cases are not supported (yet):
- node.removeMixin("mix:versionable")
- node.remove() after all versions (except the root version) have been deleted (don't know if this is possible)

This patch comes with a test case to validate version history cleaning.

(Continue reading)

headers

Marcel Reutegger (JIRA | 11 Aug 13:56

Created: (JCR-1717) Configure occurrence of property value in excerpt

Configure occurrence of property value in excerpt
-------------------------------------------------

                 Key: JCR-1717
                 URL: https://issues.apache.org/jira/browse/JCR-1717
             Project: Jackrabbit
          Issue Type: New Feature
          Components: jackrabbit-core
            Reporter: Marcel Reutegger
            Priority: Minor

Jackrabbit currently includes all indexed property values as potential content in an excerpt. This is not
always desirable because there may be properties that need to be full-text indexed but should not show up
in an excerpt.

headers

Apache Hudson Server | 11 Aug 12:52

Hudson build is back to stable: Jackrabbit-trunk » Jackrabbit SPI to JCR #144

See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-spi2jcr/144/changes

headers

jira | 10 Aug 08:17

Subscription: open issues

Issue Subscription
Filter: open issues (287 issues)
Open Issues for Apache Jackrabbit
Subscriber: jackrabbitdev

Key         Summary
JCR-1715    Prevent excessive Path.Element instances
            https://issues.apache.org/jira/browse/JCR-1715
JCR-1714    QueryImpl result offSet must be considered after security class grant the item.
            https://issues.apache.org/jira/browse/JCR-1714
JCR-1712    JSR 283: JCR Names
            https://issues.apache.org/jira/browse/JCR-1712
JCR-1711    Download: improve user experience
            https://issues.apache.org/jira/browse/JCR-1711
JCR-1708    Impossible to import a string containing _x0020_  with Session.importXml
            https://issues.apache.org/jira/browse/JCR-1708
JCR-1707    Node.setProperty(String, String, PropertyType.UNDEFINED) might fail unexpectedly for
multiple prop. defs
            https://issues.apache.org/jira/browse/JCR-1707
JCR-1705    Reduce memory usage of transient nodes
            https://issues.apache.org/jira/browse/JCR-1705
JCR-1703    Oracle JNDI DataSource support
            https://issues.apache.org/jira/browse/JCR-1703
JCR-1702    Unable to create/lock Node in one Transaction
            https://issues.apache.org/jira/browse/JCR-1702
JCR-1695    Improve and promote spi-logger
            https://issues.apache.org/jira/browse/JCR-1695
JCR-1694    System properties does not get replaced in a Cluster configuration
            https://issues.apache.org/jira/browse/JCR-1694
JCR-1693    JNDIDatabaseJournal doesn't work with "oracle" schema (or: unable to use

(Continue reading)

headers

Marcel Reutegger (JIRA | 8 Aug 17:15

Created: (JCR-1716) Prefer PathFactory.createElement() over createPath().getNameElement()

Prefer PathFactory.createElement() over createPath().getNameElement()
---------------------------------------------------------------------

                 Key: JCR-1716
                 URL: https://issues.apache.org/jira/browse/JCR-1716
             Project: Jackrabbit
          Issue Type: Improvement
          Components: jackrabbit-core
            Reporter: Marcel Reutegger
            Priority: Minor

The latter creates an unnecessary Path instance.

Mon	Tue	Wed	Thu	Fri	Sat	Sun

				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30	31