-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there anyway to re-classify this an an enhancement so it's not lost in the 3.X thread?
Mike Barber (JIRA) wrote: > [ > http://issues.apache.org/jira/browse/TAPESTRY-893?page=comments#action_12371610 > ] > > Mike Barber commented on TAPESTRY-893: > -------------------------------------- > > I suspected as much....the page doesn't clearly indicate that 4.0 is the > reference version. Oh well. From what I understand, coding a custom engine > is not a trivial process. > > I retract my claim that this is a bug, but it seems to me that it would not > take much to implement in 3.x. Basically, when you access the page catalog, > if the getMessage() fails, just look for an application catalog. Maybe just > a few lines of IO code. This would allow me to have a master application > catalog, and small page catalog that could override a few messages and add a > few new messages. > > I coded a workaround in my own code with custom ValidFields and such, but > it's really not an acceptable way to go about it. It requires my fellow devs > to do too much, and is a maintenance quagmire. > > If the fix/enhancement is simple (I suspect so), this would be a great > improvement to Tapestry 3 (as we can see in Tapestry 4). > >> Application Catalog for i18n does not work >> ------------------------------------------ >> >> Key: TAPESTRY-893 >> URL: http://issues.apache.org/jira/browse/TAPESTRY-893 >> Project: Tapestry >> Type: Bug >> Components: Framework >> Versions: 3.0.3 >> Environment: Windows 2000, Unix >> Reporter: Mike Barber > >> If I remove all page-specific catalogs (.properties files) and have an >> application catalog (myapplication.properties) in WEB-INF, Tapestry does not >> detect it. It is documented as working, but it does not. I am forced to >> have page catalogs. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEIu5AaCoPKRow/gARAmOQAKCyyskg+HLscbyG6/oirwEvLywA/QCdGWI5 4Jqxw7R2ynfhNa9qS4mNsks= =eUpp -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
