Dennis Muhlestein wrote: > I have a situation where an account can have one or none of an another > entity bean in a relationship. > > I've defined it below as a one-one relationship. This works fine if the > billingInfo exists, but if it doesn't and I call getBillingInfo from the > account, I still get an EntityBean Interface back. (No Exception > occurs) Then, when I try to access or set something on the billingInfo > interface, I get NoSuchEntityException from jboss.
That is a bug. Pleas post a report at SourceForge along with a simple test case. > Should I use one-many instead?? No. > Shouldn't I get null back or something > instead of an interface to the ejb when the billingInfo doesn't yet > exists? Null. > If this is the correct functionality, then how to I know if a > billing info record exists or not yet? Is it possible to remove the > billingInfo record in this case or is that against the law in a one-one > relationship? It is a bug -- xxxxxxxxxxxxxxxxxxxxxxxxx Dain Sundstrom Chief Architect, JBossCMP JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxxx _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
