| Summary: | Unable to deploy bpel quickstarts on signed SOA-P. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Marek Baluch <mbaluch> | ||||
| Component: | Build Process, Examples | Assignee: | Gary Brown <gary.pi4tech> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 5.1.0.ER2 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.1.0 GA | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-2366 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-02-18 01:47:55 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: | |||||
| Attachments: |
|
||||||
|
Description
Marek Baluch
2010-10-01 10:25:20 UTC
Attachment: Added: server.log Hi Marek - What changed between ER1 and ER2? I assume the quickstarts ran ok in ER1? Changed the package used for the generated Web Service endpoint. Will co-ordinate with productisation team on verifying the fix in the SOA-P build. Link: Added: This issue is a dependency of RIFTSAW-293 Fix has been applied, and tested locally. Will be part of next tagged version when requested by productisation or QE. Verified on SOA-P 5.1 ER5 Temporarily reopening to update release note info. Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/RIFTSAW-293 BPEL quick starts would fail due to an exception. An error message would state that "signer information does not match signer information of other classes in the same package." This happened when Riftsaw was deployed as a signed installation, because the service end-point created when a a BPEL process was deployed was unsigned. To fix this problem, the web service package has been renamed. Users will no longer encounter the exception. this is the first time we have shipped this so it does not have to be documented with resolved issues in the release notes Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Not Required |