I created a bug (https://issues.apache.org/jira/browse/TAP5-892).
So when I use tapestry-spring-5.0.18 with Tapestry 5.1.0.5, it works fine.
Whatever the problem is, it seems to have been introduced in the new version of
tapestry-spring. Hopefully, this can get fixed soon. :)
I'm trying to upgrade to Tapestry 5.1 from 5.0.18. The Select field component
is giving me some errors.
I'm using a Spring application context that is externally maintained
(tapestry.use-external-spring-context) and have 4 instances of java.util.Locale
(named locale_DE,
locale_FR, locale_UK,
. It
wouldn't be ideal to only do a partial upgrade but I'll try it until I get any
replies.
- Original Message
From: Dave Greggory davegregg...@yahoo.com
To: Tapestry users users@tapestry.apache.org
Sent: Mon, October 12, 2009 11:18:05 AM
Subject: Tapestry5.1 Upgrade Issue
I'm trying
Em Mon, 12 Oct 2009 17:57:09 -0300, Dave Greggory davegregg...@yahoo.com
escreveu:
Does any one have any ideas on why this is happening? Shouldn't tapestry
be looking at the request to see which Locale it is for?
It does, but Tapestry adds Locale as something that is @Inject'able, not
