Databases
StackOverflow2013
Postsdbo
POConfigs loaded in Mule functional tests throw errors, but runs outside of a test
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POConfigs loaded in Mule functional tests throw errors, but runs outside of a test
    primarykey
    data
    text
    <p>I have a strange situation where Mule configs loaded in Mule functional tests throw errors of the sort below from flows with vm's. The annoying thing is this flow runs perfect as a mule application and sometimes by tweaking with mule studio I can get the test to run, almost randomly.</p> <pre><code>&lt;flow name="simpleOutBoundFlow"&gt; &lt;vm:inbound-endpoint path="testV" name="test" /&gt; &lt;logger level="ERROR" message="blah #[payload]" /&gt; &lt;foo:outbound config-ref="fooOutbound" doc:name="baa" /&gt; &lt;/flow&gt; </code></pre> <p>the error occurs at the vm: line and says something like</p> <blockquote> <p>org.mule.api.config.ConfigurationException: Line 21 in XML document from URL [file:/D:/config.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 21; columnNumber: 18; cvc-complex-type.2.4.a: Invalid content was found starting with element 'vm:inbound-endpoint'. One of '{"<a href="http://www.mulesoft.org/schema/mule/core" rel="nofollow">http://www.mulesoft.org/schema/mule/core</a>":annotations, "<a href="http://www.mulesoft.org/schema/mule/core" rel="nofollow">http://www.mulesoft.org/schema/mule/core</a>":description, "<a href="http://www.mulesoft.org/schema/mule/core" rel="nofollow">http://www.mulesoft.org/schema/mule/core</a>":abstract-message-source, "<a href="http://www.mulesoft.org/schema/mule/core" rel="nofollow">http://www.mulesoft.org/schema/mule/core</a>":abstract-inbound-endpoint, "<a href="http://www.mulesoft.org/schema/mule/core" rel="nofollow">http://www.mulesoft.org/schema/mule/core</a>":abstract-message-processor, "<a href="http://www.mulesoft.org/schema/mule/core" rel="nofollow">http://www.mulesoft.org/schema/mule/core</a>":abstract-outbound-endpoint, "<a href="http://www.mulesoft.org/schema/mule/core" rel="nofollow">http://www.mulesoft.org/schema/mule/core</a>":abstract-mixed-content-message-processor, "<a href="http://www.mulesoft.org/schema/mule/core" rel="nofollow">http://www.mulesoft.org/schema/mule/core</a>":response}' is expected. (org.mule.api.lifecycle.InitialisationException) at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:52)</p> </blockquote> <p>Any ideas? Really strange one for me.</p> <p>nb: the foo:outbound comes from a devKit update site I generated with the maven devkit archtype</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNikos
    1. USNikos
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. CODo you have the namespace for VM declared in your configuration?
      singulars
      1. POConfigs loaded in Mule functional tests throw errors, but runs outside of a test
      1. USSeba
    2. CO@Seba, yes its there, otherwise when I ran it ass a mule app it would Error
      singulars
      1. POConfigs loaded in Mule functional tests throw errors, but runs outside of a test
      1. USNikos
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload