I verified that if I add a dependency to j2ee-corba-yoko, the ORB gets
started (port 6882 gets opened) when starting our WAR. However, my servlet
still cannot see java:comp/ORB. Do I need any other dependencies?
Thanks,
Andres
djencks wrote:
>
>
> On Mar 21, 2007, at 10:47 PM, Andres wrote:
>
>>
>> In our situation, we have a startup servlet that is looking for an ORB
>> because we need to make a callback to another CORBA component. It
>> sounds
>> like we should have access to java:comp/ORB since the code is
>> running in a
>> servlet, but I tried it (after turning the ORB on) in Geronimo 1.2
>> and it
>> throws an exception (javax.naming.NameNotFoundException: ORB). Our
>> workaround is to call ORB.init if java:comp/ORB is not found. I was
>> originally having problems shutting the ORB down using destroy() using
>> Geronimo 1.1/Sun ORB, but since I moved to Geronimo 1.2, this
>> appears to no
>> longer be a problem with the Yoko ORB.
>
> I think if you add a dependency on the yoko module (j2ee-corba-yoko)
> in the environment of your servlet plan you will be able to look up
> the orb in jndi. When deciding whether to turn on the orb for you we
> look for corba style ejb references or an explicit dependency on the
> orb module: if neither is present we try to simplify the server by
> not starting the orb.
>
> Hope this helps
> david jencks
>
>>
>> Andres
>>
>>
>> djencks wrote:
>>>
>>>
>>> On Mar 17, 2007, at 5:34 PM, Andres wrote:
>>>
>>>>
>>>> We are porting an application from Websphere 6.1 to Geronimo
>>>> 1.1.1. We have
>>>> a CORBA component (not EJB) that used to obtain the ORB by
>>>> looking up
>>>> java:comp/ORB. Is there a way to do this in the present release
>>>> using JNDI
>>>> or will this be available in 1.2./2.0 when global JNDI support is
>>>> completed?
>>>
>>>
>>> if this is a corba service that runs in a thread started by the orb,
>>> and doesn't go through any j2ee components, I'm not sure you will be
>>> able to bind the orb under java:comp even in 1.2/2.0. In 1.2 you'll
>>> be able to write some extra code to bind an orb anywhere you want in
>>> global jndi, but I'm not sure whether you can bind into the
>>> "java:comp" context since that is pretty heavily specified for use by
>>> j2ee components. It might work, I don't know. In 2.0 this will be
>>> at least as possible and the orb may be pre-bound (although AFAIK
>>> that isn't implemented yet)
>>>
>>> If the thread this runs on went through a j2ee component before
>>> getting to your code, there should be an orb bound to java:comp/ORB
>>> already so long as the orb module is actually running. We've
>>> generally shipped with the orb turned off and turn it on when we
>>> detect an app using corba transport for ejbs. So one thing you want
>>> to do is look in var/config/config.xml or the admin console and see
>>> if its on. In 1.2/2.0 I think the module is called
>>> org.apache.geronimo.configs.corba-yoko/${version}/car, and in 1.1.1
>>> probably geronimo/openejb-corba-sun/1.1.1/car.
>>>
>>> Hope this helps, feel free to ask more.
>>>
>>> david jencks
>>>
>>>>
>>>> Thanks.
>>>> --
>>>> View this message in context: http://www.nabble.com/java%3Acomp-ORB-
>>>> tf3420569s134.html#a9533637
>>>> Sent from the Apache Geronimo - Users mailing list archive at
>>>> Nabble.com.
>>>>
>>>
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/java%3Acomp-ORB-
>> tf3420569s134.html#a9607529
>> Sent from the Apache Geronimo - Users mailing list archive at
>> Nabble.com.
>>
>
>
>
--
View this message in context:
http://www.nabble.com/java%3Acomp-ORB-tf3420569s134.html#a9641265
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
