Bug 881924
| Summary: | RollupClone - org.jboss.internal.soa.esb.message.format.xml.marshal.SerializedMarshalUnmarshalPlugin.unmarshal throws ClassNotFoundException when WSDL is not available to SoapUI | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Rick Wagner <rwagner> |
| Component: | JBossESB | Assignee: | Pavel Drozd <pdrozd> |
| Status: | CLOSED UPSTREAM | QA Contact: | Pavel Drozd <pdrozd> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.3.0 GA | CC: | mvecera |
| Target Milestone: | ER4 | Flags: | pdrozd:
needinfo+
|
| Target Release: | 5.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The soapui-1.7.1.jar is not included in the jboss-as/server/<configuration>/deployers/esb.deployer/lib/ directory resulting in a ClassNotFoundException. To workaround this issue, the user can add the JAR file to this directory manually.
Manual instructions:
Copy the soapui-1.7.1.jar from jboss-as/server/<configuration>/deploy/soapui-client.sar/lib to jboss-as/server/<configuration>/deployers/esb.deployer/lib directory.
Note: The platform with this modification has been tested only for the purpose of verifying issue BZ-881924.
|
Story Points: | --- |
| Clone Of: | 870426 | Environment: | |
| Last Closed: | 2025-02-10 03:27:04 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: | |||
| Bug Depends On: | 870426 | ||
| Bug Blocks: | |||
|
Description
Rick Wagner
2012-11-29 19:20:10 UTC
*** Bug 876284 has been marked as a duplicate of this bug. *** *** Bug 870426 has been marked as a duplicate of this bug. *** The soapui-1.7.1.jar is not included in the jboss-as/server/<configuration>/deployers/esb.deployer/lib/ directory. Verified in 531ER3 If this workaround will be used, in the documentation should be at least following: 1. Instruction from where the jar file should be copied 2. Note that the platform with the change has been tested only for this case Pavel, Would you be able to update the Doc Text with the appropriate instructions please? Thanks, Ben This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |