I have a related follow-up question. I was getting a stack overflow at
runtime because of the polymorphic hierarchy and was not using @ExtraTypes.
My hierarchy was 3 levels deep. Top level is GenericType, next level is
CategoryType and EventType, and next level is four subtypes of
On Saturday, February 23, 2013 5:20:23 AM UTC+1, Bademus ᵗʰᵉ wrote:
It seems that GenTool goes into infinite loop again
Version: gwt 2.5.1-rc1
Code:
public interface EntityBaseProxy extends EntityProxy { ... }
@ExtraTypes(AuthorProxy.class)
public interface UserProxy extends
It seems that GenTool goes into infinite loop again
Version: gwt 2.5.1-rc1
Code:
public interface EntityBaseProxy extends EntityProxy { ... }
@ExtraTypes(AuthorProxy.class)
public interface UserProxy extends EntityBaseProxy { ... }
public interface AuthorProxy extends UserProxy { ... }
Result:
Thanks for all of the replies. I have had some time to dig into this a
little more. Long story short, the ValidationTool finds inherited
@ExtraTypes when run on its own from the command line but does not
when run as an automated annotation processor. I think it might have
something to do with the
I have these interfaces:
@ExtraTypes({FooProxy.class})
public interface FooRequestFactory extends RequestFactory
{
...
}
@ExtraTypes({BarProxy.class})
public interface BarRequestFactory extends FooRequestFactory
{
...
}
if i look at the generated
Can't you put your @ExtraTypes on the proxies instead? I.e. if you have
FooProxy extends SuperFooProxy, then why not put
@ExtraTypes(FooProxy.class) on the SuperFooProxy interface?
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view
Hey Thomas,
Thanks for the reply. I think I actually tried that at one point on
the RC and ran into a stack overflow. Regardless, the design still
wont really work for me because the base Component proxy object really
has no idea what it's subclasses are or its subclasses' dependent
ValueProxies.
I also have @ExtraTypes on RF due to stack overflow in RC. Haven't tried
yet in the release.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
Brad, what if you place @ExtraTypes(FooProxy.class) on some RequestContext
returned by methods of FooRequestFactory?
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
Doesn't appear much has changed on the RequestFactoryGenerator in the
final release from RC1. I ended up having to do a copy of
RequestFactoryGenerator and change AllReachableTypesVisitor to be:
private static class AllReachableTypesVisitor extends
RequestMethodTypesVisitor {
Also, after you put that in your copied RequestFactoryGenerator,
you'll need to put:
generate-with
class=package where you put your copied
generator.RequestFactoryGenerator
when-type-assignable
Looking further, it would probably be best though if a fix for
RequestFactoryModel was checked in that had a check against the type
being examined and the type it gets for the proxy type in the
@ExtraTypes array:
private ListEntityProxyModel checkExtraTypes(JClassType type,
boolean
12 matches
Mail list logo
