Components and services are loaded by different classloaders. Services should never reference component classes.
Your service has a method: refreshAjaxZones(Zone) This is the problem since Zone is a component. Try referencing the interface ClientElement instead. On 1 Jun 2014 12:41, "Boris Horvat" <horvat.z.bo...@gmail.com> wrote: > No it is the other way around. I want them to be part of the tapestry > service, but for some reason it fails with the class loading exception. I > think that by moving it to the *base *package it should work > > > On Sun, Jun 1, 2014 at 12:39 PM, Lance Java <lance.j...@googlemail.com> > wrote: > > > If you want to keep your utility out of the tapestry controlled packages, > > you can reference interfaces instead of concrete components. Make sure > your > > own interfaces are not in a tapestry controlled package. > > On 1 Jun 2014 09:34, "Boris Horvat" <horvat.z.bo...@gmail.com> wrote: > > > > > That does sound promising. Will try it out. Thanks > > > > > > > > > On Sun, Jun 1, 2014 at 12:38 AM, Chris Mylonas <ch...@opencsta.org> > > wrote: > > > > > > > What if you move your classes from tapestry.utility to > > > > tapestry.base.utility which is controlled by tapestry....maybe > > > > > > > > http://tapestry.apache.org/class-reloading.html > > > > On 01/06/2014 4:58 am, "Boris Horvat" <horvat.z.bo...@gmail.com> > > wrote: > > > > > > > > > In what package should I put this component? Currently it resides > in > > > > > > > > > > package com.bomahabo.flow.tapestry.utility > > > > > > > > > > and it uses > > > > > > > > > > private AjaxResponseRenderer ajaxResponseRenderer; > > > > > private Request request; > > > > > private JavaScriptSupport javascript; > > > > > > > > > > Should I move it outside of the tapestry in order to help with this > > > > issue? > > > > > > > > > > > > > > > On Tue, May 27, 2014 at 5:50 PM, Thiago H de Paula Figueiredo < > > > > > thiag...@gmail.com> wrote: > > > > > > > > > > > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat < > > > > > horvat.z.bo...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > But it is only triggered in class re loading > > > > > >> > > > > > > > > > > > > It could be a reloadable service being used both injected from > > > > > > Tapestry-IoC and directly, not through T-IoC. If something is > live > > > > class > > > > > > reloadable, you should always access it though Tapestry (classes > in > > > > > > controlled packages) or Tapestry-IoC (injected services). > > > > > > > > > > > > -- > > > > > > Thiago H. de Paula Figueiredo > > > > > > Tapestry, Java and Hibernate consultant and developer > > > > > > http://machina.com.br > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > > > > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Sincerely > > > > > *Boris Horvat* > > > > > > > > > > > > > > > > > > > > > -- > > > Sincerely > > > *Boris Horvat* > > > > > > > > > -- > Sincerely > *Boris Horvat* >
