I found the issue.
I was referencing the implementing class in the interface, which is to be
implemented.
Like:
interface MyInterface{
public MyImplementation doSomething();
}
class MyImplementation implements MyInterface {
public MyImplementation doSomething();
}
So it was entirely my
On Saturday, September 8, 2012, bigcache1 wrote:
I found the issue.
I was referencing the implementing class in the interface, which is to be
implemented.
Like:
interface MyInterface{
public MyImplementation doSomething();
}
class MyImplementation implements MyInterface {
public
Absolutely, you typically have services injected into other service
implementations.
Sent from my iPad
On Aug 3, 2012, at 10:56 PM, bigcache1 sharp.maes...@gmail.com wrote:
I will try to recreate this exception on another page, with another services
injected.
Is it right, that there is
On Sat, 04 Aug 2012 02:56:38 -0300, bigcache1 sharp.maes...@gmail.com
wrote:
I will try to recreate this exception on another page, with another
services
injected.
Is it right, that there is no constraints (except jvm memory) for
Tapestry,
for the level of injection?
Nope. Don't
If you mean launching application in production mode - it didn't help. Still
getting the same exception.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/another-java-lang-LinkageError-loader-constraint-violation-in-interface-itable-initialization-tp5714993p5715036.html
I will try to recreate this exception on another page, with another services
injected.
Is it right, that there is no constraints (except jvm memory) for Tapestry,
for the level of injection?
I mean, could we place @Inject, inside of injected service, which lives
inside another injected service,
In my application I use the idea if middle data access layers. I implemented
that through the set of different data access objects, which I named
mediators. Each mediator is presented through the interface and implementing
class, which are binded with the Tapestry IoC.
But mediators are
Forgot to mention, mediators interfaces are placed in the
x.y.dal.mediators.interfaces and implementing classes in x.y.dal.mediators
--
View this message in context:
This may be a consequence of live class reloading for services, if you
are invoking protected (or package private) methods of other classes.
Try turning live class reloading entirely off; if that fixes the
problem, you can disabled service reloading for the individual
service(s) using the
