Hello list,
I find it odd that IoC depends on JSON. I discovered this was done in
patch TAP5-1362 (April 1st) whenere there was a coercion from String to
JSONArray and to JSONObject added to "Tapestry"
It would be better if these coercions were added by, for example,
tapestry-core instead. Now, this is the case! TAP5-1457 adds coercions
from String to JSONArray and to JSONObject (July 2nd). It is a mystery
why these coercions were added twice, but they are.
My suggestion is that commit 8a26fb1b... is partially reverted so
tapestry-ioc no longer depends on tapestry-json.
I have created a JIRA issue for it.
You can use the patch from JIRA (TAP5-1591) or pull from
git://hetdiana.dyndns.org/tapestry5.git branch 1591
To be honest, it might be worth it to wonder: shouldn't the coercion be
added by tapestry-json, rather than tapestry-core or tapestry-ioc? But I
leave that question to people with more experience than me.
Regards,
Tom.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
