On Sat, Aug 1, 2009 at 5:51 AM, Thomas E Enebo wrote:
> For clarification (for more general JI audience), I think in theory we
> should consider changing JRuby so:
>
> beanHome = PortableRemoteObject.narrow(home, BeanHome)
>
> I believe this is more or less unambiguous. I really don't think
> a
On Fri, Jul 31, 2009 at 5:31 PM, Mikael
Lammentausta wrote:
> I solved my problem. It was really simple in the end :)
Sorry. I should have given the full snippet. This was what I was
recommending you do :)
For clarification (for more general JI audience), I think in theory we
should consider ch
On Fri, Jul 31, 2009 at 3:31 AM, Mikael
Lammentausta wrote:
> I solved my problem. It was really simple in the end :)
Things with JRuby often are :)
> home = @@context.lookup('ServicesHome')
>
> beanHome = PortableRemoteObject.narrow(
> home,
> BeanHome.java_class
> )
>
I solved my problem. It was really simple in the end :)
home = @@context.lookup('ServicesHome')
beanHome = PortableRemoteObject.narrow(
home,
BeanHome.java_class
)
ejb = beanHome.create
Now I can call methods on the ejb object.
Sorry for the inconvenience.
-
The type cast is required, because the remote object from context is
EJBHome, and I need the Home object for a specific JavaBean, and I can only
access them through this node.
I'm debugging with
beanHome = PortableRemoteObject.narrow(
java.lang.Object.new(),
Java::custom.ServicesHome.java_cla
Try changing:
Java.ruby_to_java(Java::custom.ServicesHome.class)
to:
Java::custom.ServicesHome.java_class
...though it strikes me that we should really work if we do:
Java::custom.ServicesHome
Hmmm, may need to look into that,
-Tom
On Thu, Jul 30, 2009 at 2:36 AM, Mikael
Lammentausta wrote
I am using JRuby to act as EJB client.
The attached test case describes the problem I have:
http://pastie.org/563934
In essence, after opening the context, I have a problem getting the proper
type cast on the object I receive by RMI. For that, to my understanding, I
would need to call PortableRem