Bug 841491
| Summary: | WSRP: White spaces are required between publicId and systemId | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Michal Vanco <mvanco> |
| Component: | Portal | Assignee: | Default User <jbpapp-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.2.2.ER02 | CC: | epp-bugs, mvecera, theute |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-16 12:04:51 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
Michal Vanco
2012-07-19 07:23:50 UTC
Alessio Soldano <asoldano> made a comment on jira JBWS-3511 Also see [1] , this looks to me a duplicate of the issue already raised there. There's actually not a lot to do here to solve the problem, the issue is in the OASIS redirecting HTTP requests for their WSRP WSDL to HTTPS with an HTTP 302 response that includes an XML document that has a public ID but no system ID. Correct schema resolution is not possible in that case. As suggested / discussed in [1] and [2], the "solution" here is leveraging catalogs to avoid the need for going to the internet to resolve the WSRP wsdl & schemas. Depending on the jbossws stack in use (native or cxf based), that is done using either as explained in [2] (native stack) or using jax-ws-catalog.xml catalogs (cxf stack). Attached is an example of jaxws catalog that can be used to read the schemas/wsdl from the file system (but you can also use "classpath:/" to read from jars in the classpath). I've been successfully testing that using the zip wsrp-entity-fix.zip attached to [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=831445 [2] https://issues.jboss.org/browse/JBPAPP-9337 [3] Alessio Soldano <asoldano> made a comment on jira JBWS-3511 Also see [1] , this looks to me a duplicate of the issue already raised there. There's actually not a lot to do here to solve the problem, the issue is in the OASIS redirecting HTTP requests for their WSRP WSDL to HTTPS with an HTTP 302 response that includes an XML document that has a public ID but no system ID. Correct schema resolution is not possible in that case. As suggested / discussed in [1] and [2], the "solution" here is leveraging catalogs to avoid the need for going to the internet to resolve the WSRP wsdl & schemas. Depending on the jbossws stack in use (native or cxf based), that is done using either as explained in [2] (native stack) or using jax-ws-catalog.xml catalogs (cxf stack). Attached is an example of jaxws catalog that can be used to read the schemas/wsdl from the file system (but you can also use "classpath:/" to read from jars in the classpath). I've been successfully testing that using the zip wsrp-entity-fix.zip attached to [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=831445 [2] https://issues.jboss.org/browse/JBPAPP-9337 Alessio Soldano <asoldano> updated the status of jira JBWS-3511 to Resolved |