You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "Janne Jalkanen (JIRA)" <ji...@apache.org> on 2008/11/09 10:38:44 UTC

[jira] Created: (JSPWIKI-421) JCR backend

JCR backend
-----------

                 Key: JSPWIKI-421
                 URL: https://issues.apache.org/jira/browse/JSPWIKI-421
             Project: JSPWiki
          Issue Type: Improvement
          Components: Core & storage
            Reporter: Janne Jalkanen
            Assignee: Janne Jalkanen
             Fix For: 3.0


3.0 should use JSR-170 (aka Java Content Repository) as the backend.  This allows our metadata model to be replaced with something far more efficient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (JSPWIKI-421) JCR backend

Posted by "Andrew Jaquith (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JSPWIKI-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834579#action_12834579 ] 

Andrew Jaquith commented on JSPWIKI-421:
----------------------------------------

Janne, I think this is done. Yes, there are some unit test errors that remain. But the core JCR back-end is pretty solid. Recommend we close this issue. If we find blockers, we should add them specifically. (As I have with the "Clean unit tests [JSPWiki-636]" issue.)

> JCR backend
> -----------
>
>                 Key: JSPWIKI-421
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-421
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Core & storage
>            Reporter: Janne Jalkanen
>            Assignee: Janne Jalkanen
>             Fix For: 3.0
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> 3.0 should use JSR-170 (aka Java Content Repository) as the backend.  This allows our metadata model to be replaced with something far more efficient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JSPWIKI-421) JCR backend

Posted by "Andrew Jaquith (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JSPWIKI-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Jaquith updated JSPWIKI-421:
-----------------------------------

    Comment: was deleted

(was: Janne, I think this is done. Yes, there are some unit test errors that remain. But the core JCR back-end is pretty solid. Recommend we close this issue. If we find blockers, we should add them specifically. (As I have with the "Clean unit tests [JSPWiki-646]" issue.))

> JCR backend
> -----------
>
>                 Key: JSPWIKI-421
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-421
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Core & storage
>            Reporter: Janne Jalkanen
>            Assignee: Janne Jalkanen
>             Fix For: 3.0
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> 3.0 should use JSR-170 (aka Java Content Repository) as the backend.  This allows our metadata model to be replaced with something far more efficient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (JSPWIKI-421) JCR backend

Posted by "Andrew Jaquith (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JSPWIKI-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834578#action_12834578 ] 

Andrew Jaquith commented on JSPWIKI-421:
----------------------------------------

Janne, I think this is done. Yes, there are some unit test errors that remain. But the core JCR back-end is pretty solid. Recommend we close this issue. If we find blockers, we should add them specifically. (As I have with the "Clean unit tests [JSPWiki-646]" issue.)

> JCR backend
> -----------
>
>                 Key: JSPWIKI-421
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-421
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Core & storage
>            Reporter: Janne Jalkanen
>            Assignee: Janne Jalkanen
>             Fix For: 3.0
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> 3.0 should use JSR-170 (aka Java Content Repository) as the backend.  This allows our metadata model to be replaced with something far more efficient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (JSPWIKI-421) JCR backend

Posted by "Janne Jalkanen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JSPWIKI-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Janne Jalkanen resolved JSPWIKI-421.
------------------------------------

    Resolution: Fixed

Marking resolved then :)

> JCR backend
> -----------
>
>                 Key: JSPWIKI-421
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-421
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Core & storage
>            Reporter: Janne Jalkanen
>            Assignee: Janne Jalkanen
>             Fix For: 3.0
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> 3.0 should use JSR-170 (aka Java Content Repository) as the backend.  This allows our metadata model to be replaced with something far more efficient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JSPWIKI-421) JCR backend

Posted by "Janne Jalkanen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JSPWIKI-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Janne Jalkanen updated JSPWIKI-421:
-----------------------------------


Also add 

* Content renaming

> JCR backend
> -----------
>
>                 Key: JSPWIKI-421
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-421
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Core & storage
>            Reporter: Janne Jalkanen
>            Assignee: Janne Jalkanen
>             Fix For: 3.0
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> 3.0 should use JSR-170 (aka Java Content Repository) as the backend.  This allows our metadata model to be replaced with something far more efficient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JSPWIKI-421) JCR backend

Posted by "Janne Jalkanen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JSPWIKI-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Janne Jalkanen updated JSPWIKI-421:
-----------------------------------

    Remaining Estimate: 0h
     Original Estimate: 0h

Committed initial version in 3.0.0-svn-78.  At least the following things are still missing:

* AttachmentManager migration
* Removing PageProviders 
* Removing AttachmentProviders
* Removing unit tests referring to the individual providers
* Adding ehcache for Priha EhCachingProvider
* Making sure Sessions are cleared properly (ContentManager.discardModifications())
* Making sure that the facade methods in WikiEngine call save() properly.


> JCR backend
> -----------
>
>                 Key: JSPWIKI-421
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-421
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Core & storage
>            Reporter: Janne Jalkanen
>            Assignee: Janne Jalkanen
>             Fix For: 3.0
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> 3.0 should use JSR-170 (aka Java Content Repository) as the backend.  This allows our metadata model to be replaced with something far more efficient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.