Objects loaded from queries don't always connect properly to their related objects about java-sdk HOT 3 CLOSED

Hi David,

I have tried a few different scenarios to reproduce this issue, but everything is working as expected; however, I'd like to get a little more clarity as to exactly what you were doing when you encountered this issue:

1. Does Subscription look up to Application which looks up to Vendor? Just want to make sure I understand your data model correctly.
2. What is your exact query look like?
3. Are you within a transaction when you run the query? Have you found any differences if you are within a transaction or not with regards to this issue?
4. Do you have any other special configuration worth calling out? Like any special app-context, persistence unit, etc. Also are you using Spring to manage the transactions?

Thanks,
Ryan

from java-sdk.

Ryan,

What office are you located in? The best bet is probably for me to show you
in a running program. Unfortunately I was unable to create a simple test
program that fails. This means I don't fully understand the unique
circumstances that cause the problem but the problem occurs none-the-less
:-(.

I have a program that reproduces it pretty easily but unfortunately it is
not a small isolated test program. If you are interested in seeing the
source it is at:

https://github.com/forcedotcom/isv-services

It is not a public repository so you'll need access granted. Unfortunately
I have not been given admin access so I can't do it. Someone in your group
that owns forcedotcom should be able to grant you access.

Look at the file "CompanySubscriptionsResource.java". There is a "TODO
comment in that file which will identity the problem area. I have also
attached the file this this email.

I

Basically I am just doing a single query and then examining the returned
results. I believe I am implicitly doing a single object fetch after the
query when i start examining the objects.

The problem was originally spotted when I was not using transactions. I am
now using transactions and the problem still occurs. The transactions did
not appear to change the symptoms.

You can see the query in the attached source file.

Since we work for the same company the best bet might be for you to come to
my desk and see the problem in action. I can run the program in the
debugger and with DEBUG logging enabled and reproduce the problem in about
30 seconds .We can then interactively talk and probably give you a lot more
insight a lot more quickly.

• Dave

On Mon, Nov 28, 2011 at 11:23 AM, Ryan Brainard <
[email protected]

wrote:

Hi David,

I have tried a few different scenarios to reproduce this issue, but
everything is working as expected; however, I'd like to get a little more
clarity as to exactly what you were doing when you encountered this issue:

1. Does Subscription look up to Application which looks up to Vendor? Just
   want to make sure I understand your data model correctly.
2. What is your exact query look like?
3. Are you within a transaction when you run the query? Have you found any
   differences if you are within a transaction or not with regards to this
   issue?
4. Do you have any other special configuration worth calling out? Like any
   special app-context, persistence unit, etc. Also are you using Spring to
   manage the transactions?

Thanks,
Ryan

---

Reply to this email directly or view it on GitHub:
#12 (comment)

from java-sdk.

Fixed in e631e6e in develop develop branch and included in 22.0.8-SNAPSHOT. Confirmed with David his issue is resolved.

from java-sdk.