Aaron,
Well "Doh"! Yup, I didn't put the home and remote interface classes in the
jar. It makes sense in hindsight. The ejbCreate doesn't even get invoked.
The call works now that I have these in the jar with Bean A (Bean B is
indeed in a different jar).
Thanks.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
> Sent: Saturday, 30 September 2000 5:27
> To: jBoss
> Subject: Re: [jBoss-User] Another problem with Bean 2 Bean calls
>
>
> An InvocationTargetException usually means that some method called
> via reflection threw an exception. In this case, the likely suspect is
> the create method of the 2nd bean called by the first one - though it is
> odd that it wouldn't fail when called by a client. However, you seem to
> be seeing the "client side" (since the client is an EJB all exceptions
> appear in the jBoss console) of this exception - the exception generated
> for the EJB that is the client. You may be able to see the "server
> side" of the exception as well elsewhere in your console output, and this
> may be more informative. If all else fails, you can put a try/catch
> around the entire contents of ejbCreate.
> Also, are your 2 beans packaged into 1 JAR? If not, does the
> calling EJB JAR have the home & remote interfaces and primary key for the
> called EJB?
>
> Aaron
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
