Do we have any plans to capture cryptic error messages experienced while
working with AS7 so we can review if there are better ways the problem
can be reported?
Over the past week I have experienced the two errors at the end of this
e-mail.
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.
The second error although claiming an extension could not be found was
actually because the extension could not be loaded as the module
containing a class used by the extension was not referenced from the
module.xml.
Regards,
Darran Lofthouse.
===== 1 =====
Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[142,91]
Message: Unexpected element '{urn:jboss:domain:osgi:1.0}configuration'
encountered
at
org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:61)
at
org.jboss.as.controller.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:383)
===== 2 =====
10:35:08,866 ERROR [org.jboss.msc] MSC-00001: Failed to start service
jboss.as.server-controller: org.jboss.msc.service.StartException in
service jboss.as.server-controller: Failed to start service
at
org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1207)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_23]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_23]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
Caused by: java.util.ServiceConfigurationError:
org.jboss.as.controller.NewExtension: Provider
org.jboss.as.webservices.NewWSExtension not found
at java.util.ServiceLoader.fail(ServiceLoader.java:214) [:1.6.0_23]
at java.util.ServiceLoader.access$400(ServiceLoader.java:164) [:1.6.0_23]
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:350)
[:1.6.0_23]