[CAMEL-14748] Unmarshal ZIP w/ error handling in Camel 3.x

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.1
• Fix Version/s: 3.2.0
• Component/s: camel-zipfile
• Estimated Complexity: Unknown
• Assignee: Omar Al-Safi
• Reporter: Gerald Kallas
• Created: 20/Mar/20 07:49
• Updated: 26/Mar/21 11:44
• Resolved: 20/Mar/20 16:07

Description

I've following route
 
 

<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0">
 <camelContext xmlns="http://camel.apache.org/schema/blueprint">
   <route>
     <from uri="file:/var/files/in?include=.*\.zip" />
     <unmarshal>
       <zipfile />
     </unmarshal>
     <log message="body: ${in.body}" />
     <to uri="file:/var/files/out" />
   </route>
 </camelContext>
</blueprint>

 
When I'm sending a corrupted ZIP file to this route I'd expect a Camel runtime error. This won't happen, I'm only getting an empty body.

Issue Links

• is cloned by: CAMEL-16410 camel-zipfile - Unmarshal ZIP without error handling in Camel 3.8.0 when using split
• relates to: CAMEL-14752 Unmarshal TAR w/ error handling in Camel 3.x
• links to: GitHub Pull Request #3657