You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Boris Horvat <ho...@gmail.com> on 2014/05/24 11:30:30 UTC
Tapestry ClassLoading errors
Hi everyone,
I have create a service to help me reload different ajax zone but I get the
following exception
java.lang.LinkageError
loader constraint violation: when resolving method
"com.bomahabo.flow.tapestry.utility.AjaxZonesReloader.refreshAjaxZones([Lorg/apache/tapestry5/corelib/components/Zone;)V"
the class loader (instance of
org/apache/tapestry5/internal/plastic/PlasticClassLoader) of the current
class, com/bomahabo/flow/tapestry/pages/blackbox/Assets, and the class
loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) for
resolved class, com/bomahabo/flow/tapestry/utility/AjaxZonesReloader, have
different Class objects for the type
com.bomahabo.flow.tapestry.utility.AjaxZonesReloader.refreshAjaxZones([Lorg/apache/tapestry5/corelib/components/Zone;)V
used in the signature
Class definition and package location
package com.bomahabo.flow.*tapestry.utility*
public class AjaxZonesReloader {
private AjaxResponseRenderer ajaxResponseRenderer;
private Request request;
private JavaScriptSupport javascript;
public AjaxZonesReloader(AjaxResponseRenderer ajaxResponseRenderer,
Request request, JavaScriptSupport javascript) {
this.ajaxResponseRenderer = ajaxResponseRenderer;
this.request = request;
this.javascript = javascript;
}
Thank you :)
--
Sincerely
*Boris Horvat*
Re: Tapestry ClassLoading errors
Posted by Boris Horvat <ho...@gmail.com>.
I will try to search for the direct usage of the class and to remove it if
I find it
Thanks
On Tue, May 27, 2014 at 5:50 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <ho...@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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Sincerely
*Boris Horvat*
Re: Tapestry ClassLoading errors
Posted by Boris Horvat <ho...@gmail.com>.
Glad to report that this resolved my issue. Thank you :)
On Mon, Jun 2, 2014 at 11:59 PM, Lance Java <la...@googlemail.com>
wrote:
> http://tapestry.apache.org/class-reloading.html
> On 2 Jun 2014 22:49, "Boris Horvat" <ho...@gmail.com> wrote:
>
> > Hm...I did not know about this. Will try it out over the weekend. Thank
> you
> > very much.
> >
> > BTW is there some place in documentation where I can read about this
> trick?
> >
> >
> > On Sun, Jun 1, 2014 at 11:05 PM, Lance Java <la...@googlemail.com>
> > wrote:
> >
> > > 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" <ho...@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.java@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" <ho...@gmail.com>
> > wrote:
> > > > >
> > > > > > That does sound promising. Will try it out. Thanks
> > > > > >
> > > > > >
> > > > > > On Sun, Jun 1, 2014 at 12:38 AM, Chris Mylonas <
> chris@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.boris@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 <
> > > > > > > > thiagohp@gmail.com> wrote:
> > > > > > > >
> > > > > > > > > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
> > > > > > > > horvat.z.boris@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-unsubscribe@tapestry.apache.org
> > > > > > > > > For additional commands, e-mail:
> > > users-help@tapestry.apache.org
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Sincerely
> > > > > > > > *Boris Horvat*
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Sincerely
> > > > > > *Boris Horvat*
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sincerely
> > > > *Boris Horvat*
> > > >
> > >
> >
> >
> >
> > --
> > Sincerely
> > *Boris Horvat*
> >
>
--
Sincerely
*Boris Horvat*
Re: Tapestry ClassLoading errors
Posted by Lance Java <la...@googlemail.com>.
http://tapestry.apache.org/class-reloading.html
On 2 Jun 2014 22:49, "Boris Horvat" <ho...@gmail.com> wrote:
> Hm...I did not know about this. Will try it out over the weekend. Thank you
> very much.
>
> BTW is there some place in documentation where I can read about this trick?
>
>
> On Sun, Jun 1, 2014 at 11:05 PM, Lance Java <la...@googlemail.com>
> wrote:
>
> > 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" <ho...@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.java@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" <ho...@gmail.com>
> wrote:
> > > >
> > > > > That does sound promising. Will try it out. Thanks
> > > > >
> > > > >
> > > > > On Sun, Jun 1, 2014 at 12:38 AM, Chris Mylonas <chris@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" <ho...@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 <
> > > > > > > thiagohp@gmail.com> wrote:
> > > > > > >
> > > > > > > > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
> > > > > > > horvat.z.boris@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-unsubscribe@tapestry.apache.org
> > > > > > > > For additional commands, e-mail:
> > users-help@tapestry.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Sincerely
> > > > > > > *Boris Horvat*
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sincerely
> > > > > *Boris Horvat*
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Sincerely
> > > *Boris Horvat*
> > >
> >
>
>
>
> --
> Sincerely
> *Boris Horvat*
>
Re: Tapestry ClassLoading errors
Posted by Boris Horvat <ho...@gmail.com>.
Hm...I did not know about this. Will try it out over the weekend. Thank you
very much.
BTW is there some place in documentation where I can read about this trick?
On Sun, Jun 1, 2014 at 11:05 PM, Lance Java <la...@googlemail.com>
wrote:
> 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" <ho...@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 <la...@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" <ho...@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" <ho...@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 <
> > > > > > thiagohp@gmail.com> wrote:
> > > > > >
> > > > > > > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
> > > > > > horvat.z.boris@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-unsubscribe@tapestry.apache.org
> > > > > > > For additional commands, e-mail:
> users-help@tapestry.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Sincerely
> > > > > > *Boris Horvat*
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sincerely
> > > > *Boris Horvat*
> > > >
> > >
> >
> >
> >
> > --
> > Sincerely
> > *Boris Horvat*
> >
>
--
Sincerely
*Boris Horvat*
Re: Tapestry ClassLoading errors
Posted by Lance Java <la...@googlemail.com>.
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" <ho...@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 <la...@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" <ho...@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" <ho...@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 <
> > > > > thiagohp@gmail.com> wrote:
> > > > >
> > > > > > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
> > > > > horvat.z.boris@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-unsubscribe@tapestry.apache.org
> > > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sincerely
> > > > > *Boris Horvat*
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Sincerely
> > > *Boris Horvat*
> > >
> >
>
>
>
> --
> Sincerely
> *Boris Horvat*
>
Re: Tapestry ClassLoading errors
Posted by Boris Horvat <ho...@gmail.com>.
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 <la...@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" <ho...@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" <ho...@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 <
> > > > thiagohp@gmail.com> wrote:
> > > >
> > > > > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
> > > > horvat.z.boris@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-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Sincerely
> > > > *Boris Horvat*
> > > >
> > >
> >
> >
> >
> > --
> > Sincerely
> > *Boris Horvat*
> >
>
--
Sincerely
*Boris Horvat*
Re: Tapestry ClassLoading errors
Posted by Lance Java <la...@googlemail.com>.
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" <ho...@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" <ho...@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 <
> > > thiagohp@gmail.com> wrote:
> > >
> > > > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
> > > horvat.z.boris@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-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Sincerely
> > > *Boris Horvat*
> > >
> >
>
>
>
> --
> Sincerely
> *Boris Horvat*
>
Re: Tapestry ClassLoading errors
Posted by Boris Horvat <ho...@gmail.com>.
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" <ho...@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 <
> > thiagohp@gmail.com> wrote:
> >
> > > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
> > horvat.z.boris@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-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > Sincerely
> > *Boris Horvat*
> >
>
--
Sincerely
*Boris Horvat*
Re: Tapestry ClassLoading errors
Posted by Boris Horvat <ho...@gmail.com>.
Not much more code can be given so let me copy it from the beginning of the
mail
So where should one put the class below in order to be able to simple
inject it into a page and that after reloaded I dont get a given exception
java.lang.LinkageError
loader constraint violation: when resolving method
"com.bomahabo.flow.tapestry.utility.AjaxZonesReloader.refreshAjaxZones([Lorg/apache/tapestry5/corelib/components/Zone;)V"
the class loader (instance of
org/apache/tapestry5/internal/plastic/PlasticClassLoader) of the current
class, com/bomahabo/flow/tapestry/pages/blackbox/Assets, and the class
loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) for
resolved class, com/bomahabo/flow/tapestry/utility/AjaxZonesReloader, have
different Class objects for the type
com.bomahabo.flow.tapestry.utility.AjaxZonesReloader.refreshAjaxZones([Lorg/apache/tapestry5/corelib/components/Zone;)V
used in the signature
Class definition and package location
package com.bomahabo.flow.*tapestry.utility*
public class AjaxZonesReloader {
private AjaxResponseRenderer ajaxResponseRenderer;
private Request request;
private JavaScriptSupport javascript;
public AjaxZonesReloader(AjaxResponseRenderer ajaxResponseRenderer,
Request request, JavaScriptSupport javascript) {
this.ajaxResponseRenderer = ajaxResponseRenderer;
this.request = request;
this.javascript = javascript;
}
public class AppModule {
public static void bind(ServiceBinder binder) {
binder.bind(AjaxZonesReloader.class);
}
On Sun, Jun 1, 2014 at 2:32 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Sat, 31 May 2014 19:38:43 -0300, 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
>>
>
> 'base' is a controlled package for classes that are meant to be
> superclasses of pages, components and mixins, so I advise you to not do
> that. No code was given, so it's hard to know what's happening. I still
> think there's a mix of usage of your utility class in two ways: through
> injected service and not through injected service. Another option is to
> disable class reloading for this service. Anyway,
> com.bomahabo.flow.tapestry.utility is *not* a controlled package.
>
>
>
>> http://tapestry.apache.org/class-reloading.html
>> On 01/06/2014 4:58 am, "Boris Horvat" <ho...@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 <
>>> thiagohp@gmail.com> wrote:
>>>
>>> > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
>>> horvat.z.boris@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-unsubscribe@tapestry.apache.org
>>> > For additional commands, e-mail: users-help@tapestry.apache.org
>>> >
>>> >
>>>
>>>
>>> --
>>> Sincerely
>>> *Boris Horvat*
>>>
>>>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Sincerely
*Boris Horvat*
Re: Tapestry ClassLoading errors
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Sat, 31 May 2014 19:38:43 -0300, 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
'base' is a controlled package for classes that are meant to be
superclasses of pages, components and mixins, so I advise you to not do
that. No code was given, so it's hard to know what's happening. I still
think there's a mix of usage of your utility class in two ways: through
injected service and not through injected service. Another option is to
disable class reloading for this service. Anyway,
com.bomahabo.flow.tapestry.utility is *not* a controlled package.
>
> http://tapestry.apache.org/class-reloading.html
> On 01/06/2014 4:58 am, "Boris Horvat" <ho...@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 <
>> thiagohp@gmail.com> wrote:
>>
>> > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
>> horvat.z.boris@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-unsubscribe@tapestry.apache.org
>> > For additional commands, e-mail: users-help@tapestry.apache.org
>> >
>> >
>>
>>
>> --
>> Sincerely
>> *Boris Horvat*
>>
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry ClassLoading errors
Posted by Chris Mylonas <ch...@opencsta.org>.
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" <ho...@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 <
> thiagohp@gmail.com> wrote:
>
> > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
> horvat.z.boris@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-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Sincerely
> *Boris Horvat*
>
Re: Tapestry ClassLoading errors
Posted by Boris Horvat <ho...@gmail.com>.
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 <
thiagohp@gmail.com> wrote:
> On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <ho...@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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Sincerely
*Boris Horvat*
Re: Tapestry ClassLoading errors
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat
<ho...@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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry ClassLoading errors
Posted by Boris Horvat <ho...@gmail.com>.
But it is only triggered in class re loading
On 27 May 2014 15:11, "Taha Siddiqi" <ta...@gmail.com> wrote:
> It looks like a dependency problem. Two versions of tapestry-core in class
> path perhaps.
>
> Sent from my iPhone
>
> > On May 27, 2014, at 5:30 PM, Boris Horvat <ho...@gmail.com>
> wrote:
> >
> > Anyone has any idea?
> >> On 24 May 2014 11:30, "Boris Horvat" <ho...@gmail.com> wrote:
> >>
> >>
> >> Hi everyone,
> >>
> >> I have create a service to help me reload different ajax zone but I get
> >> the following exception
> >>
> >> java.lang.LinkageError
> >> loader constraint violation: when resolving method
> >>
> "com.bomahabo.flow.tapestry.utility.AjaxZonesReloader.refreshAjaxZones([Lorg/apache/tapestry5/corelib/components/Zone;)V"
> >> the class loader (instance of
> >> org/apache/tapestry5/internal/plastic/PlasticClassLoader) of the current
> >> class, com/bomahabo/flow/tapestry/pages/blackbox/Assets, and the class
> >> loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) for
> >> resolved class, com/bomahabo/flow/tapestry/utility/AjaxZonesReloader,
> have
> >> different Class objects for the type
> >>
> com.bomahabo.flow.tapestry.utility.AjaxZonesReloader.refreshAjaxZones([Lorg/apache/tapestry5/corelib/components/Zone;)V
> >> used in the signature
> >>
> >> Class definition and package location
> >>
> >> package com.bomahabo.flow.*tapestry.utility*
> >>
> >> public class AjaxZonesReloader {
> >>
> >> private AjaxResponseRenderer ajaxResponseRenderer;
> >> private Request request;
> >> private JavaScriptSupport javascript;
> >>
> >> public AjaxZonesReloader(AjaxResponseRenderer ajaxResponseRenderer,
> >> Request request, JavaScriptSupport javascript) {
> >> this.ajaxResponseRenderer = ajaxResponseRenderer;
> >> this.request = request;
> >> this.javascript = javascript;
> >> }
> >>
> >> Thank you :)
> >>
> >> --
> >> Sincerely
> >> *Boris Horvat*
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Tapestry ClassLoading errors
Posted by Taha Siddiqi <ta...@gmail.com>.
It looks like a dependency problem. Two versions of tapestry-core in class path perhaps.
Sent from my iPhone
> On May 27, 2014, at 5:30 PM, Boris Horvat <ho...@gmail.com> wrote:
>
> Anyone has any idea?
>> On 24 May 2014 11:30, "Boris Horvat" <ho...@gmail.com> wrote:
>>
>>
>> Hi everyone,
>>
>> I have create a service to help me reload different ajax zone but I get
>> the following exception
>>
>> java.lang.LinkageError
>> loader constraint violation: when resolving method
>> "com.bomahabo.flow.tapestry.utility.AjaxZonesReloader.refreshAjaxZones([Lorg/apache/tapestry5/corelib/components/Zone;)V"
>> the class loader (instance of
>> org/apache/tapestry5/internal/plastic/PlasticClassLoader) of the current
>> class, com/bomahabo/flow/tapestry/pages/blackbox/Assets, and the class
>> loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) for
>> resolved class, com/bomahabo/flow/tapestry/utility/AjaxZonesReloader, have
>> different Class objects for the type
>> com.bomahabo.flow.tapestry.utility.AjaxZonesReloader.refreshAjaxZones([Lorg/apache/tapestry5/corelib/components/Zone;)V
>> used in the signature
>>
>> Class definition and package location
>>
>> package com.bomahabo.flow.*tapestry.utility*
>>
>> public class AjaxZonesReloader {
>>
>> private AjaxResponseRenderer ajaxResponseRenderer;
>> private Request request;
>> private JavaScriptSupport javascript;
>>
>> public AjaxZonesReloader(AjaxResponseRenderer ajaxResponseRenderer,
>> Request request, JavaScriptSupport javascript) {
>> this.ajaxResponseRenderer = ajaxResponseRenderer;
>> this.request = request;
>> this.javascript = javascript;
>> }
>>
>> Thank you :)
>>
>> --
>> Sincerely
>> *Boris Horvat*
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry ClassLoading errors
Posted by Boris Horvat <ho...@gmail.com>.
Anyone has any idea?
On 24 May 2014 11:30, "Boris Horvat" <ho...@gmail.com> wrote:
>
> Hi everyone,
>
> I have create a service to help me reload different ajax zone but I get
> the following exception
>
> java.lang.LinkageError
> loader constraint violation: when resolving method
> "com.bomahabo.flow.tapestry.utility.AjaxZonesReloader.refreshAjaxZones([Lorg/apache/tapestry5/corelib/components/Zone;)V"
> the class loader (instance of
> org/apache/tapestry5/internal/plastic/PlasticClassLoader) of the current
> class, com/bomahabo/flow/tapestry/pages/blackbox/Assets, and the class
> loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) for
> resolved class, com/bomahabo/flow/tapestry/utility/AjaxZonesReloader, have
> different Class objects for the type
> com.bomahabo.flow.tapestry.utility.AjaxZonesReloader.refreshAjaxZones([Lorg/apache/tapestry5/corelib/components/Zone;)V
> used in the signature
>
> Class definition and package location
>
> package com.bomahabo.flow.*tapestry.utility*
>
> public class AjaxZonesReloader {
>
> private AjaxResponseRenderer ajaxResponseRenderer;
> private Request request;
> private JavaScriptSupport javascript;
>
> public AjaxZonesReloader(AjaxResponseRenderer ajaxResponseRenderer,
> Request request, JavaScriptSupport javascript) {
> this.ajaxResponseRenderer = ajaxResponseRenderer;
> this.request = request;
> this.javascript = javascript;
> }
>
> Thank you :)
>
> --
> Sincerely
> *Boris Horvat*
>