Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 2.0.0-RC1
-
Fix Version/s: 2.0.0-RC2
-
Component/s: Build: Maven
-
Labels:None
-
User impact:Low
-
Similar Issues:
MULE-3330mule-transport-archetype is not up to date with the latest APIMULE-2451mule-transport-archetype has invalid method signature for overriding AbstractPollingMessageReceiverMULE-3409A few issues with the transport archetypeMULE-5209mule-project-archetype generates a sample configuration file that has an invalid namespace for Mule coreMULE-4281archetypes generate test classes with wrong package nameMULE-5750Test generated by mvn archetype fails with assertion errorMULE-4981Broken link generated by transport archetypeMULE-5172mule-catalog-archetype has no tests, generates broken codeMULE-4473Review archetypes for 3.xMULE-4006Add a readme to the generated contant of the project-archetype
Description
The resulting functional test configuration xml doesn't seem to be validating. The functional test component was placed above the inbound-router, which it disliked (seems to be in an <xsd:sequence> of inbound-router, abstract-component, outbound-router,...)
Secondly, the functional test component has this block therein:
<properties> <spring:entry key="addReceived" value="true"/> </properties>
Whereas the XML validator expects (abstract-object-factory?, binding*).
This was discussed on the mailing list – doesn't seem to show up in Nabble yet.
Issue Links
| Duplicate | |||
|---|---|---|---|
|
|||