| Summary: | Incorrect parsing of jboss-service.xml | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Pavel Macik <pmacik> |
| Component: | JBossAS | Assignee: | Default User <jbpapp-maint> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0 GA | ||
| Target Milestone: | --- | ||
| Target Release: | 5.2.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2042 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-07 08:36: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: | |
Link: Added: This issue depends JBAS-7953 Link: Removed: This issue depends JBAS-7953 Link: Added: This issue depends JBPAPP-4136 This was triaged for SOA 5.1.0. This will not be in SOA 5.1.0 Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2042 The jboss-service.xml file was being parsed incorrectly. The parser was not ignoring white space. A code change has been applied and, as a result, this file is now parsed correctly. Verified in 520ER4 |
project_key: SOA In the server/<config>/conf/jboss-service.xml file there is mbean's attributes configured as following: <server> <mbean ... name="jboss:service=Naming" ...> ... <attribute name="BindAddress"> <value-factory bean="ServiceBindingManager" method="getStringBinding"> <parameter>jboss:service=Naming</parameter> <parameter>Port</parameter> <parameter><null/></parameter> </value-factory> </attribute> ... </mbean> ... </server> This exact configuration is fine. But while I change element formatting as follows, the </null> parameter parsing fails. ... <attribute name="BindAddress"> <value-factory bean="ServiceBindingManager" method="getStringBinding"> <parameter>jboss:service=Naming</parameter> <parameter>Port</parameter> <parameter> <null/> </parameter> </value-factory> </attribute> ... It seems the parser that parses this file doesn't ignore white-spaces around the <null/> element and the mbean behaves in different way.