| Summary: | Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Taro Yasuma <tyasuma> |
| Component: | JBossESB | Assignee: | Nobody <nobody> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.3 GA | CC: | imamura.yousuke, rwagner |
| Target Milestone: | --- | ||
| Target Release: | FUTURE | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1264 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Task | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Taro Yasuma
2009-04-01 03:10:22 UTC
Link: Added: This issue depends JBESB-2444 The other support case opened: https://enterprise.redhat.com/issue-tracker/281654 This is a jUDDI v2 issue, we do not know whether it is still relevant in the jUDDI v3 codebase. Do we know if this issue occurs in 5.0? We will need to document it in the Release Notes if so. Thanks. As per IRC discussion with Len Di Maggio, this won't be in the 5.0GA Release Notes as version number does not affect 5.0: <ldimaggi_> dlesage, I vote "out" <ldimaggi_> dlesage, If the affects != 5.0, it's out We only know for certain that the issue exists in juddi v2. Juddi v3 uses hibernate for its persistence layer and should handle this in a better way. Link: Added: This issue is related to SOA-2119 This has now been confirmed in juddi v3 deployments Rick reviewing old JIRAs. JBESB-2444 still open, but this might not exist with juddi3. Left Open. |