Is that a reload, or just the initial load? The "[3] Reloading" line may, or may not, be accurate.
On Thu, Jun 13, 2013 at 4:52 AM, Muhammad Gelbana <m.gelb...@gmail.com>wrote: > I'm trying to resolve a contribution error due to a class casting exception > but I find the following highlighted message very strange. Why would > tapestry reload a class being instantiated ? > I understand there are tapestry concepts such as reloading services, > pages\components or templates during dev mode only when they are changed to > speed up development, but here, I'm only starting my application. > > 13:26:27 ERROR (OperationTrackerImpl.java:128)-[main] Operations trace: > 13:26:27 ERROR (OperationTrackerImpl.java:137)-[main] [ 1] Realizing > service ConfigurationShutdownManager > 13:26:27 ERROR (OperationTrackerImpl.java:137)-[main] [ 2] Instantiating > service ConfigurationShutdownManager implementation via > com.sc.ipk.services.CoreModule.bind(ServiceBinder) (at CoreModule.java:42) > *13:26:27 ERROR (OperationTrackerImpl.java:137)-[main] [ 3] Reloading class > com.sc.ipk.services.ConfigurationShutdownManager.* > 13:26:27 ERROR (OperationTrackerImpl.java:137)-[main] [ 4] Creating plan to > instantiate com.sc.ipk.services.ConfigurationShutdownManager via public > > com.sc.ipk.services.ConfigurationShutdownManager(java.util.Map,org.slf4j.Logger) > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
