You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Muhammad Gelbana <m....@gmail.com> on 2013/06/13 13:52:47 UTC
[t5.3.7] Why is tapestry reloading a service being instantiated ?
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)
Re: [t5.3.7] Why is tapestry reloading a service being instantiated ?
Posted by Muhammad Gelbana <m....@gmail.com>.
I suspect this could have something to do with this issue:
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/T-5-3-Everything-annotated-with-Startup-called-twice-tt5715991.html
On Thu, Jun 13, 2013 at 6:53 PM, Muhammad Gelbana <m....@gmail.com>wrote:
> It's the initial load, the first run on the application in eclipse.
>
>
> On Thu, Jun 13, 2013 at 6:48 PM, Howard Lewis Ship <hl...@gmail.com>wrote:
>
>> 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.gelbana@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
>>
>
>
Re: [t5.3.7] Why is tapestry reloading a service being instantiated ?
Posted by Muhammad Gelbana <m....@gmail.com>.
It's the initial load, the first run on the application in eclipse.
On Thu, Jun 13, 2013 at 6:48 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> 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.gelbana@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
>
Re: [t5.3.7] Why is tapestry reloading a service being instantiated ?
Posted by Howard Lewis Ship <hl...@gmail.com>.
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....@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