Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-07-13 Thread Drew Spencer
Ahhh I see... for some reason I thought there might be a situation where an attacker could see objects from the outside but not see the properties if they were private - must have been an assumption I made years ago and it stuck with me! You're a legend, Jeff. Drew -- You received this

Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-07-12 Thread Drew Spencer
Thanks for the great reply as always Jeff. In contrast to you, my app is going to be used only by employees of my company, so preferably I would like to have all data sent over the wire encrypted. We're talking about employees of my company accessing data about our clients - so it is very

Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-07-12 Thread Jeff Schnitzer
The public/private/protected/package status of java fields is 100% irrelevant from a security perspective. It's just there to help keep your code clean. The data is still being passed across the wire in a simple, easily-decoded protocol that any sniffer can translate. If you're passing

Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-07-05 Thread Jeff Schnitzer
That's what I tend to do. Since I write consumer apps, passing my raw entities across the wire usually isn't an option in the first place - there's usually too much security-sensitive stuff, or at the very least data I would rather not disclose to a potential attacker. Also... using entities

Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-06-30 Thread Drew Spencer
Thanks guys. So basically I should be grabbing the Supplies and Suppliers on the server side, combining the data I need from both into a SupplyDTO object, and passing that back to the client, rather than doing the processing on the client? Seems to make sense! Drew -- You received this

[appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-06-28 Thread Drew Spencer
Hey coders, wasn't sure whether to put this in the objectify group or here, so I went for here. I have a many-to-one relationship that is causing me a headache. I am using a CellTable to display the data for this entity: class Supply { @Id private Long id; private String number; private String

Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-06-28 Thread Bruno Fuster
Hello Drew, I don't know much about GWT, but what I think you need to create a new object to handle this data, like a wrapper that should have all the information you need (number, consumption, supplier name) or @Transient properties into the entity object. So you need to get the suppliers from

Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-06-28 Thread Drew Spencer
Thanks for the info, Bruno. So you are saying I need a kind of proxy entity that wraps the needed data from both objects? I think I may need a custom cell after doing a little more reading. There must be a simple way. Also I think I should have posted this in the GWT group. :/ -- You

Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-06-28 Thread Bruno Fuster
Modeling your views based on your domains/entities can give you some headaches. In this case you can simple use a @Transient value, but if it grows, create a new object to handle these 2 entities. You could even replicate the supplier name to make it easier and less RPC calls. But if your

Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-06-28 Thread Drew Spencer
Well I am just trying to get some kind of demo program running and learn about cells/celltable while I go because my app needs to display lots of tabular data and I understand this is the fastest way to do it. What I am doing is this: Get the supplies (List) Loop the supplies, adding each

Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-06-28 Thread Jeff Schnitzer
To be honest, whenever I start to have a less-than-perfect match between my entities and the content rendered in my client, I usually create DTOs. It's mildly annoying, but it results in a clean interface without a lot of extra payload (some of which might be security-sensitive) sent across the

Re: [appengine-java] Best way to work with a CellTable and many-to-one relationship with objectify?

2011-06-28 Thread Bruno Fuster
I'm with you Jeff. DTOs are the way to go in these cases. On Tue, Jun 28, 2011 at 3:09 PM, Jeff Schnitzer j...@infohazard.org wrote: To be honest, whenever I start to have a less-than-perfect match between my entities and the content rendered in my client, I usually create DTOs. It's