Even if it doesn't complain about the annotations... I don't think
this really addresses the problem, does it? If your annotations are
in your client-side code, they aren't going to be used, are they? It
seems to me that putting them there just confuses matters. This goes
back to what some of the first responses indicated... people don't
read the FAQ nor understand how they are supposed to program in GWT.
The way I think about it is quite simple - you break down every GWT
project into two main pieces... you have client-side code (GWT -->
Javascript), and server-side code (Java, PHP, whatever you feel like
doing). The client-side code has many constraints because it is what
will be compiled into Javascript and sent to the browser. You
obviously cannot access a Hibernate object directly from your browser,
so you have to come up with some way to do it indirectly (as Vitali
suggested). And yes, I know... there's another piece which ties the
two together ("Controller" code) - but that's a bit arbitrary. The
fact is, GWT makes Javascript... therefore, if it can't be done in
Javascript, it should not be in your client-side GWT code.
On Mar 17, 6:13 am, Jason Morris <lem...@gmail.com> wrote:
> As far as I know it won't complain (doesn't complain when I use annotations
> from EoD SQL).
>
> The best way to find out is write a test class with some annotations and try
> compile it ;)
>
> //J
>
> djd wrote:
> > For hibernate entity beans, can I use hibernate's specific
> > annotations? I never actually tried it, since we've mapped them
> > using .hbm.xml config files. But will GWT ignore the annotations or,
> > better said, how do I map entity beans using annotations without
> > making GWT scream about the imports? :)
>
> > On Mar 17, 5:41 am, Ian Petersen <ispet...@gmail.com> wrote:
> >> On Mon, Mar 16, 2009 at 7:29 PM, Joe Cole <profilercorporat...@gmail.com>
> >> wrote:
> >>> Even better: make the error message in gwt be super-specific. That way
> >>> people won't need to go to the FAQ.
> >>> Error: The class X was not in one of the gwt-compilation folders
> >>> (a,b,c). Since gwt only compiles code below these folders into
> >>> javascript your class was removed from compilation. Your options are
> >>> to: 1) provide a replacement class (seehttp://faq) , 2) rewrite the
> >>> functionality you need to a reachable class or 3) move the class into
> >>> one of the folders reachable by your modules.
> >> That sounds like a good idea, but it seems like lots of people are
> >> already not reading the existing error messages. Adding more text is
> >> only going to create more problems, I think.
>
> >> Ian
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
