gmane.org.google.gwt

Re: Handling Violations controlled by groups or Violations not found by default validation

Jens — 2013-05-21T12:58:32

By default, GWT calls validator.validate(domain) in 
ReflectiveServiceLayer.validate(), but you probably want 

if(domain.getId() == null) {
  return validator.validate(domain, CreateGroup.class);
}
return validator.validate(domain, Server/DefaultGroup.class);

You can do this by providing a custom ServiceLayerDecorator to 
RequestFactoryServlet and implement ServiceLayerDecorator.validate(T 
domain) accordingly.

Re: MVP For Popups

David — 2013-05-21T12:56:19

Typically you would have a Presenter that  initializes your view ( the 
static dom) , loads your view with data from an  async server invocation , 
and receives requests from the view for more data .   Have a look at 
https://developers.google.com/web-toolkit/articles/mvp-architecture-2.

Apart from dispatching url place requests via browser History, I personally 
hold off from using the event bus until  I have a situation where multiple 
views may be interested in a single event or a given view is reused by many 
use cases with different presenters.            The EventBus also is handy 
for managing a model cache (broadcasting model changes to interested views).

Here's a recent video from last weeks Google IO :
https://www.youtube.com/watch?v=kilmaSRq49g   .  The EventBus is covered 
about halfway in.

David


On Monday, May 20, 2013 8:15:22 AM UTC-4, Tim Hill wrote:

Re: Handling Violations controlled by groups or Violations not found by default validation

Alex opn — 2013-05-21T12:21:50

I just ran into the same issue. As there is no way to get or change the 
SimpleRequestProcessor im stuck now! Have you found out anything more, 
Michael Wiles?

Am Mittwoch, 27. März 2013 10:52:24 UTC+1 schrieb Michael Wiles:

Re: IE9 problem with GWT

Juan Pablo Gardella — 2013-05-21T11:03:22

How do you show messages?


2013/5/21 Mike <miguelaz9686-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>

Re: JPA issue: A parent cannot be established or changed once an object has been persisted.

Juan Pablo Gardella — 2013-05-21T11:02:02

You should persist company before persist Tradesman or attach to an
existent company. This relation should be explicit. Create
company.addTrademan(Trademan t) method:

company.addTrademan(Trademan t){
users.add(t);
t.setCompany(this);
}

Call this in a transactional method.

Juan






2013/5/21 Nermin <user113-Mmb7MZpHnFY< at >public.gmane.org>

IE9 problem with GWT

Mike — 2013-05-21T10:48:41


GWT Release: 2.5.0

Browser: IE9
Our clients have a problem using our web application because, on IE9, when the application shows a message (i.e., to confirm if a file is uploaded or not), the focus
remains behind the message shown and it is impossible to interact with the message, so you can't close it and you can't work with the application either.
It is not a problem of the application code, it is a problem of the version 9 of IE, it does not happen with IE 10.
The message shown is modal.

I know it is an alternative using Mozilla or Google Chrome, but our client is a little bit special, so he does not want to use other web browsers.

Any idea? Has this problem happened to someone else?

P.D.: Sorry if there is any mistake in the grammar or in some word.

Re: JPA issue: A parent cannot be established or changed once an object has been persisted.

Nermin — 2013-05-21T10:41:10

Dear Juan,

I tried *< at >ManyToOne(optional=false)*, unfortunately no changes.
In my current setting, the < at >PrePersist is called only once. (I see it on 
system out) That means: no multiple attempts to persist Tradesman entity.

However, it looks to me that whenever I change parameters on the Tradesman 
entity JPA creates/persists for some reason the Tradesman in the DB, 
independently from the Company entity.
I use Standard GWT settings: GWT 2.5, DataNucleus on Appengine Datastore.

The scenario I am describing here is a standard scenario you will face when 
using GWT with JPA. I am surprised that my code is not working.
< at >PrePersist works fine as long as the Entity is not in a owned relation 
with other entities.

Does anyone has an idea what could be wrong here?

Thank you!!

Nermin

< at >Thomas: Thank you for the advise. I will 

Am Dienstag, 21. Mai 2013 12:01:43 UTC+2 schrieb Juan Pablo Gardella:

Re: JPA issue: A parent cannot be established or changed once an object has been persisted.

Juan Pablo Gardella — 2013-05-21T10:01:43

Update your entity as:

< at >Entity
public class Tradesman extends User{
    < at >ManyToOne(optional=false)
    private Company company;

