ENGAGE-356: Message Bundles are not being located for the standalone (war file) version, for services using spouts

Metadata

Source
ENGAGE-356
Type
Bug
Priority
Blocker
Status
Closed
Resolution
Fixed
Assignee
Jess Mitchell
Reporter
Justin Obara
Created
2010-02-08T17:26:52.000-0500
Updated
2014-03-03T14:12:32.294-0500
Versions
N/A
Fixed Versions
  1. 0.3b
Component
  1. Kettle

Description

Message Bundles are not being located for the standalone (war file) version, for services using spouts.

This means that the default strings will appear and the component will not be internationalized.

It appears that this may have something to do with the path rewriting as it is working fine in the local version.

Comments

  • Justin Obara commented 2010-02-08T17:27:34.000-0500

    Bug Parade Engage 0.3

  • Antranig Basman commented 2010-02-12T19:21:15.000-0500

    I am investigating this, but currently finding this working on a standalone build on Windows.

  • Antranig Basman commented 2010-02-13T02:17:35.000-0500

    Apparently an issue due to spurious removal of leading "/" in a pathname when roundtripping through canonicalisation functions. Believed resolved at rev 9397

  • Antranig Basman commented 2010-02-18T12:55:34.000-0500

    Now appears fixed on the daily build site by the commit at 9426.