| Summary: | Console file replacement breaks standalone runtime | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Julian Coleman <jcoleman> |
| Component: | Build Process | Assignee: | Mike Brock <cbrock> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.2 CP02 | CC: | rruss |
| Target Milestone: | --- | ||
| Target Release: | 4.2 CP02 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-560 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
Standalone only
|
|
| Last Closed: | 2008-06-06 12:48:50 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: | |
The replacement of the management-web/web.xml file doesn't appear to be the problem. If the web.xml from the ESB repository is copied to jboss-as/tools/console/management-web/ then the standalone server still fails with the same error. Also, the SOA-P build only appends the console authentication and doesn't change anything else in this file. So, is the problem in the SOA-P console code or in the way that the servlet is deployed? The servlet does not exist, which is why it was removed from the web.xml file. This was the only location that referred to it. I am going into the office today to meet Trev, will let you know what is going wrong once I see the build in action. Fixed with revision 1305 of: build-tools/builders/soa/p-consoles/esb/management-web/web.xml which aligns the SOA-P version with the ESB version. |
Date of First Response: 2008-06-06 04:43:36 project_key: SOA Run standalone SOA and see: 16:40:19,297 ERROR [ContainerBase] Error loading WebappClassLoader delegate: false repositories: ----------> Parent Classloader: java.net.FactoryURLClassLoader@14f2dff org.jboss.soa.esb.monitoring.server.BeanRegistrationServlet java.lang.ClassNotFoundException: org.jboss.soa.esb.monitoring.server.BeanRegist rationServlet in the log file/console output. kconner pointed out that there has been a change here so that this is now a proper servlet. The SOA-P build does not take this change into account - the change is to the file: management-web/web.xml which is overwritten during the console build process. This may also affect the embedded version. This needs checking.