jerryjackson.net

Through a combination of hints found online along with some guidance from the instructor at the “Seam Essentials” training course I recently attended in Austin, TX - I figured out how to solve a problem I was having where instance data on the “far side” of @OneToOne and @OneToMany data associations was not staying synchronized with values on the “near side”.

Now that I understand the solution, it becomes clear to me that all the information I needed was out there - just not all in one place with good example code.

For the sake of formatting, I’ve placed the commented code here: http://pastie.org/private/wk2v3rbw892e5vbbenum7g (and I’m NOT claiming this is good example code)

Now I can move on to the never-ending list of other challenges.

UPDATE: After I made some substantial protests to the “office of the president”, a replacement phone was sent to me overnight. So - now they suck a little bit less.

I have a 5 month old Blackberry 8310 with what I now know to be the NOTORIOUS problem with the USB charging port. I phone AT&T customer support and the droid asks me 2 dozen stupid questions. LAST question is: “does the charging plug wiggle?” - I answer: “yes, it wiggles a very tiny bit” - then the droid tells me my warranty is voided due to physical damage.Â

Actually, it wasn’t 2 dozen stupid questions - the first question was “what color is the water exposure indicator” - THEN 22 stupid questions to distract the caller - THEN - WHAMO - “does your charging plug wiggle?”.

WTF ?????

I have 2 brand new 8310 units here with exactly the same amount of “slop” in the plug - so where the hell do they come up with “physical damage - warranty voided” ???

I guess having 5 phones on the AT&T family plan means nothing more than I get to pay them $3500/year for this bullshit. Plus the new 3g iPhone I purchased last week along with a 2 year contract upgrade.

I’m feeling really good about the fun I’m gonna have with this

att wireless at&t