    *< at >PrePersist*
    public void hashPassword(){
        setPassword(BCrypt.hashpw(**entity.getPassword(), BCrypt.gensalt());
    }

And then check where are you persisting Tradesman without company.



2013/5/21 Thomas Broyer <t.broyer-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>

Re: JPA issue: A parent cannot be established or changed once an object has been persisted.

Thomas Broyer — 2013-05-21T09:57:49


On Tuesday, May 21, 2013 11:18:42 AM UTC+2, Nermin wrote:

You're not reaching the appropriate group ;-)

I suppose you're using AppEngine (form what I know of JPA, I can't see a 
reason for that kind of message, unless you're using JPA on AppEngine), in 
which case you can ask for support on StackOverflow: 
https://developers.google.com/appengine/community

JPA issue: A parent cannot be established or changed once an object has been persisted.

Nermin — 2013-05-21T09:18:42

Dear GWT developers,

I have a "probably simple" problem with my application which I am obviously 
not able to solve.

Two Classes: Company, Tradesman

< at >Entity
public class Company {
    < at >OneToMany(cascade = CascadeType.ALL, mappedBy = "company")
    private List<Tradesman> users = new ArrayList<Tradesman>();

....
}


< at >Entity
public class Tradesman extends User{
    < at >ManyToOne
    private Company company;

    *< at >PrePersist*
    public void hashPassword(){
        setPassword(BCrypt.hashpw(entity.getPassword(), BCrypt.gensalt());
    }

*JSR 303 validation on GWT is activated.*

Here is the *error message:
*Detected attempt to establish Company(no-id-yet) as the parent of 
Tradesman(356) but the entity identified by Tradesman(356) has already been 
persisted without a parent.  A parent cannot be established or changed once 
an object has been persisted.

My problem is obviously that when I change some parameters within the 
Tradesman entity within the *< at >PrePersist* method, a new child entity is 
created.
In

Re: problem with javax.servlet.ServletContext in gwt-user.jar

Gabriele Prandini — 2013-05-21T09:12:31

Thanks Jens, i thik the problem is what you explain


2013/5/21 Thomas Broyer <t.broyer-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>

Re: Super dev mode - sourcemap not working anymore

Juan Pablo Gardella — 2013-05-21T08:55:55

I don't know what is your problem, but try
https://groups.google.com/forum/?fromgroups#!topic/google-web-toolkit/78Hl47eFPKw
.


2013/5/21 Martones <ludovit.martonyik-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>

Re: problem with javax.servlet.ServletContext in gwt-user.jar

Thomas Broyer — 2013-05-21T08:54:40


On Tuesday, May 21, 2013 10:30:44 AM UTC+2, gabriele.prandini wrote:

Er, you're running Tomcat at compile-time? (or is the blog you linked to 
actually unrelated to your issue?)

Deleting the servletcontext.class in the jar resolved the problem
The correct fix is that you shouldn't compile your server-side classes with 
gwt-user. I don't know Grails build system and I don't know how the Grails 
GWT plugin works (heck I don't actually know Grails but by name), so I 
can't tell how to solve your problem in Grails, but you should only use 
gwt-user for client-side code, and use gwt-servlet for server-side code 
(and for deployment).
You should ask the Grails-GWT guys.

Re: problem with javax.servlet.ServletContext in gwt-user.jar

Jens — 2013-05-21T08:38:38

During compilation you have a servlet 3.0 vs. servlet 2.5 (which is 
embedded in gwt-user.jar/gwt-servlet.jar) mismatch. Make sure you have 
servlet 3.0 api on classpath before gwt-user.jar.

Re: problem with javax.servlet.ServletContext in gwt-user.jar

Gabriele Prandini — 2013-05-21T08:30:44

I'm not deployng the app...
the error comes in compile time.

Deleting the servletcontext.class in the jar resolved the problem


2013/5/21 Thomas Broyer <t.broyer-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>

Re: Super dev mode - sourcemap not working anymore

Martones — 2013-05-21T08:28:03

Hello Brian, thanks for your answer. 

I tested the Showcase sample from the 2.5.1 GA bundle and the issue is the 
same. SDM works well for me. Here is my compilation result which states 
that source maps are well enabled :

   Compiling 1 permutation
      Compiling permutation 0...
      Source Maps Enabled
   Compile of permutations succeeded
Linking into <my path>
   Link succeeded
   Compilation succeeded -- 27,468s
Compile completed in 27825 ms

In Chrome I have "Enable source maps" checked. But I see no java in my 
source tab or the CTRL-o window. Using GWT 2.5.1. 

Many thanks,

Ludovit

Re: Offline debugging my gwt app

Thomas Broyer — 2013-05-21T00:51:53


On Monday, May 20, 2013 8:46:08 PM UTC+2, yves wrote:

Is hosted.html / devmode.js (depending on your linker) available offline? 
(i.e. included in the appcache manifest)

Re: problem with javax.servlet.ServletContext in gwt-user.jar

Thomas Broyer — 2013-05-21T00:47:19


On Monday, May 20, 2013 10:27:17 AM UTC+2, gabriele.prandini wrote:

How is it that gwt-user is deployed? It's only needed at compile-time and 
must not be deployed (gwt-servlet should, if you use GWT-RPC)

Re: Offline debugging my gwt app

yves — 2013-05-20T21:18:18

Thanks for your answer, but my question is about the HTML5 offline feature. 
Sorry if my post was not clear.

The problem is that I can't debug the GWT app while running it without a 
connection to the site server, thus "offline".

Yves

Re: Offline debugging my gwt app

Joseph Lust — 2013-05-20T21:10:35

It is not clear what you're attempting here. By "Offline" I believe you 
mean when not using the "DevMode" debugging plugin. You can only debug with 
the debugger when running in debugging mode. You can however use source 
maps and set breakpoints in the browser (i.e. Chrome Dev Tools) if you like 
without using DevMode.

Beyond that, to run your GWT app while not in the DevMode plugin, you'll 
need to compile and deploy it to a server (i.e. Jetty, Tomcat, JBoss) and 
start it. If you try to run it *not* in DevMode, but with the codesvr 
parameter in the URL, it will fail as it thinks you're trying to use 
DevMode.


Hope that helps.

Sincerely,
Joseph

Re: Web Component support/usage?

Ed Bras — 2013-05-20T19:36:01

Thanks for the update.
Are things like these kind of "news" items put some where in the future ?
Maybe "better" use of the gwt blog ?


On Mon, May 20, 2013 at 9:23 PM, Goktug Gokdogan <goktug-hpIqsD4AKlfQT0dZR+AlfA< at >public.gmane.org> wrote: