-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 5.2.0.ER4
-
Fix Version/s: 5.2.0.ER5
-
Component/s: 3rd Party, Compatibility, Documentation
-
Labels:None
-
Affects:Documentation (Ref Guide, User Guide, etc.)
-
Release Notes Text:
-
Release Notes Docs Status:Documented as Known Issue
Smooks doesn't support some configurations with SOA-P 5.2 that are possible with SOA-P 5.1.
For example we can define EDI mapping model in two ways. The first[1] works on both versions, but second[2] can be used only with SOA-P 5.1.
The second configuration was in quickstarts last time in SOA-P 4.3 so it's probably not very important issue. But if customer uses this configuration on SOA-P 5.1 and will migrate, it will crash on SOA-P 5.2.
[1]
<edi:reader mappingModel="parse/edi-to-xml-order-mapping.xml" />
[2]
<resource-config selector="org.xml.sax.driver">
<resource>org.milyn.smooks.edi.SmooksEDIParser</resource>
<param name="mapping-model">/smooks_configs/parse/edi-to-xml-order-mapping.xml</param>
</resource-config>