| Summary: | Sample extension datasource uses local-tx-datasource type | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Miroslav Cupák <mcupak> |
| Component: | Portal, Portal Packaging | Assignee: | Nobody <nobody> |
| Status: | VERIFIED --- | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.2.1.ER03 | CC: | epp-bugs, theute, tkyjovsk |
| Target Milestone: | --- | ||
| Target Release: | 5.2.2.ER01 | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
It was discovered that the sample datasource file for portal extensions
<filename>jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml</filename> specifies the incorrect datasource type for IDM. It should be no-tx-datasource for IDM and
local-tx-datasource for JCR, instead of local-tx-datasource for both directive blocks. To work around the issue, define the datasource type manually, following the guidelines in this Release Note.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 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
Miroslav Cupák
2012-04-02 15:21:14 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
It was discovered that the sample datasource file for portal extensions
<filename>jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml</filename> specifies the incorrect datasource type for IDM. It should be no-tx-datasource for IDM and
local-tx-datasource for JCR, instead of local-tx-datasource for both directive blocks. To work around the issue, define the datasource type manually, following the guidelines in this Release Note.
Verified again at 5.2.2 CR01 |