[jboss-as7-dev] Cryptic Error Messages
Brian Stansberry
brian.stansberry at redhat.com
Thu Feb 3 13:08:29 EST 2011
On 2/3/11 6:06 AM, Darran Lofthouse wrote:
> On 02/03/2011 11:59 AM, David M. Lloyd wrote:
>> On 02/03/2011 05:08 AM, Darran Lofthouse wrote:
>>> The first of these errors was reported because a subsystem had not read
>>> all of it's configuration but the reported error gives the impression
>>> there may be a problem with the actual XML.
>>
>> Well, a bug in the XML parser will almost always look like an XML
>> parsing error. The only fix for that is to just not have any XML
>> parsing bugs.
>
> I am wondering for this one if there is any way we can detect that a
> subsystem did not read all of the elements under it's subsystem element
> - if we could do that we may be able to report an error along the lines
> of reporting that a specific subsystem has not read all the child content.
>
I think that should be doable, just by calling XMLStreamReader.getName()
and validating that it returns the QName for the <profile> element.
> Regards,
> Darran Lofthouse.
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
More information about the jboss-as7-dev
mailing list