Marcin,
Not sure if you figured it out or not yet, but we had a similar issue and
ours was fixed when fixed two issues:
- we were creating the objects with two separate request contexts. If I
understand correctly how the persisting works, you must create any
sub-proxies with the same
What I meant is that, to me, it's unrelated to RequestFactory proper, and at
least totally a server thing (it doesn't matter what your ProductProxy looks
like, it's what the Product looks like on the server side that matters,
because only the Product/ProductProxy EntityProxyId will go over the w
On Apr 26, 1:08 am, Thomas Broyer wrote:
> What's validated is the Product object. When Product#findProduct loads the
> product, does it also load the Group list?
Group is loaded. Double, if you add following lines
ProductMarginRequest request =
requestFactory.productMarginRequest();
On Monday, April 25, 2011 10:59:58 PM UTC+2, Marcin Makowski wrote:
>
> hello,
>
> I have problem with complex object tree being passed from client side
> to server side via RequestFactory:
>
> my proxy interfaces for my model:
>
> @ProxyFor(value = ProductMargin.class, locator =
> ProductMa
hello,
I have problem with complex object tree being passed from client side
to server side via RequestFactory:
my proxy interfaces for my model:
@ProxyFor(value = ProductMargin.class, locator =
ProductMarginLocator.class)
public interface ProductMarginProxy extends EntityProxy {
public lon
