[
https://issues.apache.org/jira/browse/DELTASPIKE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408814#comment-13408814
]
Mark Struberg commented on DELTASPIKE-222:
------------------------------------------
I don't yet get the use case. This is purely for giving the user the option to
'name' additional resource 'locations'.
If it gets more complicated, e.g. in JSF, then you need an own MessageResolver
anyway. Thats what we will provide for sure in the JSF module. A
MessageResolver which first looks in all the JSF registered resource locations,
and then delegates further to the DefaultResourceResolver...
Such functionality would be much too complex for a 'MessageSource'
implementation anyway.
> Add possibility to set base path
> --------------------------------
>
> Key: DELTASPIKE-222
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-222
> Project: DeltaSpike
> Issue Type: New Feature
> Components: I18n-Module
> Affects Versions: 0.2-incubating
> Reporter: Thomas Herzog
> Fix For: 0.3-incubating
>
>
> Add the possibility to set the base path, means the path to the properties
> file.
> Now they are assumed to be at same level as the @MessageResource annotated
> interface is, in fact within the same package.
> Maybe someone wants to put his resource bundles at
> /META-INF/resources/*.properties.
> With cal10n it was possible to set the Base with @Base("/META-INF/resources")
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
