As you see from this Tapestry FAQ, I just realized that my bad habit has cost me some of the advantaged of using Tapestry. I often lazy in creating an Interface when binding a Tapestry Service. It turns out that if you don't give an Interface for the service, Tapestry will create the implementation immediately after injection. While I was expecting it will be instantiated only after the first method of the service is invoked.
Well, i guess its time to dig up some old code :)
No comments:
Post a Comment