| Summary: | EBWS endpoints created without dependency | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Kevin Conner <kevin.conner> |
| Component: | Documentation | Assignee: | Dana Mison <dmison> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.3 IR3 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.3 CR1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-759 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-10-20 11:53:10 UTC | Type: | Task |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Link: Added: This issue is related to SOA-726 Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes] "The war file created to automatically expose ESB services through a webservice endpoint does not contain a dependency on the esb archive." This is a specific war file that ships in SOA for this purpose? filename? "the esb archive" in this context is the jbossesb.sar ? This is only an issue if "the esb archive has failed to deploy cleanly". In JBESB-1972 this was due to misconfiguration of, this would also be a factor for otherwise messed up deployments of the ESB into an existing JBossAS deployment? The ESB deployer automatically generates a war file for every .esb artifact that attempts to expose the ESB services through JBossWS. This war file *should* have the specific esb artifact as a dependency, to prevent deployment when the esb artifact fails, but cannot do so because of a bug in the JBossWS deployer. As a consequence it is possible to see the generated war file deployed even though the associated esb artifact has failed to deploy. Release notes updated: ESB Webservice EndPoint Deployment =========================== It is possible for the WebService EndPoints for an ESB service to successfully deploy even if the ESB service that it represents fails to deploy. This is due to the WAR archives automatically created by the ESB deployer not containing a dependency on the originating ESB archives. These dependancies should be included but have been disabled due to an issue in JBossWS. Additional information: http://jira.jboss.com/jira/browse/SOA-726 Verfied in CR1 |
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes Date of First Response: 2008-09-14 22:33:58 project_key: SOA This issue is related to SOA-726. The war file created to automatically expose ESB services through a webservice endpoint does not contain a dependency on the esb archive. The consequence of this is that the webservice endpoints can still be deployed even though the esb archive has failed to deploy cleanly. This needs to be documented as a known issue. The decision to remove the dependency on the esb was taken because of a problem with the JBossWS deployer. The deployer incorrectly assumes that the parent classloader has been created at the point where it is building the associated metadata. This leads to the following exception. java.lang.IllegalArgumentException: Runtime classloader cannot be null at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:55)