| Summary: | EPP 5.1.1.DEV02 fails to start against existing DB schema | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Martin Weiler <mweiler> |
| Component: | Portal | Assignee: | hfnukal <hfnukal> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.1.1.DEV02, 5.1.1.CR01 | CC: | hfnukal, mposolda, ndkhoi168, smumford, theute |
| Target Milestone: | --- | ||
| Target Release: | 5.1.1.DEV03, 5.1.1.GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-987 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-08-02 05:57:12 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Martin Weiler
2011-06-22 14:47:09 UTC
Good catch... The infamous JCR_CONFIG We have 2 choices: - Duplicate the file so that it woks for new and existing solutions - Document the workaround I would be tempted to duplicate and add a comment in the one embedded in the jar What about make update script for DB, it can search for wrong records and replace it. Patch upgrade should be as easy as possible (binary replacement). Unless *absolute* need. Link: Added: This issue relates to JBQA-4899 Release Notes Text: Added: JCR cache configuration was moved from jar file to folder in web to be editable. When upgrading form previous version of EPP, path to config is stored in database in JCR_CONFIG table. For backward compatibility, to avoid changing database, configuration files are duplicated in jar. If config changes in JCR cache are needed, its important to update or delete JCR_CONFIG table to use "war:" prefix instead of "classpath:". Release Notes Text: Removed: JCR cache configuration was moved from jar file to folder in web to be editable. When upgrading form previous version of EPP, path to config is stored in database in JCR_CONFIG table. For backward compatibility, to avoid changing database, configuration files are duplicated in jar. If config changes in JCR cache are needed, its important to update or delete JCR_CONFIG table to use "war:" prefix instead of "classpath:". Added: ORIGINAL TEXT: JCR cache configuration was moved from jar file to folder in web to be editable. When upgrading form previous version of EPP, path to config is stored in database in JCR_CONFIG table. For backward compatibility, to avoid changing database, configuration files are duplicated in jar. If config changes in JCR cache are needed, its important to update or delete JCR_CONFIG table to use "war:" prefix instead of "classpath:". UPDATED TEXT: The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from the /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.jcr.component.core-VERSION.jar to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr. This change prevented upgraded versions of JBoss Enterprise Portal Platform from starting with the path to the old JCR configuration files stored in the database JCR_CONFIG table. This issue has been resolved by retaining duplicates of the configuration files in the original jar. This corrects the issue and ensures backward compatibility, without the need to change the database. Note: As a result of this change, if configuration changes to the JCR cache are required, it is important that the JCR_CONFIG table be updated to use the "war:" prefix instead of "classpath:" (for example; file:war:/conf/jcr/jbosscache/local/config.xml). Updated file name in Release Note text as per advice from Honza Release Notes Text: Removed: ORIGINAL TEXT: JCR cache configuration was moved from jar file to folder in web to be editable. When upgrading form previous version of EPP, path to config is stored in database in JCR_CONFIG table. For backward compatibility, to avoid changing database, configuration files are duplicated in jar. If config changes in JCR cache are needed, its important to update or delete JCR_CONFIG table to use "war:" prefix instead of "classpath:". UPDATED TEXT: The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from the /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.jcr.component.core-VERSION.jar to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr. This change prevented upgraded versions of JBoss Enterprise Portal Platform from starting with the path to the old JCR configuration files stored in the database JCR_CONFIG table. This issue has been resolved by retaining duplicates of the configuration files in the original jar. This corrects the issue and ensures backward compatibility, without the need to change the database. Note: As a result of this change, if configuration changes to the JCR cache are required, it is important that the JCR_CONFIG table be updated to use the "war:" prefix instead of "classpath:" (for example; file:war:/conf/jcr/jbosscache/local/config.xml). Added: The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from the /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.portal.component.common-<version>.jar to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr. This change prevented upgraded versions of JBoss Enterprise Portal Platform from starting with the path to the old JCR configuration files stored in the database JCR_CONFIG table. This issue has been resolved by retaining duplicates of the configuration files in the original jar. This corrects the issue and ensures backward compatibility, without the need to change the database. Note: As a result of this change, if configuration changes to the JCR cache are required, it is important that the JCR_CONFIG table be updated to use the "war:" prefix instead of "classpath:" (for example; file:war:/conf/jcr/jbosscache/local/config.xml). Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Release Notes Text: Removed: The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from the /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.portal.component.common-<version>.jar to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr. This change prevented upgraded versions of JBoss Enterprise Portal Platform from starting with the path to the old JCR configuration files stored in the database JCR_CONFIG table. This issue has been resolved by retaining duplicates of the configuration files in the original jar. This corrects the issue and ensures backward compatibility, without the need to change the database. Note: As a result of this change, if configuration changes to the JCR cache are required, it is important that the JCR_CONFIG table be updated to use the "war:" prefix instead of "classpath:" (for example; file:war:/conf/jcr/jbosscache/local/config.xml). Added: The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from the /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.portal.component.common-<version>.jar to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/. This change created problems when attempting to start upgraded versions of JBoss Enterprise Portal Platform that had the original file path stored in the JCR_CONFIG table in the database. To resolve the issue, duplicates of the configuration files have been retained in the original location. This also ensures backward compatibility, without the need to change the database. Note: After this change, if configuration changes to the JCR cache are required, it is important that the JCR_CONFIG table be updated to use the "war:" prefix instead of "classpath:" (for example; file:war:/conf/jcr/jbosscache/local/config.xml). |