java.lang.IllegalStateException

java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName

Solutions on the web12730

  • java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName
  • java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName
  • java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName
  • Stack trace

    • java.lang.IllegalStateException: java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName at org.apache.tuscany.sca.node.impl.NodeImpl.start(NodeImpl.java:178) at org.apache.tuscany.sca.host.webapp.WebAppHelper.createAndStartNode(WebAppHelper.java:195) at org.apache.tuscany.sca.host.webapp.WebAppHelper.init(WebAppHelper.java:118) at org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:56) at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:281) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:262) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:107) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4656) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5309) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName at javax.xml.namespace.QName.<init>(QName.java:244) at javax.xml.namespace.QName.<init>(QName.java:188) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.read(CompositeProcessor.java:206) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.read(CompositeProcessor.java:124) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.read(DefaultStAXArtifactProcessorExtensionPoint.java:296) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.read(ExtensibleStAXArtifactProcessor.java:170) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.read(CompositeDocumentProcessor.java:119) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.read(CompositeDocumentProcessor.java:92) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.read(CompositeDocumentProcessor.java:49) at org.apache.tuscany.sca.contribution.processor.DefaultURLArtifactProcessorExtensionPoint$LazyURLArtifactProcessor.read(DefaultURLArtifactProcessorExtensionPoint.java:287) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.read(ExtensibleURLArtifactProcessor.java:112) at org.apache.tuscany.sca.contribution.processor.impl.ContributionContentProcessor.read(ContributionContentProcessor.java:158) at org.apache.tuscany.sca.contribution.processor.impl.ContributionContentProcessor.read(ContributionContentProcessor.java:65) at org.apache.tuscany.sca.contribution.processor.DefaultURLArtifactProcessorExtensionPoint$LazyURLArtifactProcessor.read(DefaultURLArtifactProcessorExtensionPoint.java:287) at org.apache.tuscany.sca.deployment.impl.DeployerImpl.loadContribution(DeployerImpl.java:762) at org.apache.tuscany.sca.node.impl.NodeFactoryImpl.loadContributions(NodeFactoryImpl.java:350) at org.apache.tuscany.sca.node.impl.NodeImpl.load(NodeImpl.java:198) at org.apache.tuscany.sca.node.impl.NodeImpl.start(NodeImpl.java:118) ... 16 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago