No, this isn't yet another question about how to set up a debugger to work
with Orion and EJBs, I have a more insidious problem at hand...
One of my entity beans returns a bulk accessor (which implements
Serializable), but for some odd reason, calling the method to get
this always returns a null. I'm positive that in my EJB implementation
class, an object is being returned. I've snagged the generated wrapper
sources, and looked over the whole thing in a debugger, and it seems the
culprit is in the following code snippet:
if(thread.contextContainer != null)
response = response == null ? null
: (com.alltrue.ejb.VideoData)EJBUtils.cloneObject(response,
this.context.home);
Using a debugger shows that the code does step into the cloneObject
method, but unfortunately EJBUtils is jax'ed so I can't step into it.
So, my questions are:
1) Is there any way of specifying options to be passed to Orion's
compilation process (such as -g)
2) Is there any way of keeping the sources of the generated files?
3) Is anything required for returned objects other than that they
implement Serializable?
I'm almost positive I'm missing something incredibly obvious, as I'm sure
the bulk accessor paradigm is very common and almost standard practice
with entity beans, so I'd be surprised if it somehow wasn't a mistake on
my part....
Hani
