Bug 900491 (JBPAPP6-930)
| Summary: | Error message when deploying -service.xml doesn't list what component has the error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | dereed | ||||
| Component: | Microcontainer and Deployers | Assignee: | Eduardo Martins <emartins.redhat> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.0.0 | CC: | brian.stansberry, dereed, emartins.redhat, jason.greene, rhatlapa, twells, vrastsel | ||||
| Target Milestone: | --- | ||||||
| Target Release: | EAP 6.0.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-930 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-11-20 08:44:24 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: | |||||||
| Attachments: |
|
||||||
|
Description
dereed
2012-05-21 18:07:30 UTC
Hi Eduardo can you take a look at this? sure Dennis, are you able to attach the test ear you used? I get no deployment error when bundling a test-service.xml in an EAR, without application.xml. Perhaps this is already fixed in 7.1 branch, or there is a specific EAR setup that raises the issue, waiting for Dennis clarification about the EAR used. Attachment: Added: test.ear Attached test.ear. It contains just a test-service.xml, which it tries to deploy from jboss-app.xml (which worked in previous EAP versions but is no longer supported in EAP 6). Note that the ear isn't valid, as application.xml must contain at least one module, but this one doesn't. But it still triggers the issue this JIRA is about, so I didn't bother adding a dummy module to it. Git Pull Request: Added: https://github.com/jbossas/jboss-as/pull/2791 The linked PR changes the behaviour of the deployer, there is no deployment error, instead it ignores any module which type is not supported, such as the legacy service, and display a warning log message. After discussion with Kabir and Stuart, I'm changing PRs to throw error, instead of ignore. PRs merged by Brian Verified on EAP 6.0.1 ER2 Updated release notes fields Release Notes Docs Status: Added: Not Yet Documented Writer: Added: sgilda Release Notes Docs Status: Removed: Not Yet Documented Writer: Removed: sgilda Docs QE Status: Removed: NEW Verified for eap 6.0.1-ER3 |