gmane.org.google.gwt

Re: Offline debugging my gwt app

yves — 2013-05-21T17:36:28

Yes hosted.html is included in the CACHE section of the manifest.
I don't have a "devmode.js" file.
Yves

Re: Testing GWT without GwtTestCase

Thad — 2013-05-21T17:28:12

On Monday, May 20, 2013 2:14:42 PM UTC-4, Goktug Gokdogan wrote:

Is that safe? My services makes heavy use of the HttpSession. At a minimum, 
I store the user's connection to the legacy server app I work with, but 
there are other things, too--tables last queried, images retrieved, etc. 
This is why I wish I could override getThreadLocalRequest() with a mock for 
testing.

To have an entirely separate class, I'd have to instantiate it with each 
RPC call so the session object wouldn't get stomped on by another user. I'm 
worried about that overhead once I'm out of development and test and into 
production. Failing that I could pass the session in with the call, but 
then I don't see the point of a separate class. I could just have something 
like this for each public method.

< at >Override
public LoginInfo doLogin(String server, String name, String passwd) {
  return doLogin(getThreadLocalRequest().getSession(true), server, name, 
password);
}

private LoginInfo doLogin(HttpSession session, String server, String name, 
String passwd) {
  MyApp app = new MyApp();
  // prep more params and log in
  ...
  app.login(server, name, passwd, param0...);
  // remember session
  ...
  return app.getLoginInfo();
}

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

Alfredo Quiroga — 2013-05-21T16:29:54

Or use a cascade persist, merge to force creation or merge respectively

Sent from my iPhone

On May 21, 2013, at 7:02 AM, Juan Pablo Gardella <gardellajuanpablo-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

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

Thomas Broyer — 2013-05-21T15:06:02

From the point of view of RF, these are just an exception thrown by the 
service method, like any other.
If you want to communicate failure to your client with specific 
information, then you have to make your service method return a response 
object containing the status (success/failure) and the details about the 
failure. onFailure is about *exceptional cases*, i.e. things that should 
*not* happen.

If it were me, I'd remove bean validation from RF entirely. It was useful 
when and meaningful when RF had optimistic locking (back in its really 
early days in the first GWT 2.1 milestones), but currently it's just 
confusing: because you send a diff, validation could fail not because you 
failed on the client-side, but because someone else modified a field that 
you didn't touch, and now conflicts with a field you modified on the 
client; now how do you fix that?
Keep RF automatic validation only for field-level syntactic / range 
validation, not for anything else; and for "business rules" inside service 
methods, they're just errors like any other, so treat them as such (see 
above)

On Tuesday, May 21, 2013 4:13:52 PM UTC+2, Alex opn wrote:

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

Alex opn — 2013-05-21T14:13:52

Thanks for your answer!

Well...propably I'm abusing bean validation (?), but in my case that 
doesn't help (actually I'm already doing it like this with different 
groups).

I'll try to explain my problem:

Basically I've got two validation groups which both should be run on the 
server-side: Client and Server 

Client: These validators should be run when an object enters the server 
from the client (in the ServiceLayerDecorator)
Server: These validators should be run before persist / update etc happens 
(in my DAOs)

The reason why I separated it like this is that there are some class level 
constraints which may be violated when an object enters the server that 
should get corrected in the service method afterwards, but for safety be 
checked again before updating the database.

So far that works good and was pretty easy to implement:

ServiceLayerDecorator:

    < at >Override
    public <T> Set<ConstraintViolation<T>> validate(T domainObject) {
        return validator.validate(domainObject, Client.class);
    }

But ViolationExceptions occuring later are, as Michael already explained 
pretty well, reported as ServerFailures, not as ConstraintViolations -> 
non-resusable RequestContext, no error messages shown etc :-/

I already tried to copy/paste SimpleRequestProcessor & 
RequestFactoryServlet (into com.google... package structure) to change it 
to my needs. I have to admit though that I couldn't figure out how to catch 
all exceptions and not handle ConstraintViolationExceptions as server 
failures. I would already be happy with that although it feels a bit hacky 
:)! 

Am Dienstag, 21. Mai 2013 14:58:32 UTC+2 schrieb Jens:

Re: IE9 problem with GWT

Honza Rames — 2013-05-21T14:00:07

If you display the message in DialogBox (or PopupPanel), are you displaying 
glass to darken the window? If so doesn't the glass overlap your message? 
It could be a problem of layouting, are you using multiple z-orders in your 
app? These issues should be easy to figure out in developer tools that are 
present in IE9.

Honza

On Tuesday, May 21, 2013 12:48:41 PM UTC+2, Mike wrote:

Re: Super dev mode - sourcemap not working anymore

Martones — 2013-05-21T13:48:46

I tryed to reinstall the bookmark, this didnt help. But thanks for your tip 
;)

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 case I do not touch any parameter, in the < at >PrePersist, everything works 
fine.

What am I doing wrong here?

Thank you in advance:

Nermin

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.