On 5 Feb 2014, at 21:10, Rama Krishna Gollapudi wrote:
> This is not working. I'm getting the same exception(DomainResource is
> abstract, not a concrete class. Unable to create AssistedInject factory).
Unfortunately I don't see that exception using the snippets of code you pasted
below, the
This is not working. I'm getting the same exception(DomainResource is
abstract, not a concrete class. Unable to create AssistedInject factory).
On Wednesday, 5 February 2014 14:52:22 UTC-6, scl wrote:
>
> According to the documentation:
>
> constructedType is a concrete class with an @Inject-an
Yes, this is one of the use-cases that assistedinject supports, and there's
a lot of tests to make sure it's working as expected. Since you're
experiencing a problem with it, the best way to find out what's causing
that problem is to isolate it into a reproducible test-case.
sam
On Wed, Feb 5,
I'm not sure. But here is my problem precisely. I'm using an abstract class
inside the factory and bindind that implementation.
Example:
public interface ResourceFactory {
Resource domainResource(Domain target);
}
public abstract class Resource{}
public MyResource extends Resource{}.
Whe
According to the documentation:
constructedType is a concrete class with an @Inject-annotated
constructor. In addition to injector-supplied parameters, the
constructor should have parameters that match each of the factory
method's parameters. Each factory-supplied pa
Can you isolate the problem into a repeatable self-contained test-case?
sam
On Tue, Feb 4, 2014 at 1:39 PM, Rama Krishna Gollapudi
wrote:
> Here is my abstract class
>
> public abstract class DomainResource {
>
> @Inject
> @Assisted
> private Domain target;
>
> @Inject
> pr
Hello is there any solution to my problem ?
On Tuesday, 4 February 2014 12:39:29 UTC-6, Rama Krishna Gollapudi wrote:
>
> Here is my abstract class
>
> public abstract class DomainResource {
>
> @Inject
> @Assisted
> private Domain target;
>
> @Inject
> private LinkHelper helpe
I tried re-importing from maven and invalidating the caches. Neither
worked, but I was able to fix it by going into the Modules configuration
and removing the broken "guava (1)", "guava (2)" and "guava (4)" modules.
Not sure how they got in there, but everything works now.
Thanks for the assist
Did you try "Invalidate Caches"?
-- Brian
On Feb 5, 2014, at 11:22 AM, Michael Burton wrote:
> Is there a recommended way to build guice from within IntelliJ? It works
> fine using maven, but when I try to edit or build code from IntellIJ 13 I see
> a number of errors due to unresolved depe
I'd summit this issue to JetBrainssee what they say.
-Dave
On Wed, Feb 5, 2014 at 11:26 AM, Sam Berlin wrote:
> In Eclipse, I just put in the source & jars. Not sure what IntelliJ would
> be doing ... maybe it's trying to build a layout off the POMs and is
> confused since the current POM
In Eclipse, I just put in the source & jars. Not sure what IntelliJ would
be doing ... maybe it's trying to build a layout off the POMs and is
confused since the current POM setup shades the dependencies?
sam
On Wed, Feb 5, 2014 at 1:22 PM, Michael Burton wrote:
> Is there a recommended way
Is there a recommended way to build guice from within IntelliJ? It works
fine using maven, but when I try to edit or build code from IntellIJ 13 I
see a number of errors due to unresolved dependencies in things like the
Guava library. I assume this is because of the way the build is using
jar
12 matches
Mail list logo
