Bug 779571 (SOA-1947)
Summary: | JDBC Exception thrown when deploying a jboss esb service which has it's description attribute set to an empty String. | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Marek Baluch <mbaluch> |
Component: | JBossESB, Deployment, Examples, jUDDI - within SOA | Assignee: | Kevin Conner <kevin.conner> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.0.0 CR1 | ||
Target Milestone: | --- | ||
Target Release: | 5.1.0 GA | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://jira.jboss.org/jira/browse/SOA-1947 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-02-11 06:16:33 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: | |
Embargoed: |
Description
Marek Baluch
2010-02-11 13:07:19 UTC
Link: Added: This issue depends JBESB-3180 We already work around a similar issue for the service binding EPRs, but it would be nicer if the juddi integration could handle this cleanly. As Kevin commented this is a jUDDI issue therefore adding also "jUDDI - withing SOA" component. This is a candidate for SOA 5.1.0. Not committed. This is not a blocker for SOA 5.1.0 Updated in the ESB codebase. Writer: Added: dlesage Verified on ER6. Temporarily reopening to update release note info. Release Notes Docs Status: Added: Documented as Resolved Issue Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3180 If the user deployed a JBoss ESB service for which the description attribute was set to "", an exception would occur when the service was registered in jUDDI if the Oracle10g database was being used. This was caused by a problem with jUDDI. To bypass it, the ESB has been changed to ensure that a service description is present. Release Notes Text: Removed: https://issues.jboss.org/browse/JBESB-3180 If the user deployed a JBoss ESB service for which the description attribute was set to "", an exception would occur when the service was registered in jUDDI if the Oracle10g database was being used. This was caused by a problem with jUDDI. To bypass it, the ESB has been changed to ensure that a service description is present. Added: https://issues.jboss.org/browse/JBESB-3180 If the user deployed a JBoss ESB service for which the description attribute was set to "", an exception would occur when the service was registered in jUDDI if the Oracle10g database was being used. This was caused by a problem with jUDDI. To bypass this issue, the ESB has been changed. It now ensures that a service description is present. |