Tools

piotras said

piotras  

What JCR really misses and Midgard2 supports well:

5 comments

piotras posted to #midgard 06.07.2011 (en)

5 comments

Bottom

piotras  

  • replication
    • metadata
    • no staging/live for storage layout (see replication)
    • OOP content design which can not be represented by registered classes
      • * The tree by default (especially huge) is very bad UX
The last one is probably for these nerds which are so excited the some visual tree is built and can scroll and scroll and scroll...

piotras commented on posted to #midgard 06.07.2011 (en)

bergie  

JCR has replication capabilities in the XML import and export, though yes, necessary metadata is missing. But you can implement that by having the right mixins. Shame it isn't a default, though

Staging/live is just a question of copying appropriate stuff between workspaces.

bergie commented on posted to #midgard Paris 10 Entrepôt 07.07.2011 (en)

piotras  

@bergie One would say there's the same replication between MySQL or PostgreSQL ;) Staging/live on storage layer is different thing. Without proper storage models you can not upgrade production after dev improvements. Anyway, I just try to keep in one place poor features of JCR :)

piotras commented on posted to #midgard 07.07.2011 (en)

bergie  

BTW, this proposal would make JCR workspaces work a lot more like Midgard workspaces.

bergie commented on posted to #midgard Paris 10 Entrepôt 08.07.2011 (en)

piotras  

jcr:createdBy being not a reference is a bad, bad idea

piotras commented on posted to #midgard 30.07.2011 (en)

Login or register to leave a comment

Publicity
These messages are public and can be seen by anyone.