[TREQ-21] Within an OSGi environment, URLApplicationResource must throw a FileNotFoundException instead of IOException when a resource is not found

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.7
• Assignee: Michael Semb Wever
• Reporter: Roland Hauser
• Created: 07/Jun/17 09:20
• Updated: 04/Sep/17 11:12
• Resolved: 04/Sep/17 11:12

Description

Otherwise, BaseLocaleUrlDefinitionDAO does not load resources correctly, see TILES-589.

In general, if the URL#openConnection method of a local protocol is called, an IOException should be transformed into a FileNotFoundException as it implies that the resource does not exist. This should be avoided for remote protocols because an IOException can mean something different, for instance that the network connection could not be established.

By default any protocol is considered to be local, except of

• ftp
• http
• https
• mailto
• netdoc
• Any additional protocol specified via system parameter -Dtiles.remoteProtocols

Issue Links

• blocks: TILES-589 IOException occurs when BaseLocaleUrlDefinitionDAO tries to load a non-existing resource within an OSGi environment