You definitely want to compare because there is new code in James for
handling the file repositories. There are two lines that need to be changed
in config.xml from older versions of James if you use file repositories.
--- Noel
-----Original Message-----
From: Chris Means [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 20, 2003 23:47
To: James Users List
Subject: RE: updating my james version
It was that "simple" for me.
You will probably want to compare the new config.xml to your config.xml so
that you can see what blocks need to be added, or which ones have new or
changed parameters.
Other than that, I use MySQL as the repository, so the changeover was a
snap. I don't know, but assume it is true for file based to.
-Chris
> -----Original Message-----
> From: Mike Danifo [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 20, 2003 10:27 PM
> To: [EMAIL PROTECTED]
> Subject: updating my james version
>
>
> Hello,
> given the recent announcements about new james versions, I thought I'd
> ask this question.
> It may seem like an obvious question to james veterans, but as a newbie,
> I just have to ask:
>
> what is typically involved in updating a version of james?
> can I get away with just copying over the config.xml and/or
> environment.xml from the older version?
> do I have to manually replicate the changes in these 2 files from one
> version to the next?
>
> I have a pretty basic setup, so I don't have to worry about any sql auth
> stuff, etc.
>
> thanks
>
> -Mike
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
