Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I add DynaTableRequestFactoryDeobfuscatorBuilder class from this site: https://code.google.com/p/arjunsatyapal/source/detail?r=9d89f7a1b5102d2db0e032ec87f9ae7b8bc841a8 It seems woring fine now On Friday, September 23, 2011 10:20:24 AM UTC+8, TULC wrote: I have not yet been able to get past this problem... I am simply trying to run the DynaTableRF from the samples in eclipse. I have the latest GPE installed. I have followed the instructions at http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation for eclipse and have also tried adding requestfactory-apt.jar to the eclipse project build path manually. I am not using Maven. I have tried adding all the requestfactory-* JARs to the build path, even though I understand requestfactory-client.jar is supposed to be included in gwt-user.jar and similarly with requestfactory-server.jar in gwt-servlet.jar. I have also tried putting both requestfactory- server.jar and requestfactory-apt.jar into the WEB-INF/lib directory. But it keeps failing with this error. Can anyone help me?? Cheers, Evan -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
Just like everyone else, I was stuck at this validation error. Following http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation, I deleted the classes manually from WEB-INF folder and that did the job. Basically, obfuscator classes should appear in .apt_generated folder in home project directory. रविवार, 7 अप्रैल 2013 6:26:19 pm UTC+5:30 को, Aman Sharma ने लिखा: How to do the all of these steps if no IDE's including Eclipse. On Saturday, September 24, 2011 2:33:49 AM UTC+5:30, Jonas wrote: Hi, this Wiki entry helped me to solve the problem: http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation Do exactly what is shown in the printscreens and it should work. If it's not working tell exactly what you did. I almost got crazy and did see that they added verbose=false to Annotation Processing. I thought this isn't necessary as they didn't mention it in the text. I was wrong. Jonas -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
How to do the all of these steps if no IDE's including Eclipse. On Saturday, September 24, 2011 2:33:49 AM UTC+5:30, Jonas wrote: Hi, this Wiki entry helped me to solve the problem: http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation Do exactly what is shown in the printscreens and it should work. If it's not working tell exactly what you did. I almost got crazy and did see that they added verbose=false to Annotation Processing. I thought this isn't necessary as they didn't mention it in the text. I was wrong. Jonas -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I have been struggling with the similar issue and then some. I finally succeeded to make Maven, 2.4 and RF work all together. Here's the details in springsource forum: http://forum.springsource.org/showthread.php?127502-GWT-2-4-maven-STS-Eclipse-(especially-if-you-are-upgrading-from-an-older-gwt)p=416166#post416166 Thanks, Arash -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/WsgpUOv0uhIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
On Saturday, June 16, 2012 10:57:45 AM UTC+2, Arash wrote: I have been struggling with the similar issue and then some. I finally succeeded to make Maven, 2.4 and RF work all together. Maven, GWT 2.4 and RF always worked rather well together (RfValidator is a standard Java annotation processor), and the new m2e-apt connector from JBoss integrates it nicely within Eclipse. See http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation See also http://code.google.com/p/google-web-toolkit/source/detail?r=11019 for an alternate way of doing it (if you cannot use m2e-apt) AFAIK, the issue was when you have other processors such as AspectJ. I'm not using it though, so I can't comment. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/7S-3ZXfEhR8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
My project was running fine when suddendly and I enfasize SUDDENDLY, I got the Validation error. I was following all the steps in http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation before the error, I changed the .apt_generated to .apt_generated1 but it didn't solve anything. I solved it strangely by: 1.- Clean the project 2.- Close the project 3.- Open the project and change .apt_generated to .apt_generated1 4.- Recompile and worked fine I don't know why but this worked. Hope it helps -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I too have been banging my head for RequestFactory error 'The
RequestFactory ValidationTool must be run for the '. I too have
requestfactory-apt.jar on buid path. Done checking eclipse('helios')
for annotation processing. I am quite frustrated at all and thinking
on moving over gwt. Do we have any explicit way to revoke the
validation tool or any straight solution to the problem like working
from command line to run Validation tool or are there any parameters
to give in run config. Please help!!! any link, any reference on net
to explain in depth what is this validation tool and why n how it
works. SOS!!
On Apr 22, 4:03 pm, Prashant Hegde prashant.he...@gmail.com wrote:
encountered the same issue today, solved by changing the directory name from
.apt_generated to .apt_generated1
Seems like that forces a revalidation.
Prashant
On 17-Apr-2012, at 1:08 AM, Felipe Stanham wrote:
I Know this is old but I just got stuck with the same problem. Did you ever
got around this and solved it?
I'm really frustrated, I've tried everything I knew of, everything any blog
speaks of and still no validation run!
PLEASE HELP!!!
On Sunday, January 15, 2012 12:32:56 AM UTC-2, TULC wrote:
I'm still stuck on this. Some projects I've ported to 2.4 now work,
but others still just won't budge. I have tried all the additional
steps, but my *DeobfuscatorBuilder.java just won't appear in those
projects (event thought the .apt_generated folder does, and is
replaced if I change the name). I have noticed some (though not all)
of those projects are now giving me the error build.properties does
not exist, which may or may not be related.
I'm frustrated to the point I'm considering ditching GWT altogether; I
haven't been able to proceed with any GWT development since the 2.4
upgrade. Like the man said, I'm good, really I am, but I just can't
figure this one out, and it really shouldn't be this hard. Thanks for
the breaking change.
Evan
On Dec 14 2011, 12:12 pm, dparish dpar...@gmail.com wrote:
I had the same problem. There are two other possible reasons you see
this:
1. Your java compliance level in the project is set to 1.5
2. Your classes are already compiled. I don't know why, but touching
the my RequestContext classes had NO affect until I deleted the
classes that were compiled before I added annotations. Now it all
works just fine.
Attention Google:
This stuff is w tooo complicated. I'm good. really I am, but
this is just misdirection at it's worst.
On Nov 20, 5:47 pm, oerten25 ozgur.er...@gmail.com wrote:
I've been getting the same error and tried the things mentioned in the
discussion without any luck. Finally i realised that i don't have the
apt_generated folder. So i changed the generated source directory
option to something other than apt_generated in Annotation
Processing setting. That fixed it.
On Oct 2, 11:29 pm, TULC evan.a.te...@gmail.com wrote:
I just get the sameerroras posted by Eric at the beginning of the
thread, but I have copied/pasted the full dump below.
Thomas, I'm not sure what you mean about the .apt_generated being in
my build path?
Thanks for the help, guys...
Evan
Console:
log4j:WARN No appenders could be found for logger
(org.apache.jasper.compiler.Js
pRuntimeContext).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig
for more in
fo.
03/10/2011 8:24:49 AM
com.google.web.bindery.requestfactory.server.RequestFactor
yServlet doPost
SEVERE: Unexpectederror
java.lang.RuntimeException:
TheRequestFactoryValidationToolmustberunfor th
e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory
RequestFactor
y type
at com.google.web.bindery.requestfactory.vm.impl.Deobfuscator
$Builder.load(Deob
fuscator.java:59)
at
com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeo
b
fuscator(ResolverServiceLayer.java:43)
at
com.google.web.bindery.requestfactory.server.ResolverServiceLayer.resolveRe
q
uestFactory(ResolverServiceLayer.java:176)
at
com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR
e
questFactory(ServiceLayerDecorator.java:172)
at
com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR
e
questFactory(ServiceLayerDecorator.java:172)
at
com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR
e
questFactory(ServiceLayerDecorator.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39
)
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
Is there any chance if move on to maven or check 'Use google
appengine'( I am not using appengine) to make it work
On Apr 28, 11:13 am, saurabh saurabh saurabh.bl...@gmail.com wrote:
I too have been banging my head for RequestFactory error 'The
RequestFactory ValidationTool must be run for the '. I too have
requestfactory-apt.jar on buid path. Done checking eclipse('helios')
for annotation processing. I am quite frustrated at all and thinking
on moving over gwt. Do we have any explicit way to revoke the
validation tool or any straight solution to the problem like working
from command line to run Validation tool or are there any parameters
to give in run config. Please help!!! any link, any reference on net
to explain in depth what is this validation tool and why n how it
works. SOS!!
On Apr 22, 4:03 pm, Prashant Hegde prashant.he...@gmail.com wrote:
encountered the same issue today, solved by changing the directory name
from .apt_generated to .apt_generated1
Seems like that forces a revalidation.
Prashant
On 17-Apr-2012, at 1:08 AM, Felipe Stanham wrote:
I Know this is old but I just got stuck with the same problem. Did you
ever got around this and solved it?
I'm really frustrated, I've tried everything I knew of, everything any
blog speaks of and still no validation run!
PLEASE HELP!!!
On Sunday, January 15, 2012 12:32:56 AM UTC-2, TULC wrote:
I'm still stuck on this. Some projects I've ported to 2.4 now work,
but others still just won't budge. I have tried all the additional
steps, but my *DeobfuscatorBuilder.java just won't appear in those
projects (event thought the .apt_generated folder does, and is
replaced if I change the name). I have noticed some (though not all)
of those projects are now giving me the error build.properties does
not exist, which may or may not be related.
I'm frustrated to the point I'm considering ditching GWT altogether; I
haven't been able to proceed with any GWT development since the 2.4
upgrade. Like the man said, I'm good, really I am, but I just can't
figure this one out, and it really shouldn't be this hard. Thanks for
the breaking change.
Evan
On Dec 14 2011, 12:12 pm, dparish dpar...@gmail.com wrote:
I had the same problem. There are two other possible reasons you see
this:
1. Your java compliance level in the project is set to 1.5
2. Your classes are already compiled. I don't know why, but touching
the my RequestContext classes had NO affect until I deleted the
classes that were compiled before I added annotations. Now it all
works just fine.
Attention Google:
This stuff is w tooo complicated. I'm good. really I am, but
this is just misdirection at it's worst.
On Nov 20, 5:47 pm, oerten25 ozgur.er...@gmail.com wrote:
I've been getting the same error and tried the things mentioned in the
discussion without any luck. Finally i realised that i don't have the
apt_generated folder. So i changed the generated source directory
option to something other than apt_generated in Annotation
Processing setting. That fixed it.
On Oct 2, 11:29 pm, TULC evan.a.te...@gmail.com wrote:
I just get the sameerroras posted by Eric at the beginning of the
thread, but I have copied/pasted the full dump below.
Thomas, I'm not sure what you mean about the .apt_generated being in
my build path?
Thanks for the help, guys...
Evan
Console:
log4j:WARN No appenders could be found for logger
(org.apache.jasper.compiler.Js
pRuntimeContext).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig
for more in
fo.
03/10/2011 8:24:49 AM
com.google.web.bindery.requestfactory.server.RequestFactor
yServlet doPost
SEVERE: Unexpectederror
java.lang.RuntimeException:
TheRequestFactoryValidationToolmustberunfor th
e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory
RequestFactor
y type
at
com.google.web.bindery.requestfactory.vm.impl.Deobfuscator
$Builder.load(Deob
fuscator.java:59)
at
com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeo
b
fuscator(ResolverServiceLayer.java:43)
at
com.google.web.bindery.requestfactory.server.ResolverServiceLayer.resolveRe
q
uestFactory(ResolverServiceLayer.java:176)
at
com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR
e
questFactory(ServiceLayerDecorator.java:172)
at
com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR
e
questFactory(ServiceLayerDecorator.java:172)
at
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
No, it didn't, I tried everything suggested in the forum, now I am
thinking of upgrading helios to indigo may be that could help.
On Apr 28, 12:05 pm, Prashant Hegde prashant.he...@gmail.com wrote:
Have you tried renaming .apt_generated to .apt_generated1 (different from
.apt_generated) in the Compiler Settings Annotation processing section.
That worked for me.
Prashant
On 28-Apr-2012, at 11:59 AM, saurabh saurabh wrote:
Is there any chance if move on to maven or check 'Use google
appengine'( I am not using appengine) to make it work
On Apr 28, 11:13 am, saurabh saurabh saurabh.bl...@gmail.com wrote:
I too have been banging my head for RequestFactory error 'The
RequestFactory ValidationTool must be run for the '. I too have
requestfactory-apt.jar on buid path. Done checking eclipse('helios')
for annotation processing. I am quite frustrated at all and thinking
on moving over gwt. Do we have any explicit way to revoke the
validation tool or any straight solution to the problem like working
from command line to run Validation tool or are there any parameters
to give in run config. Please help!!! any link, any reference on net
to explain in depth what is this validation tool and why n how it
works. SOS!!
On Apr 22, 4:03 pm, Prashant Hegde prashant.he...@gmail.com wrote:
encountered the same issue today, solved by changing the directory name
from .apt_generated to .apt_generated1
Seems like that forces a revalidation.
Prashant
On 17-Apr-2012, at 1:08 AM, Felipe Stanham wrote:
I Know this is old but I just got stuck with the same problem. Did you
ever got around this and solved it?
I'm really frustrated, I've tried everything I knew of, everything any
blog speaks of and still no validation run!
PLEASE HELP!!!
On Sunday, January 15, 2012 12:32:56 AM UTC-2, TULC wrote:
I'm still stuck on this. Some projects I've ported to 2.4 now work,
but others still just won't budge. I have tried all the additional
steps, but my *DeobfuscatorBuilder.java just won't appear in those
projects (event thought the .apt_generated folder does, and is
replaced if I change the name). I have noticed some (though not all)
of those projects are now giving me the error build.properties does
not exist, which may or may not be related.
I'm frustrated to the point I'm considering ditching GWT altogether; I
haven't been able to proceed with any GWT development since the 2.4
upgrade. Like the man said, I'm good, really I am, but I just can't
figure this one out, and it really shouldn't be this hard. Thanks for
the breaking change.
Evan
On Dec 14 2011, 12:12 pm, dparish dpar...@gmail.com wrote:
I had the same problem. There are two other possible reasons you see
this:
1. Your java compliance level in the project is set to 1.5
2. Your classes are already compiled. I don't know why, but touching
the my RequestContext classes had NO affect until I deleted the
classes that were compiled before I added annotations. Now it all
works just fine.
Attention Google:
This stuff is w tooo complicated. I'm good. really I am, but
this is just misdirection at it's worst.
On Nov 20, 5:47 pm, oerten25 ozgur.er...@gmail.com wrote:
I've been getting the same error and tried the things mentioned in the
discussion without any luck. Finally i realised that i don't have the
apt_generated folder. So i changed the generated source directory
option to something other than apt_generated in Annotation
Processing setting. That fixed it.
On Oct 2, 11:29 pm, TULC evan.a.te...@gmail.com wrote:
I just get the sameerroras posted by Eric at the beginning of the
thread, but I have copied/pasted the full dump below.
Thomas, I'm not sure what you mean about the .apt_generated being in
my build path?
Thanks for the help, guys...
Evan
Console:
log4j:WARN No appenders could be found for logger
(org.apache.jasper.compiler.Js
pRuntimeContext).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig
for more in
fo.
03/10/2011 8:24:49 AM
com.google.web.bindery.requestfactory.server.RequestFactor
yServlet doPost
SEVERE: Unexpectederror
java.lang.RuntimeException:
TheRequestFactoryValidationToolmustberunfor th
e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory
RequestFactor
y type
at com.google.web.bindery.requestfactory.vm.impl.Deobfuscator
$Builder.load(Deob
fuscator.java:59)
at
com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeo
b
fuscator(ResolverServiceLayer.java:43)
at
com.google.web.bindery.requestfactory.server.ResolverServiceLayer.resolveRe
q
uestFactory(ResolverServiceLayer.java:176)
at
com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR
e
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
hey sorry prashant I mean thr yes I did renamed it.
On Apr 28, 12:56 pm, saurabh saurabh saurabh.bl...@gmail.com wrote:
No, it didn't, I tried everything suggested in the forum, now I am
thinking of upgrading helios to indigo may be that could help.
On Apr 28, 12:05 pm, Prashant Hegde prashant.he...@gmail.com wrote:
Have you tried renaming .apt_generated to .apt_generated1 (different from
.apt_generated) in the Compiler Settings Annotation processing section.
That worked for me.
Prashant
On 28-Apr-2012, at 11:59 AM, saurabh saurabh wrote:
Is there any chance if move on to maven or check 'Use google
appengine'( I am not using appengine) to make it work
On Apr 28, 11:13 am, saurabh saurabh saurabh.bl...@gmail.com wrote:
I too have been banging my head for RequestFactory error 'The
RequestFactory ValidationTool must be run for the '. I too have
requestfactory-apt.jar on buid path. Done checking eclipse('helios')
for annotation processing. I am quite frustrated at all and thinking
on moving over gwt. Do we have any explicit way to revoke the
validation tool or any straight solution to the problem like working
from command line to run Validation tool or are there any parameters
to give in run config. Please help!!! any link, any reference on net
to explain in depth what is this validation tool and why n how it
works. SOS!!
On Apr 22, 4:03 pm, Prashant Hegde prashant.he...@gmail.com wrote:
encountered the same issue today, solved by changing the directory name
from .apt_generated to .apt_generated1
Seems like that forces a revalidation.
Prashant
On 17-Apr-2012, at 1:08 AM, Felipe Stanham wrote:
I Know this is old but I just got stuck with the same problem. Did you
ever got around this and solved it?
I'm really frustrated, I've tried everything I knew of, everything any
blog speaks of and still no validation run!
PLEASE HELP!!!
On Sunday, January 15, 2012 12:32:56 AM UTC-2, TULC wrote:
I'm still stuck on this. Some projects I've ported to 2.4 now work,
but others still just won't budge. I have tried all the additional
steps, but my *DeobfuscatorBuilder.java just won't appear in those
projects (event thought the .apt_generated folder does, and is
replaced if I change the name). I have noticed some (though not all)
of those projects are now giving me the error build.properties does
not exist, which may or may not be related.
I'm frustrated to the point I'm considering ditching GWT altogether; I
haven't been able to proceed with any GWT development since the 2.4
upgrade. Like the man said, I'm good, really I am, but I just can't
figure this one out, and it really shouldn't be this hard. Thanks for
the breaking change.
Evan
On Dec 14 2011, 12:12 pm, dparish dpar...@gmail.com wrote:
I had the same problem. There are two other possible reasons you see
this:
1. Your java compliance level in the project is set to 1.5
2. Your classes are already compiled. I don't know why, but touching
the my RequestContext classes had NO affect until I deleted the
classes that were compiled before I added annotations. Now it all
works just fine.
Attention Google:
This stuff is w tooo complicated. I'm good. really I am, but
this is just misdirection at it's worst.
On Nov 20, 5:47 pm, oerten25 ozgur.er...@gmail.com wrote:
I've been getting the same error and tried the things mentioned in
the
discussion without any luck. Finally i realised that i don't have the
apt_generated folder. So i changed the generated source directory
option to something other than apt_generated in Annotation
Processing setting. That fixed it.
On Oct 2, 11:29 pm, TULC evan.a.te...@gmail.com wrote:
I just get the sameerroras posted by Eric at the beginning of the
thread, but I have copied/pasted the full dump below.
Thomas, I'm not sure what you mean about the .apt_generated being in
my build path?
Thanks for the help, guys...
Evan
Console:
log4j:WARN No appenders could be found for logger
(org.apache.jasper.compiler.Js
pRuntimeContext).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig
for more in
fo.
03/10/2011 8:24:49 AM
com.google.web.bindery.requestfactory.server.RequestFactor
yServlet doPost
SEVERE: Unexpectederror
java.lang.RuntimeException:
TheRequestFactoryValidationToolmustberunfor th
e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory
RequestFactor
y type
at
com.google.web.bindery.requestfactory.vm.impl.Deobfuscator
$Builder.load(Deob
fuscator.java:59)
at
com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeo
b
fuscator(ResolverServiceLayer.java:43)
at
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
If the project is maven based, try :
Right click on project - Run - Maven clean
and then hit F5 to revalidate the project
On Apr 28, 11:05 am, saurabh saurabh saurabh.bl...@gmail.com wrote:
hey sorry prashant I mean thr yes I did renamed it.
On Apr 28, 12:56 pm, saurabh saurabh saurabh.bl...@gmail.com wrote:
No, it didn't, I tried everything suggested in the forum, now I am
thinking of upgrading helios to indigo may be that could help.
On Apr 28, 12:05 pm, Prashant Hegde prashant.he...@gmail.com wrote:
Have you tried renaming .apt_generated to .apt_generated1 (different from
.apt_generated) in the Compiler Settings Annotation processing section.
That worked for me.
Prashant
On 28-Apr-2012, at 11:59 AM, saurabh saurabh wrote:
Is there any chance if move on to maven or check 'Use google
appengine'( I am not using appengine) to make it work
On Apr 28, 11:13 am, saurabh saurabh saurabh.bl...@gmail.com wrote:
I too have been banging my head for RequestFactory error 'The
RequestFactory ValidationTool must be run for the '. I too have
requestfactory-apt.jar on buid path. Done checking eclipse('helios')
for annotation processing. I am quite frustrated at all and thinking
on moving over gwt. Do we have any explicit way to revoke the
validation tool or any straight solution to the problem like working
from command line to run Validation tool or are there any parameters
to give in run config. Please help!!! any link, any reference on net
to explain in depth what is this validation tool and why n how it
works. SOS!!
On Apr 22, 4:03 pm, Prashant Hegde prashant.he...@gmail.com wrote:
encountered the same issue today, solved by changing the directory
name from .apt_generated to .apt_generated1
Seems like that forces a revalidation.
Prashant
On 17-Apr-2012, at 1:08 AM, Felipe Stanham wrote:
I Know this is old but I just got stuck with the same problem. Did
you ever got around this and solved it?
I'm really frustrated, I've tried everything I knew of, everything
any blog speaks of and still no validation run!
PLEASE HELP!!!
On Sunday, January 15, 2012 12:32:56 AM UTC-2, TULC wrote:
I'm still stuck on this. Some projects I've ported to 2.4 now work,
but others still just won't budge. I have tried all the additional
steps, but my *DeobfuscatorBuilder.java just won't appear in those
projects (event thought the .apt_generated folder does, and is
replaced if I change the name). I have noticed some (though not all)
of those projects are now giving me the error build.properties does
not exist, which may or may not be related.
I'm frustrated to the point I'm considering ditching GWT altogether;
I
haven't been able to proceed with any GWT development since the 2.4
upgrade. Like the man said, I'm good, really I am, but I just can't
figure this one out, and it really shouldn't be this hard. Thanks
for
the breaking change.
Evan
On Dec 14 2011, 12:12 pm, dparish dpar...@gmail.com wrote:
I had the same problem. There are two other possible reasons you see
this:
1. Your java compliance level in the project is set to 1.5
2. Your classes are already compiled. I don't know why, but
touching
the my RequestContext classes had NO affect until I deleted the
classes that were compiled before I added annotations. Now it all
works just fine.
Attention Google:
This stuff is w tooo complicated. I'm good. really I am,
but
this is just misdirection at it's worst.
On Nov 20, 5:47 pm, oerten25 ozgur.er...@gmail.com wrote:
I've been getting the same error and tried the things mentioned in
the
discussion without any luck. Finally i realised that i don't have
the
apt_generated folder. So i changed the generated source
directory
option to something other than apt_generated in Annotation
Processing setting. That fixed it.
On Oct 2, 11:29 pm, TULC evan.a.te...@gmail.com wrote:
I just get the sameerroras posted by Eric at the beginning of the
thread, but I have copied/pasted the full dump below.
Thomas, I'm not sure what you mean about the .apt_generated being
in
my build path?
Thanks for the help, guys...
Evan
Console:
log4j:WARN No appenders could be found for logger
(org.apache.jasper.compiler.Js
pRuntimeContext).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN
Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig
for more in
fo.
03/10/2011 8:24:49 AM
com.google.web.bindery.requestfactory.server.RequestFactor
yServlet doPost
SEVERE: Unexpectederror
java.lang.RuntimeException:
TheRequestFactoryValidationToolmustberunfor th
e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
See http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation There are recipes for Eclipse, the command line, and Maven. Choose your poison. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/nRQPsTvbri4J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
encountered the same issue today, solved by changing the directory name from .apt_generated to .apt_generated1 Seems like that forces a revalidation. Prashant On 17-Apr-2012, at 1:08 AM, Felipe Stanham wrote: I Know this is old but I just got stuck with the same problem. Did you ever got around this and solved it? I'm really frustrated, I've tried everything I knew of, everything any blog speaks of and still no validation run! PLEASE HELP!!! On Sunday, January 15, 2012 12:32:56 AM UTC-2, TULC wrote: I'm still stuck on this. Some projects I've ported to 2.4 now work, but others still just won't budge. I have tried all the additional steps, but my *DeobfuscatorBuilder.java just won't appear in those projects (event thought the .apt_generated folder does, and is replaced if I change the name). I have noticed some (though not all) of those projects are now giving me the error build.properties does not exist, which may or may not be related. I'm frustrated to the point I'm considering ditching GWT altogether; I haven't been able to proceed with any GWT development since the 2.4 upgrade. Like the man said, I'm good, really I am, but I just can't figure this one out, and it really shouldn't be this hard. Thanks for the breaking change. Evan On Dec 14 2011, 12:12 pm, dparish dpar...@gmail.com wrote: I had the same problem. There are two other possible reasons you see this: 1. Your java compliance level in the project is set to 1.5 2. Your classes are already compiled. I don't know why, but touching the my RequestContext classes had NO affect until I deleted the classes that were compiled before I added annotations. Now it all works just fine. Attention Google: This stuff is w tooo complicated. I'm good. really I am, but this is just misdirection at it's worst. On Nov 20, 5:47 pm, oerten25 ozgur.er...@gmail.com wrote: I've been getting the same error and tried the things mentioned in the discussion without any luck. Finally i realised that i don't have the apt_generated folder. So i changed the generated source directory option to something other than apt_generated in Annotation Processing setting. That fixed it. On Oct 2, 11:29 pm, TULC evan.a.te...@gmail.com wrote: I just get the sameerroras posted by Eric at the beginning of the thread, but I have copied/pasted the full dump below. Thomas, I'm not sure what you mean about the .apt_generated being in my build path? Thanks for the help, guys... Evan Console: log4j:WARN No appenders could be found for logger (org.apache.jasper.compiler.Js pRuntimeContext). log4j:WARN Please initialize the log4j system properly. log4j:WARN Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig for more in fo. 03/10/2011 8:24:49 AM com.google.web.bindery.requestfactory.server.RequestFactor yServlet doPost SEVERE: Unexpectederror java.lang.RuntimeException: TheRequestFactoryValidationToolmustberunfor th e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory RequestFactor y type at com.google.web.bindery.requestfactory.vm.impl.Deobfuscator $Builder.load(Deob fuscator.java:59) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeo b fuscator(ResolverServiceLayer.java:43) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.resolveRe q uestFactory(ResolverServiceLayer.java:176) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l .java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.getOrCache(S e rviceLayerCache.java:233) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.resolveReque s tFactory(ServiceLayerCache.java:198) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process ( SimpleRequestProcessor.java:207) at
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
Would clean project fix that too? Have a good day, Brandon Donnelson c.gawkat.com -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I Know this is old but I just got stuck with the same problem. Did you ever got around this and solved it? I'm really frustrated, I've tried everything I knew of, everything any blog speaks of and still no validation run! PLEASE HELP!!! On Sunday, January 15, 2012 12:32:56 AM UTC-2, TULC wrote: I'm still stuck on this. Some projects I've ported to 2.4 now work, but others still just won't budge. I have tried all the additional steps, but my *DeobfuscatorBuilder.java just won't appear in those projects (event thought the .apt_generated folder does, and is replaced if I change the name). I have noticed some (though not all) of those projects are now giving me the error build.properties does not exist, which may or may not be related. I'm frustrated to the point I'm considering ditching GWT altogether; I haven't been able to proceed with any GWT development since the 2.4 upgrade. Like the man said, I'm good, really I am, but I just can't figure this one out, and it really shouldn't be this hard. Thanks for the breaking change. Evan On Dec 14 2011, 12:12 pm, dparish dpar...@gmail.com wrote: I had the same problem. There are two other possible reasons you see this: 1. Your java compliance level in the project is set to 1.5 2. Your classes are already compiled. I don't know why, but touching the my RequestContext classes had NO affect until I deleted the classes that were compiled before I added annotations. Now it all works just fine. Attention Google: This stuff is w tooo complicated. I'm good. really I am, but this is just misdirection at it's worst. On Nov 20, 5:47 pm, oerten25 ozgur.er...@gmail.com wrote: I've been getting the same error and tried the things mentioned in the discussion without any luck. Finally i realised that i don't have the apt_generated folder. So i changed the generated source directory option to something other than apt_generated in Annotation Processing setting. That fixed it. On Oct 2, 11:29 pm, TULC evan.a.te...@gmail.com wrote: I just get the sameerroras posted by Eric at the beginning of the thread, but I have copied/pasted the full dump below. Thomas, I'm not sure what you mean about the .apt_generated being in my build path? Thanks for the help, guys... Evan Console: log4j:WARN No appenders could be found for logger (org.apache.jasper.compiler.Js pRuntimeContext). log4j:WARN Please initialize the log4j system properly. log4j:WARN Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig for more in fo. 03/10/2011 8:24:49 AM com.google.web.bindery.requestfactory.server.RequestFactor yServlet doPost SEVERE: Unexpectederror java.lang.RuntimeException: TheRequestFactoryValidationToolmustberunfor th e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory RequestFactor y type at com.google.web.bindery.requestfactory.vm.impl.Deobfuscator $Builder.load(Deob fuscator.java:59) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeo b fuscator(ResolverServiceLayer.java:43) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.resolveRe q uestFactory(ResolverServiceLayer.java:176) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l .java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.getOrCache(S e rviceLayerCache.java:233) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.resolveReque s tFactory(ServiceLayerCache.java:198) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process ( SimpleRequestProcessor.java:207) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process ( SimpleRequestProcessor.java:127) at com.google.web.bindery.requestfactory.server.RequestFactoryServlet.doPost(R e questFactoryServlet.java:133) at
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I also noticed that -strict flag should not be used for GWT compiler. Compiler prints error message but code works well... -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/dMhEbp92Ci4J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
BTW, i use *requestfactory-client+src.jar* and * requestfactory-server+src.jar* which contains source files of this libraries. Without this sources requestfactory doesn't works. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/R2Lgk-Th638J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
Been a couple weeks since anyone chimed in on this issue. Has anyone solved this? I am experiencing the same issues. On Jan 15, 3:53 am, Thomas Broyer t.bro...@gmail.com wrote: Eclipse seems to have issues with annotation processors (it regularly generates errors when I modify source code; generally it resolves itself after either a new change, a refresh or a rebuild). Is your app working if you compile your code outside Eclipse? As for your build.properties does not exist error, have a look athttp://stackoverflow.com/questions/1226642/why-do-i-get-a-warning-bui... -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I ended up solving my problem. I think the validation stuff that puts stuff in that .apt_generated folder was failing, but not reporting it to the eclipse console or problems tabs. My application is spread over 2 projects (so far). I have one project that is basically a bunch of classes that were generated by jaxws. The second project is the GWT project that contains my requestFactory stuff. I was creating an EntityProxy in my GWT project that was a proxyfor one of those Jaxws generated objects. After following all the directions, I was not getting anything in my .apt_generated directory (Just like Evan was reporting). I discovered that when I removed my EntityProxy for the jaxws genned object, the .apt_generated folder would populate. Adding it back in would cause it to go away again. After some investigation, I ended up adding a bunch of jars to my GWT-project's classpath so that it matched the classpath of my jaxws-project. After that, it all worked. I suspect that the GWT annotation-processor/validation stuff was failing with some classpath related problems and not reporting it. --Rob On Jan 27, 12:21 pm, Rob Whiteside rob.whites...@gmail.com wrote: Been a couple weeks since anyone chimed in on this issue. Has anyone solved this? I am experiencing the same issues. On Jan 15, 3:53 am, Thomas Broyer t.bro...@gmail.com wrote: Eclipse seems to have issues with annotation processors (it regularly generates errors when I modify source code; generally it resolves itself after either a new change, a refresh or a rebuild). Is your app working if you compile your code outside Eclipse? As for your build.properties does not exist error, have a look athttp://stackoverflow.com/questions/1226642/why-do-i-get-a-warning-bui... -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
Eclipse seems to have issues with annotation processors (it regularly generates errors when I modify source code; generally it resolves itself after either a new change, a refresh or a rebuild). Is your app working if you compile your code outside Eclipse? As for your build.properties does not exist error, have a look at http://stackoverflow.com/questions/1226642/why-do-i-get-a-warning-build-properties-does-not-exist -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/kQ-kcG_fnZUJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I'm still stuck on this. Some projects I've ported to 2.4 now work, but others still just won't budge. I have tried all the additional steps, but my *DeobfuscatorBuilder.java just won't appear in those projects (event thought the .apt_generated folder does, and is replaced if I change the name). I have noticed some (though not all) of those projects are now giving me the error build.properties does not exist, which may or may not be related. I'm frustrated to the point I'm considering ditching GWT altogether; I haven't been able to proceed with any GWT development since the 2.4 upgrade. Like the man said, I'm good, really I am, but I just can't figure this one out, and it really shouldn't be this hard. Thanks for the breaking change. Evan On Dec 14 2011, 12:12 pm, dparish dpar...@gmail.com wrote: I had the same problem. There are two other possible reasons you see this: 1. Your java compliance level in the project is set to 1.5 2. Your classes are already compiled. I don't know why, but touching the my RequestContext classes had NO affect until I deleted the classes that were compiled before I added annotations. Now it all works just fine. Attention Google: This stuff is w tooo complicated. I'm good. really I am, but this is just misdirection at it's worst. On Nov 20, 5:47 pm, oerten25 ozgur.er...@gmail.com wrote: I've been getting the same error and tried the things mentioned in the discussion without any luck. Finally i realised that i don't have the apt_generated folder. So i changed the generated source directory option to something other than apt_generated in Annotation Processing setting. That fixed it. On Oct 2, 11:29 pm, TULC evan.a.te...@gmail.com wrote: I just get the sameerroras posted by Eric at the beginning of the thread, but I have copied/pasted the full dump below. Thomas, I'm not sure what you mean about the .apt_generated being in my build path? Thanks for the help, guys... Evan Console: log4j:WARN No appenders could be found for logger (org.apache.jasper.compiler.Js pRuntimeContext). log4j:WARN Please initialize the log4j system properly. log4j:WARN Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig for more in fo. 03/10/2011 8:24:49 AM com.google.web.bindery.requestfactory.server.RequestFactor yServlet doPost SEVERE: Unexpectederror java.lang.RuntimeException: TheRequestFactoryValidationToolmustberunfor th e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory RequestFactor y type at com.google.web.bindery.requestfactory.vm.impl.Deobfuscator $Builder.load(Deob fuscator.java:59) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeo b fuscator(ResolverServiceLayer.java:43) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.resolveRe q uestFactory(ResolverServiceLayer.java:176) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l .java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.getOrCache(S e rviceLayerCache.java:233) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.resolveReque s tFactory(ServiceLayerCache.java:198) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process ( SimpleRequestProcessor.java:207) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process ( SimpleRequestProcessor.java:127) at com.google.web.bindery.requestfactory.server.RequestFactoryServlet.doPost(R e questFactoryServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 487) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler .java:1097) at com.google.gwt.sample.dynatablerf.server.SchoolCalendarService.doFilter(Sch o olCalendarService.java:89) at org.mortbay.jetty.servlet.ServletHandler
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I had the same problem. There are two other possible reasons you see this: 1. Your java compliance level in the project is set to 1.5 2. Your classes are already compiled. I don't know why, but touching the my RequestContext classes had NO affect until I deleted the classes that were compiled before I added annotations. Now it all works just fine. Attention Google: This stuff is w tooo complicated. I'm good. really I am, but this is just misdirection at it's worst. On Nov 20, 5:47 pm, oerten25 ozgur.er...@gmail.com wrote: I've been getting the same error and tried the things mentioned in the discussion without any luck. Finally i realised that i don't have the apt_generated folder. So i changed the generated source directory option to something other than apt_generated in Annotation Processing setting. That fixed it. On Oct 2, 11:29 pm, TULC evan.a.te...@gmail.com wrote: I just get the sameerroras posted by Eric at the beginning of the thread, but I have copied/pasted the full dump below. Thomas, I'm not sure what you mean about the .apt_generated being in my build path? Thanks for the help, guys... Evan Console: log4j:WARN No appenders could be found for logger (org.apache.jasper.compiler.Js pRuntimeContext). log4j:WARN Please initialize the log4j system properly. log4j:WARN Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig for more in fo. 03/10/2011 8:24:49 AM com.google.web.bindery.requestfactory.server.RequestFactor yServlet doPost SEVERE: Unexpectederror java.lang.RuntimeException: TheRequestFactoryValidationToolmustberunfor th e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory RequestFactor y type at com.google.web.bindery.requestfactory.vm.impl.Deobfuscator $Builder.load(Deob fuscator.java:59) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeo b fuscator(ResolverServiceLayer.java:43) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.resolveRe q uestFactory(ResolverServiceLayer.java:176) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l .java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.getOrCache(S e rviceLayerCache.java:233) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.resolveReque s tFactory(ServiceLayerCache.java:198) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process ( SimpleRequestProcessor.java:207) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process ( SimpleRequestProcessor.java:127) at com.google.web.bindery.requestfactory.server.RequestFactoryServlet.doPost(R e questFactoryServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 487) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler .java:1097) at com.google.gwt.sample.dynatablerf.server.SchoolCalendarService.doFilter(Sch o olCalendarService.java:89) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler .java:1088) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 360) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: 216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: 181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java: 729) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 405) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java: 49 ) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I've been getting the same error and tried the things mentioned in the discussion without any luck. Finally i realised that i don't have the apt_generated folder. So i changed the generated source directory option to something other than apt_generated in Annotation Processing setting. That fixed it. On Oct 2, 11:29 pm, TULC evan.a.te...@gmail.com wrote: I just get the sameerroras posted by Eric at the beginning of the thread, but I have copied/pasted the full dump below. Thomas, I'm not sure what you mean about the .apt_generated being in my build path? Thanks for the help, guys... Evan Console: log4j:WARN No appenders could be found for logger (org.apache.jasper.compiler.Js pRuntimeContext). log4j:WARN Please initialize the log4j system properly. log4j:WARN Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig for more in fo. 03/10/2011 8:24:49 AM com.google.web.bindery.requestfactory.server.RequestFactor yServlet doPost SEVERE: Unexpectederror java.lang.RuntimeException: TheRequestFactoryValidationToolmustberunfor th e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory RequestFactor y type at com.google.web.bindery.requestfactory.vm.impl.Deobfuscator $Builder.load(Deob fuscator.java:59) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeo b fuscator(ResolverServiceLayer.java:43) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.resolveRe q uestFactory(ResolverServiceLayer.java:176) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveR e questFactory(ServiceLayerDecorator.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l .java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.getOrCache(S e rviceLayerCache.java:233) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.resolveReque s tFactory(ServiceLayerCache.java:198) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process ( SimpleRequestProcessor.java:207) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process ( SimpleRequestProcessor.java:127) at com.google.web.bindery.requestfactory.server.RequestFactoryServlet.doPost(R e questFactoryServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 487) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler .java:1097) at com.google.gwt.sample.dynatablerf.server.SchoolCalendarService.doFilter(Sch o olCalendarService.java:89) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler .java:1088) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 360) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: 216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: 181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java: 729) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 405) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java: 49 ) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java: 505) at org.mortbay.jetty.HttpConnection $RequestHandler.content(HttpConnection.java: 843) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:647) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java: 395) at org.mortbay.thread.QueuedThreadPool $PoolThread.run(QueuedThreadPool.java:488 ) [ERROR]500- POST /gwtRequest (127.0.0.1) 1420 bytes Request headers Host: 127.0.0.1: Connection: keep-alive Content-Length: 163
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
When I added the option verbose=false to the Annotation Processing the .apt_generated folder got populated with the blaFactoryObfuscatorBuilder(s)and then it got also compiled to the classes directory in the war. I can only underline the importance of this option (strange as it might seem). Gregor -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/NMziSSVBQqMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
Evan, The extra steps I had to go through to get the annotation processor to run were to remove all the m2e (and everything provided by Sonatype, Inc) components from my Eclipse install, and then to a clean re-install of the Maven Integration for WTP package and all of its dependencies. The different versions of the Maven integration plugins were fighting with each other. I don't know if that will help your problem or not, but it might help out anyone who sees this error on a SpringSource STS + GWT + Maven project. --- Eric Andresen On Sun, Oct 2, 2011 at 4:29 PM, TULC evan.a.te...@gmail.com wrote: I just get the same error as posted by Eric at the beginning of the thread, but I have copied/pasted the full dump below. Thomas, I'm not sure what you mean about the .apt_generated being in my build path? Thanks for the help, guys... Evan Console: log4j:WARN No appenders could be found for logger (org.apache.jasper.compiler.Js pRuntimeContext). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more in fo. 03/10/2011 8:24:49 AM com.google.web.bindery.requestfactory.server.RequestFactor yServlet doPost SEVERE: Unexpected error java.lang.RuntimeException: The RequestFactory ValidationTool must be run for th e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory RequestFactor y type at com.google.web.bindery.requestfactory.vm.impl.Deobfuscator $Builder.load(Deob fuscator.java:59) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeob fuscator(ResolverServiceLayer.java:43) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.resolveReq uestFactory(ResolverServiceLayer.java:176) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveRe questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveRe questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveRe questFactory(ServiceLayerDecorator.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.getOrCache(Se rviceLayerCache.java:233) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.resolveReques tFactory(ServiceLayerCache.java:198) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process( SimpleRequestProcessor.java:207) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process( SimpleRequestProcessor.java:127) at com.google.web.bindery.requestfactory.server.RequestFactoryServlet.doPost(Re questFactoryServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 487) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler .java:1097) at com.google.gwt.sample.dynatablerf.server.SchoolCalendarService.doFilter(Scho olCalendarService.java:89) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler .java:1088) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 360) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: 216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: 181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java: 729) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 405) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java: 49 ) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java: 505) at org.mortbay.jetty.HttpConnection $RequestHandler.content(HttpConnection.java: 843) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:647) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I just get the same error as posted by Eric at the beginning of the thread, but I have copied/pasted the full dump below. Thomas, I'm not sure what you mean about the .apt_generated being in my build path? Thanks for the help, guys... Evan Console: log4j:WARN No appenders could be found for logger (org.apache.jasper.compiler.Js pRuntimeContext). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more in fo. 03/10/2011 8:24:49 AM com.google.web.bindery.requestfactory.server.RequestFactor yServlet doPost SEVERE: Unexpected error java.lang.RuntimeException: The RequestFactory ValidationTool must be run for th e com.google.gwt.sample.dynatablerf.shared.DynaTableRequestFactory RequestFactor y type at com.google.web.bindery.requestfactory.vm.impl.Deobfuscator $Builder.load(Deob fuscator.java:59) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.updateDeob fuscator(ResolverServiceLayer.java:43) at com.google.web.bindery.requestfactory.server.ResolverServiceLayer.resolveReq uestFactory(ResolverServiceLayer.java:176) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveRe questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveRe questFactory(ServiceLayerDecorator.java:172) at com.google.web.bindery.requestfactory.server.ServiceLayerDecorator.resolveRe questFactory(ServiceLayerDecorator.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.getOrCache(Se rviceLayerCache.java:233) at com.google.web.bindery.requestfactory.server.ServiceLayerCache.resolveReques tFactory(ServiceLayerCache.java:198) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process( SimpleRequestProcessor.java:207) at com.google.web.bindery.requestfactory.server.SimpleRequestProcessor.process( SimpleRequestProcessor.java:127) at com.google.web.bindery.requestfactory.server.RequestFactoryServlet.doPost(Re questFactoryServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 487) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler .java:1097) at com.google.gwt.sample.dynatablerf.server.SchoolCalendarService.doFilter(Scho olCalendarService.java:89) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler .java:1088) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 360) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: 216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: 181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java: 729) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 405) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java: 49 ) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java: 505) at org.mortbay.jetty.HttpConnection $RequestHandler.content(HttpConnection.java: 843) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:647) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java: 395) at org.mortbay.thread.QueuedThreadPool $PoolThread.run(QueuedThreadPool.java:488 ) [ERROR] 500 - POST /gwtRequest (127.0.0.1) 1420 bytes Request headers Host: 127.0.0.1: Connection: keep-alive Content-Length: 163 Origin: http://127.0.0.1: X-GWT-Permutation: HostedMode pageurl: http://127.0.0.1:/DynaTableRf.html?gwt.codesvr=127.0.0.1:9997 User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.2 (KHTML, like Ge cko) Chrome/15.0.854.0 Safari/535.2 Content-Type: application/json; charset=UTF-8 Accept: */* Referer: http://127.0.0.1:/DynaTableRf.html?gwt.codesvr=127.0.0.1:9997 Accept-Encoding: gzip,deflate,sdch Accept-Language:
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I had also assumed the verbose=false line wasn't necessary, but unfortunately even with that option I still get the same error. My steps are: - enable project specific settings (Java Compiler/Annotation Processing) - enable annotation processing - enable processing in editor - .apt_generated is already listed as the generated source directory - add verbose=false processor option - enable project specific settings (Java Compiler/Annotation Processing/Factory Path) - add C:\Program Files\Eclipse\Indigo\plugins \com.google.gwt.eclipse.sdkbundle_2.4.0.r37v2011083017107\gwt-2.4.0\requestfactory- apt.jar - debug as Web Application I got quite excited when I read your reply, despite how dumb I would feel if that was all it took to fix the problem... I just can't quite work out what I'm doing wrong! Thanks for your help, Evan On Sep 23, 5:03 pm, Jonas jonas.zumk...@gmail.com wrote: Hi, this Wiki entry helped me to solve the problem:http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterf... Do exactly what is shown in the printscreens and it should work. If it's not working tell exactly what you did. I almost got crazy and did see that they added verbose=false to Annotation Processing. I thought this isn't necessary as they didn't mention it in the text. I was wrong. Jonas -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
When you run the application, you should get errors in the Development Mode or Console Tabs. Can you post them? You get there some good hints where to look for the problem. 2011/10/1 TULC evan.a.te...@gmail.com I had also assumed the verbose=false line wasn't necessary, but unfortunately even with that option I still get the same error. My steps are: - enable project specific settings (Java Compiler/Annotation Processing) - enable annotation processing - enable processing in editor - .apt_generated is already listed as the generated source directory - add verbose=false processor option - enable project specific settings (Java Compiler/Annotation Processing/Factory Path) - add C:\Program Files\Eclipse\Indigo\plugins \com.google.gwt.eclipse.sdkbundle_2.4.0.r37v2011083017107\gwt-2.4.0\requestfactory- apt.jar - debug as Web Application I got quite excited when I read your reply, despite how dumb I would feel if that was all it took to fix the problem... I just can't quite work out what I'm doing wrong! Thanks for your help, Evan On Sep 23, 5:03 pm, Jonas jonas.zumk...@gmail.com wrote: Hi, this Wiki entry helped me to solve the problem: http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterf... Do exactly what is shown in the printscreens and it should work. If it's not working tell exactly what you did. I almost got crazy and did see that they added verbose=false to Annotation Processing. I thought this isn't necessary as they didn't mention it in the text. I was wrong. Jonas -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I don't remember if it matters or not (tried updating my project to 2.4 some time ago, haven't finished, and temporary tolled back) but is the .apt_generated in your build path? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/n1_DRd1gZSAJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
Hi, this Wiki entry helped me to solve the problem: http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation Do exactly what is shown in the printscreens and it should work. I'm not an experienced Java programmer and it was very difficult for me to understand all the concepts that are used with the RequestFactory. If anyone stumples upon a nice in depth explanation: Please let me know. Jonas -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/WO50iuxCwWIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
Hi, this Wiki entry helped me to solve the problem: http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation Do exactly what is shown in the printscreens and it should work. If it's not working tell exactly what you did. I almost got crazy and did see that they added verbose=false to Annotation Processing. I thought this isn't necessary as they didn't mention it in the text. I was wrong. Jonas -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/n951hlf9LmwJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I have not yet been able to get past this problem... I am simply trying to run the DynaTableRF from the samples in eclipse. I have the latest GPE installed. I have followed the instructions at http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation for eclipse and have also tried adding requestfactory-apt.jar to the eclipse project build path manually. I am not using Maven. I have tried adding all the requestfactory-* JARs to the build path, even though I understand requestfactory-client.jar is supposed to be included in gwt-user.jar and similarly with requestfactory-server.jar in gwt-servlet.jar. I have also tried putting both requestfactory- server.jar and requestfactory-apt.jar into the WEB-INF/lib directory. But it keeps failing with this error. Can anyone help me?? Cheers, Evan -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
In Eclipse I only had to make RequestFactory interfaces and their server domain counterparts to be available on the sourcepath during the compilation process. This seemed to be enough to validate RF interfaces and generate additional Java types. The deployed app worked after this. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/SJNPxqe7ZJ0J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
Hi Eric, Look for a class named *YourRequestFactory*DeobfuscatorBuilder in the WAR. This will be present if the RF validation tool has run. We're currently working on an issue where it gets wiped out in Maven projects in Eclipse Indigo. /dmc On Thu, Sep 15, 2011 at 12:45 PM, Eric Andresen ericandre...@gmail.comwrote: I just upgraded to 2.4, and am seeing the following problem when I try to run my server: SEVERE: Unexpected error java.lang.RuntimeException: The RequestFactory ValidationTool must be run for the XX RequestFactory type at com.google.web.bindery.requestfactory.vm.impl.Deobfuscator$Builder.load(Deobfuscator.java:59) I followed the instructions at http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation to turn on annotation processing in Eclipse and add the requestfactory-apt to it, and I was able to see the annotation processor flag errors between my Request types and my Services. (those errors are now fixed) Is there anything else I need to do in order to convince the deployed web-app that its RequestFactory was validated? Or anything I can look for in the deployed WAR to determine if in fact the validation was run or not? Thanks, Eric -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/ze3TX70785EJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- David Chandler Developer Programs Engineer, GWT+GAE w: http://code.google.com/ b: http://turbomanage.wordpress.com/ b: http://googlewebtoolkit.blogspot.com/ t: @googledevtools -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
@David, my post here https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/-4gaablGx8I is how I got rfvalidator-apt working with m2e in indigo. If you have questions, let me know. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/B_0bIAdym-EJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
I'm using M2E and Indigo, so it looks like I might be running into this problem. I don't see the *DeobfuscatorBuilder in my WAR anywhere. I'll take a look through Jeff's link below and see if that helps me at all. Thanks, Eric -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/9JAsK58ubDUJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: The RequestFactory ValidationTool must be run for the RequestFactory type
Thanks, Jeff. That's some pretty fine Maven wizardry. What we've discovered is that with the lifecycle mapping POM hacks in place, the ValidationTool does in fact run under Indigo, but the WTP publish operation that happens just prior to launch does not have access to the newly-generated sources in the workspace without a refresh. We're working on a GPE fix to address this as well as simplifying the POM by using built-in annotation processing rather than a separate exec. /dmc On Thu, Sep 15, 2011 at 1:44 PM, Jeff Larsen larse...@gmail.com wrote: @David, my post here https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/-4gaablGx8I is how I got rfvalidator-apt working with m2e in indigo. If you have questions, let me know. -- David Chandler Developer Programs Engineer, GWT+GAE w: http://code.google.com/ b: http://turbomanage.wordpress.com/ b: http://googlewebtoolkit.blogspot.com/ t: @googledevtools -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
