Yeah, i see. You implement manual version control in your project.
But, I decided to use RF in my project to forget about transmission domain
objects between server and client.
In general, it is unclear why the guys at Google have made the RF this way.
On Wednesday, June 10, 2015 at 2:51:48
On Wednesday, June 10, 2015 at 12:21:03 PM UTC+2, Anton Mityagin wrote:
In general, it is unclear why the guys at Google have made the RF this way.
If you look at the changes between the various milestones and RCs of GWT
2.1, and then 2.1.1 and 2.2, you'll see that RF is totally different
Undoubtedly, RF - greate thing. I use it and plan to continue to use.
The more that I get to make workaround for those things that do not exist
in RF.
Just very strange that such a good thing as RF does not support such basic
things like optimistic locking, refire request after excpetion.
We made a similar approach using the client/server version variables. But
we call it version/expectedVersion.
class MyEntity {
@Version int version;
public int getExpectedVersion() { return null; }
public void setExpectedVersion(int v) { this.version = v; }
public int getVersion() { return
Thanks for your comment
On Tuesday, June 9, 2015 at 10:12:10 PM UTC+3, Ignacio Baca Moreno-Torres
wrote:
We made a similar approach using the client/server version variables. But
we call it version/expectedVersion.
As explained in stackoverflow
We don't use RequestFactory but GWT-RPC with Eclipselink + optimistic
locking and heavy auto saving. Because we don't want to live with the extra
query when doing the em.find / detach / update version / merge dance we
simply do the version check manually in the app. Also we don't send
versions
IMO using attached entities in RF is dangerous because in hibernate any
committed transaction will persist any previous change in the current
context. So, if you are using per-request entityManager, whenever you call
transaction.commit you will persist any modification sent from the client
Thank you. I will implement one of the strategies mentioned there.
Jens jens.nehlme...@gmail.com wrote:Thats a known quirk. Take a look at:
https://groups.google.com/d/topic/google-web-toolkit/d9gZMff7RlI/discussion
-- J.
--
You received this message because you are subscribed to the Google
I have found out a few more details relating to this problem.
I have an Editor that implements LeafValueEditorListPhoneProxy.
When a user wants to add a new PhoneProxy to my editor I call
context.create().
Sometimes the user cancels the process.
When the user cancels the process the
Thats a known quirk. Take a look at:
https://groups.google.com/d/topic/google-web-toolkit/d9gZMff7RlI/discussion
-- J.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
This was recently discussed in this GWT Group
post.https://groups.google.com/forum/?fromgroups#!topic/google-web-toolkit/NStp5K8Ej2o
On Tuesday, July 3, 2012 6:18:09 AM UTC-4, nessrinovitta wrote:
Hello everyone !
Does the RequestFactory API allow us to build Web Services with the REST
Okay, I have some questions:
1) Have you developed a web application?
2) What framework, pattern or technology you have used for
development? Spring or EJB3?
I ask these questions, because the development will be the same, using
GWT, JSF, Flex or pure html. So I advise you before making any crud
What is your doubt in relation to RF and hibernate?
because the RF will communicate with your service and domain. Part of
persistence will continue in the same way the only difference is that
you will have an interface that represents the service and an
interface for the domain as the link below:
Make the following change to your web.xml and see if it will funionar:
servlet
servlet-namerequestFactoryServlet/servlet-name
servlet-
classcom.google.web.bindery.requestfactory.server.RequestFactoryServlet/
servlet-class
init-param
hi
thinks a lot
first I want to thanks you for these superb on GWT RequestFactory, they
really helped me getting started quickly.
i don't now about symbolMaps , i think it is google datastore, but i am
trying to store in mysql database.
i created a web application with GWT RequestFactory
Caused by: java.lang.RuntimeException: Server Error:
null at
com.google.web.bindery.requestfactory.shared.Receiver.onFailure(Receiver.java:44)
So I would say you most likely have a Nullpointer Exception on server side
while executing a service method.
-- J.
--
You received this message
Have u tried to override the onFailure and onviolation methods in ur Receiver?
They give you better clarity on the error?
Do u any constraints/ validation on the entity? If they are not met your
request would fail
Thanks
Ashwin
Sent from my iPhone
On Sep 15, 2011, at 1:24 PM, POODevelopper
I executed a JUnit Test on the services and there was no null pointer
Exception.
Also there is no constraint validation on the Entity. How can I make
the exception message more clear ??
Below the Code of the entity :
@Document(collection=transactions)
public class Transaction implements
Put a breakpoint in
com.google.web.bindery.requestfactory.server.DefaultExceptionHandler, or
provide your own ExceptionHandler to the RequestFactoryServlet to log the
exceptions (with their stacktrace).
--
You received this message because you are subscribed to the Google Groups
Google Web
Thank you guys for the hint, I used this article to set up a proper
Exception handling :
http://cleancodematters.wordpress.com/2011/05/29/improved-exceptionhandling-with-gwts-requestfactory/
I have found that the Property destTransactionId was Null.
GWT need to handle Exceptions well Out of the
+1
On Jul 18, 9:25 am, Elhanan Maayan elh.mailg...@gmail.com wrote:
i think google should clarify it's own philosophy in a special article in
the developer guide, because as of right now , there way too many black
holes on the subject of transports and frameworks that use them
GWT-RPC
JSON
Works like charm, thanks a lot for the post!
--
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/-/C6JsuJVunwYJ.
To post to this group, send email to
Thanks for share!
2011/8/10 j.singh.developer j.singh.develo...@gmail.com
The blog discussed in one of my post is no longer in production. If
you looking for the GWT + Spring integration solution, please visit
this
link
Hi,
Thanks for this encouragement.
I am a newby at GWT/App Engine and want to start creating applications
that follow Google's philiosofy.
Later (when I am more comfortable) I probably can add my own patterns
and stuff.
The main lesson I learned from this discussion is that GWT-RPC comes
with
i think google should clarify it's own philosophy in a special article in
the developer guide, because as of right now , there way too many black
holes on the subject of transports and frameworks that use them
GWT-RPC
JSON
RequestFactory
AutoBeans
XML.
i know that autobeans and rtf both uses
woo hoo! mabye i'll get to convince our CTO to use RF, he wants to avoid
that becouse he says if the client will be in sliverlight, that won't work.
On Fri, Jul 15, 2011 at 7:27 PM, David Chandler drfibona...@google.comwrote:
We jumped the gun a bit, but 2.4 is pretty close to becoming latest
Hmm, shouldn't it have been for trunk? I believe @ExtraTypes and
polymorphism support are not in 2.3, only in the upcoming 2.4.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
considering it's talking about requestfactory-server.jar hmm, pretty much
yea:) (is 2.4 THAT close?)
On Fri, Jul 15, 2011 at 11:38 AM, Thomas Broyer t.bro...@gmail.com wrote:
Hmm, shouldn't it have been for trunk? I believe @ExtraTypes and
polymorphism support are not in 2.3, only in the
We jumped the gun a bit, but 2.4 is pretty close to becoming latest :-)
/dmc
On Friday, July 15, 2011, Thomas Broyer wrote:
Hmm, shouldn't it have been for trunk? I believe @ExtraTypes and
polymorphism support are not in 2.3, only in the upcoming 2.4.
--
You received this message because
If you use GWT-RPC and JPA (with Hibernate provider) you will have
serialization
problemshttp://code.google.com/intl/es/webtoolkit/articles/using_gwt_with_hibernate.html.
To solution this, you have this alternatives:
1) Use DTO
2) Use Gilead
3) Use a
With ValueProxy, you can with RequestFactory do everything you would with
GWT-RPC (well, with the major exception of polymorphism –though this will be
fixed soon– and transportable types –which don't include java.util.Map for
instance, though once again will be fixed in due time–).
GWT-RPC can
I'm using RequestFactory for a 'non-data-orientated' app and its works
very nicely.
Chained method invocation:
MyServiceRC serviceRequest = appRequestFactory.MyServiceRC();
serviceRequest.giveMeAString().to(stringReceiver);
if (needPojo == true)
serviceRequest.giveMeAPojo().to(pojoReceiver);
FYI, bobv updated the RF developer guide yesterday with a separate section
on transportable types, discussion of polymorphic type-mapping rules, and
slight re-wording of the Overview section.
http://code.google.com/webtoolkit/doc/latest/DevGuideRequestFactory.html
/dmc
On Thu, Jul 14, 2011 at
Just glad to be able to give a little something back after all the help this
forum has given me :-)
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
Eric,
I was stuck on this for a couple of days... Thanks a lot for the help
If my thing ever becomes a commercial success, keep this email as your IOU
:-)
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web
Yes everything looks good. And as i pointed out above there seems to
be
sort of a type check against the base class which is located in the
old package.
Am i wrong with that?
I am still not able to run my application :(
On 5 Mai, 23:51, David Chandler drfibona...@google.com wrote:
QBiT,
Have
I saw this same problem in my environment. In my case I had upgraded all of
the RequestFactory references in my Java classes to the new package, but
forgot to switch the RequestFactoryServlet class in my web.xml file:
servlet
servlet-namerequestFactoryServlet/servlet-name
Eric,
thanks a lot. You figured it out, that was exactly the problem.
Now everything works as expected.
Problem solved.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to
QBiT,
Have you cleaned your project? I was seeing some weirdness in RF after
moving to 2.3, then realized I still had the GWT 2.2 jar on the classpath...
/dmc
On Thu, May 5, 2011 at 10:19 AM, QBiT qbit0...@googlemail.com wrote:
Hello,
when i refactored my sources to fit the new package
I would personal like to see a layer that considered base types,
beyond Object of the concrete type. However it seems that Entity
should really just be simple POJOs, even if the interface is just
exposing getter and setters. Maybe someone from the GWT team will have
some inspiration on this
Thanks Thomas and John for for your inputs. Would you see this
workaround as the default behaviour in future GWT releases?
On 18 fév, 18:13, John Maitland jfgmaitl...@googlemail.com wrote:
I had the same problem and managed to implement a new
ServiceLayerDecorator. See..
IIRC, the only blocker is the RequestFactoryInterfaceValidator (RFIV), which
stops looping over super classes as soon as it finds java.lang.Object (and
implemented interfaces come after Object in the list of super classes
being iterated).
This means it could be worked around by using a
I had the same problem and managed to implement a new
ServiceLayerDecorator. See..
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/36d0ed4f87be/45af985914ac1780?lnk=gstq=maitland#45af985914ac1780
Regards,
John
--
You received this message because you are subscribed
You can't do these things yet, but we've been discussing them.
On Thu, Feb 3, 2011 at 5:08 AM, Krishna krishnacal...@gmail.com wrote:
Hi,
Does RequestFactory EntityProxy supports AutoBean Category (http://
code.google.com/p/google-web-toolkit/wiki/AutoBean#Categories) ?
i. e. Can I define
Thanks for your reply Miroslav,
unortunatelly when i am trying to Run as Web Application in Eclipse, i
got this error:
Initializing AppEngine server
Logging to JettyLogger(null) via
com.google.apphosting.utils.jetty.JettyLogger
Successfully processed C:\development\springsource\workspace
Hello,
Are you sure that all jar from lib folder are added in your classpath ?
It seems that guice-servlet-3.0-rc1.jar is missing.
Also you can check whether you have only one version of guice in your
classpath.
--
You received this message because you are subscribed to the Google Groups
Hello Miroslav,
sorry, my fault. You are right. Now everything works. I will test your
example. Can you explain to me, why i better to use Injection of
RequestFactory?
Many thanks,
Lubor
On 19 led, 13:10, Miroslav Genov mge...@gmail.com wrote:
Hello,
Are you sure that all jar from lib folder
In my example, dependency injection is used over the server side service
classes, so I can inject into them other classes using DI. This gives me the
ability to test my services in isolation and also few more advantages such
as scopes and etc.
--
You received this message because you are
I had a small sample project that could help:
https://github.com/mgenov/injecting-request-factory
I don't know how simple is it, but it may help you some how.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send
Thank you Thomas, that was all, you are very helpful.
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
thank you Thomas. Before trying the new service layer, I have looked
this thread,
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/846564e9fc303be0,
to understand how it works. I have pasted my code here.
http://paste.pocoo.org/show/310712/.
It must be a mis-declaration of
You declared your method as InstanceRequestUserProxy, Void, i.e. this is
an instance method of UserProxy, that returns void. If your method is in
your service, then it has to be a RequestVoid and takes the
UserProxy/UserDAO as argument.
--
You received this message because you are subscribed
Hi I am trying to use the service layer of GWT 2.1.1. I have created
the infrastracture meaning:
1. An entity proxy, entity and entity locator
2. A request, a service and a service locator
I am using an interface which I annotate as service, and which I
implement. Everything works ok, except that
On Tuesday, December 28, 2010 12:19:37 AM UTC+1, giannisdag wrote:
Hi I am trying to use the service layer of GWT 2.1.1. I have created
the infrastracture meaning:
1. An entity proxy, entity and entity locator
2. A request, a service and a service locator
I am using an interface which
I cannot understand how I could persist a domain object, using the new
service layer. Because when I call
pm.makePersistent(arg);
I need to have access to the instance of the domain object that is
going to be stored. Before, I could just write
pm.makePersistent(this);
according to the example,
from your explanation I get the feeling that Locators are DAOs,
is this correct ?
placing calls like these: EntityManager#find(clazz,id) inside a
Locator,
means Locator is now responsible for accessing datastore to perform
actions.
it also means that our DAOs are somehow directly coupled with
RequestFactory sends diffs on the wire (client-to-server), so how would your
Service Object (as you call it) would receive a complete domain object if
the diff isn't applied to an object retrieved from the database/datastore?
Things are a bit more blury than service layer on top of data access
Thank you so much for your feedback on this.
I am going to experiment more, using your guidelines.
as for the need for additional layer,
a valid use case could be this:
lets say you are going to deploy your app on GAE.
for the persistence, there are several options:
- JDO/JPA
- DataStore
SL vs DAL,
one example of how they are different is that:
let's say
we have a DAO for accessing a Customer entity
a DAO for accessing Account entity
a DAO for accessing History/Trend entity
// maybe not a good example, but just three separate entities
a Service(object) living in a ServiceLayer,
On Wednesday, December 22, 2010 12:59:16 AM UTC+1, zixzigma wrote:
Thank you, it all makes sense now.
However what you described is how GWT RF uses those details
to do its magic behind the scenes.
I am not clear what our responsibility is then ?
Provide the right values so RF can do
I use the same pattern explained here with JPA/Spring for the Entity Locator
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/20ea2aea53aa29d3/687ff2df944c483c
public class MyDataLocator extends LocatorMyData, Long {
private MyRepository getRepository() {
Added an issue for this:
http://code.google.com/p/google-web-toolkit/issues/detail?id=5794
--
Bob Vawter
Google Web Toolkit Team
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
I realized I was using the 2.1 style to create my RequestFactory
I came across this, while digging into code:
* ServiceLayer serviceLayer = ServiceLayer.create();
* SimpleRequestProcessor processor = new
SimpleRequestProcessor(serviceLayer);
* EventBus eventBus = new SimpleEventBus();
*
From the RequestFactory documentation:
Four special methods are required on all entities as they are used by
the RequestFactory servlet:
A no-arg constructor. This may be the implicit default constructor.
1. id_type getId() -- IDs can be String or Long
2. static entity_type findEntity(id_type id)
@ProxyFor(value = Person.class, locator = PersonLocator.class)
then having a PersonLocator which implements LocatorPerson would fix this
for you.
But in order to get your static service methods (besides just the find
method), you need a ServiceLocator for your service:
@Service(value =
On Dec 21, 6:25 am, Matt Moriarity matt.moriar...@gmail.com wrote:
But in order to get your static service methods (besides just the find
method), you need a ServiceLocator for your service:
do all these methods have to be static ?
I thought the idea behind 2.1.1 was to get rid of static ?
in RequestFactory 2.1.1 documentations (source code),
there are many references to Domain and Domain Environment,
I am unclear what is meant by Domain Environment.
is it on the server side where RequestFactory work stops and our work
begins ?
it helps if the documentaton clarify the vocabulary,
Thank you guys for the tips.
I got it to work!
Thank you very much !
I noticed a VERY STRANGE behaviour.
following your suggestion, I declared:
@ProxyFor(MyPersonEntity, EntityLocator)
PersonProxy
@Service(MyPersonService, MyServiceLocator)
PersonService
I noticed when methods in
The getId method is used generate a stable id that's transmitted to the
client so that the object can be identified when it's later updated, and the
find() method (see below) can be called with the appropriate identifier. You
don't have to define a getId() in your EntityProxy, and if you do,
Thank you, it all makes sense now.
However what you described is how GWT RF uses those details
to do its magic behind the scenes.
I am not clear what our responsibility is then ?
What should go inside the Locator ?
From the code I posted,
http://paste.pocoo.org/show/308153/
I don't know what I
On Mon, Dec 20, 2010 at 3:10 PM, Matt Moriarity
matt.moriar...@gmail.com wrote:
I'm attempting to switch to using RequestFactory instead of GWT-RPC and
manually creating DTOs. It's been going pretty well, except I've hit one
use-case that is just a brick wall.
I have a panel that is an
tracked down the problem,
it has to do with validation: RequestFactoryInterfaceValidator
this validation fails:
RequestFactoryInterfaceValidator v = new
RequestFactoryInterfaceValidator(
logger, new RequestFactoryInterfaceValidator.
On 9 nov, 03:01, David Chandler drfibona...@google.com wrote:
It's still too early to call a release date. The RequestFactory
enhancements are in code review and should be going into trunk
shortly. See http://gwt-code-reviews.appspot.com/1062801/show
Or maybe they're already there:
I guess this is the relevant part :
A new Proxy interface will be added as a superclass of ValueProxy
and EntityProxy to allow RequestFactory.create to operate on both
value and entity types.
Because ValueProxy doesn't have a stableId() method, there's no way to
use a VP with a call to find() or
On 9 nov, 18:07, koma k...@koma.be wrote:
I guess this is the relevant part :
A new Proxy interface will be added as a superclass of ValueProxy
and EntityProxy to allow RequestFactory.create to operate on both
value and entity types.
I don't see Proxy and ValueProxy in any code review
Koen,
RequestFactory doesn't yet support the transfer of value types, only
entity types. It's on tap for 2.1.1:
http://code.google.com/p/google-web-toolkit/wiki/RequestFactory_2_1_1
/dmc
On Mon, Nov 8, 2010 at 6:31 PM, koma k...@koma.be wrote:
Hi,
My entities are persisted via JDO in the
Hi,
When is the 2.1.1 release planned for? Is there some of this already
in the trunk?
Regards,
Tobias
On Nov 9, 1:26 am, David Chandler drfibona...@google.com wrote:
Koen,
RequestFactory doesn't yet support the transfer of value types, only
entity types. It's on tap for 2.1.1:
It's still too early to call a release date. The RequestFactory
enhancements are in code review and should be going into trunk
shortly. See http://gwt-code-reviews.appspot.com/1062801/show
/dmc
On Mon, Nov 8, 2010 at 7:50 PM, Tobias thaberm...@gmail.com wrote:
Hi,
When is the 2.1.1 release
78 matches
Mail list logo
