I was thinking about it too. Maybe around line 479 we could have something like "if bundle is null
and resource name doesn't contain '.xml', append '.xml' to resource name and call
UtilResourceBundle.getBundle(...) again."
-Adrian
Scott Gray wrote:
I had an idea on that, I'll put it down in code and see if it looks any
good. I'll send a patch here if works out.
Regards
Scott
On 03/01/2008, Adrian Crum <[EMAIL PROTECTED]> wrote:
Scott Gray wrote:
Ok got it (finally) thanks for persevering , perhaps we'll need to
detail
this in a readme in the config folders otherwise we'll get endless
questions
on the user list. I'll take care of when I get a chance.
Regards
Scott
Well, I'd still like to see the process change so it's less confusing. The
only component being
affected right now is the Example component. Maybe we can come up with a
better resolver strategy
before the custom xml format is more widely adopted.
In other words, the behavior you expected at the start should work. We
just have to figure out how
to make it work that way.
-Adrian
