Yes. Port your templates to 2.1.5, bootstrap it, drop unused sample
data from the JCR, set it up as a subscriber in your 2.1RC3
environment. Activate your config, users, userroles, website stuff to
the 2.1.5. After that, it can be backed up using the export tool in
2.1.5 to create new bootstrap xml files.
--David
Christian P. Praher wrote:
Hi David,
thanks a lot for your reply - We've just decided to do that switch to 2.1.5.
Do you mean by activation that we have to build up a new magnolia 2.1.5.
parallel to our existing one(s) and activate our content from the 2.1 RC 3
instance into the 2.1.5 cms?
Would be great if I could come back to you on that issue when we're actually
doing the upgrade.
Thanks again,
chris
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 13. September 2006 12:00
An: [email protected]
Betreff: Re: [magnolia-user] AW: [magnolia-user] Question: Magnolia 2.1 RC 3
Availability
I believe you would achieve a fair performance improvement with 2.1.5.
Jackrabbit (the JCR implementation) in your version was still very much
in development.There was also movement away from the file system store.
Memory fades on this but the templates should work as is. You will have
to use activation to move your repository content from 2.1 RC3 to 2.1.5 .
--David
Christian P. Praher wrote:
Hi David,
the reason for this is that we started our project in July/August 2005 and
back then this was the most current release.
Could we expect a big benefit from changing to 2.1.5.?
Also, could there be any incompatibilities concerning templating or so, or
shouldn't be that an issue?
chris
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 13. September 2006 11:26
An: [email protected]
Betreff: Re: [magnolia-user] Question: Magnolia 2.1 RC 3 Availability
Current release is 2.1.5. Is there a reason for using 2.1RC3?
-David
Christian P. Praher wrote:
Hi everyone,
we're running a commercial site (with newsletter functionality) that
should
soon be expanded to a shop-system on top of magnolia 2.1 RC 3. Basically
everything works fine and I like Magnolia and Jackrabbit (with its
intuitive
XML-Paths) very much.
The only severe problem that we're having at the moment is that we're
having
an extremely low availability. Every 5 or 6 hours in seems as if the
server
(tomcat) completely shuts down. The very bad thing is, that we can't find
any information in the Catalina.out-Log. Could this be a deadlock-issue
or
something like this? Our JVM is 1.5 - could that be a problem?
Does anyone have a clue what this might be? We're currently persisting
Jackkrabbit to the file-system. Has anyone running a larger application
have
any experiences on that? Is it possible to run a large system just with
filesystem persistence or is there a preferred, more robust way, e.g.
persistence to a DB?
Thanks for any information, any comment would be highly appreciated since
you know availability is THE key issue for a online shop.
Thanks again,
chris
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
