On Aug 4, 2015, at 2:17 PM, Martin Gainty wrote:
>
> no org.glassfish.config.support.TranslatedConfigView never set matcher.to to be the max limit of your string
Why in the world should it? The "to" field within Matcher is internal.
The client can specify a region over which it wants to Match (regionStart and regionEnd), but by default these are set to 0 and the length of the string.
It's not the clients job to protect the Matcher from itself. If the client is specifically lying to the Matching (i.e. specifying a regionEnd that is longer than the text to match), then, you know, GIGO. "Don't do that".
No, this is a bug in the Matcher (or a UFO). Either a pattern is valid, or it's not (and a regex expression is loose enough that almost all patterns are valid, just, perhaps, not what you want -- different problem). If Matcher is walking off the end of the text, it's a bug in the Matcher. TranslatedConfigView isn't doing anything special with the Matcher that should cause it to fail. It's simply looking for properties to replace.
And this pattern is the same since 3.x.
Regards,
Will Hartung
(willh_at_mirthcorp.com)
--
This message, and any documents attached hereto, may contain confidential
or proprietary information intended only for the use of the addressee(s)
named above or may contain information that is legally privileged. If you
are not the intended addressee, or the person responsible for delivering it
to the intended addressee, you are hereby notified that reading,
disseminating, distributing or copying this message is strictly prohibited.
If you have received this message by mistake, please immediately notify us
by replying to the message and delete the original message and any copies
immediately thereafter. Thank you for your cooperation.