Luciano Montebove
Finsiel
[EMAIL PROTECTED]
-----Messaggio originale-----
Da: Montebove Luciano
Inviato: mercoled� 26 luglio 2000 16.11
A: '[EMAIL PROTECTED]'; '=SMTP:[EMAIL PROTECTED]'
Oggetto: R: howto on setting up Orion web(servlet) server to use EJBs
froma remote Orion EJB server?
Priorit�: Alta
Hi David,
Suppose SERVER A is your Orion Server where you want to put the web
(servlets, JSPs) part of your application and SERVER B the server where you
want to put your EJBs:
1)Modify the rmi.xml in SERVER A as explained in docs/rmi.xml.html:
<server host="SERVER B" username="admin" password="123" port="SERVER
B rmi port"/>-->
1B)(optional) if SERVER B is on the same machine modify rmi.xml to assign a
different rmi port:
<rmi-server port="SERVER B rmi port">
2)On SERVER B deploy the ejb part of the application
3)Start SERVER B
4)On SERVER A deploy the full application (web and ejb) then modify
orion-application.xml
<ejb-module remote="true" path="youra-app-ejb"/>
5)Start SERVER A
6)Connect your browser to SERVER A
Hope this help
Luciano Montebove
Finsiel
[EMAIL PROTECTED]
-----Messaggio originale-----
Da: David Elliot [mailto:[EMAIL PROTECTED]]
Inviato: mercoled� 26 luglio 2000 12.43
A: Orion-Interest
Oggetto: RE: FollowUp: application-client.xml, initial context
Hi Jens,
I have been working happily with Orion for some time now, but
have yet to successfully configure it such that you can have
an Orion server running an EJB container, and a seperate
jsp/servlet Orion server accessing EJBs from the 1st server.
I assume that it is just a matter of making a remote JNDI call
from the Web server to the EJB server using the
ApplicationClientInitialContextFactory. However it seems
that:
a) No matter what I set the PROVIDER_URL to on the Web
server, the lookup is always directed at the EJB container
on localhost (rather than the remote EJB server specified), and;
b) When I trying to narrow the "remote" home interface
returned by JNDI to the home interace requested, I get a
ClassCastException as the jvm attempts to cast something like
MyBeanHome_EntityHomeWrapper12 to MyBeanHome. Why is
the JNDI lookup returning this obscure wrapper class?
It seems that the EntityHomeWrapper class is some utility wrapper
that Orion is creating for each EJB...although this is a bit
of a hassle when you start getting your EJBs typed this
way on JNDI lookups so that you can't cast them to your own
bean types ??
Working with Orion for so long I'm used to getting by
without any instructions... On the brightside you don't
see people saying 'RTFM' endlessly on this email list
(the retort of course would be 'What F---- Manual?'),
although on the downside I'm now truly stuck. So has anyone
got/seen instructions/howto on setting up an Orion web(servlet)
server to use EJBs from a remote Orion EJB server ?
Many thanks,
Dave Elliot
[I'm running:
Orion 1.1.35 sun 1.3jvm linux and
Orion 1.1.35 sun 1.3jvm win32]
-----Original Message-----
From: Jens Stutte [mailto:[EMAIL PROTECTED]]
Sent: 25 July 2000 09:49
To: Orion-Interest
Subject: AW: FollowUp: application-client.xml, initial context
Hi again,
just to let you know, how it works to use the
com.evermind.server.ApplicationClientInitialContextFactory:
For an application you should write one application-client.xml, that
contains ejb-refs to all beans used by this application. This file has
to
reside in a META-INF folder located in the root of the application's
jar -
respective in the root of (one of) your classpath(s).
It is intended to provide different application-client.xml files for
each
client, listing only the needed beans - a bit difficult while
developing,
since you should have an own class tree for each client application, so
i
fear at the end the application-client.xml will simply contain all
beans in
the server...
I know, that this likely will not be subject to change (depends on the
spec), but a possibility to assign JNDI names in the server on a
per-module-base would match my needs much better... well, we got to
take it
like it is.
BTW, is there any intended use for the
com.evermind.server.rmi.RMIInitialContextFactory? Is it only for
internal
use? Where do i assign names for objects in the server, that will show
up in
this context?
Regards,
Jens Stutte
PS: Thanx to Martin Mavrov, he led me on the right way...
> -----Urspr�ngliche Nachricht-----
> Von: Jens Stutte [mailto:[EMAIL PROTECTED]]
> Gesendet am: Dienstag, 25. Juli 2000 09:45
> An: Orion-Interest
> Betreff: FollowUp: application-client.xml, initial context
>
> Hi again,
>
> just to keep it clear: i am trying to access my beans from a
> standalone
> client on a different machine.
>
> Regards
>
> Jens Stutte
>
> > -----Urspr�ngliche Nachricht-----
> > Von: Jens Stutte [mailto:[EMAIL PROTECTED]]
> > Gesendet am: Montag, 24. Juli 2000 19:15
> > An: Orion-Interest
> > Betreff: application-client.xml, initial context
> >
> > Hi,
> >
> > i think, there is some confusion out there what's the right
> > way to obtain an
> > initial context and how to specify the bindings for ejbs (and
> > me too need a
> > little help).
> >
> > There are (at least) two factorys provided by orion, the
> > com.evermind.server.ApplicationClientInitialContextFactory and the
> > com.evermind.server.rmi.RMIInitialContextFactory.
> > Up to version 1.1.21 orion automatically put a jndi binding
> > with the beans
> > name specified in the ejb-jar.xml in the context which one
> got via the
> > RMIInitialContextFactory - a very handy thing, only that it
> > seems not to be
> > covered by any spec... and the newest version does not offer
> > these bindings
> > any more, so that clients relying on RMIInitialContextFactory
> > will fail in
> > the future it seems (i discovered this, because i used this
> > feature, too).
> >
> > Now i'm trying out to use the
> > ApplicationClientInitialContextFactory, and
> > found that documentation about the application-client.xml is
> > rare - not
> > regarding the contents but regarding the place, where to put
> > it. I have for
> > example an application with two modules, which reside
> > _unpacked_ in the
> > application directory, like
> >
> > appname
> > - META-INF
> > - application.xml
> > - module1
> > - de.... (classes, this is actual a link to my classes dir)
> > - META-INF
> > - ejb-jar.xml
> > - module2
> > - de.... (classes, this is actual a link to my classes dir)
> > - META-INF
> > - ejb-jar.xml
> >
> > each of these modules containing some beans, which are
> > deployed correctly,
> > it seems.
> >
> > I tried to put two application-client.xml files in the
> > META-INFs of the two
> > modules (on the server side), but the
> > ApplicationClientInitialContextFactory
> > still complains, that it can't find the
> > META-INF/application-client.xml. So i suspected, i'll have to put
it
> > somewhere on the client side - but where? Or do i have to
> > specify some magic
> > words in the application.xml?
> > I do not want to pack my classes into a client jar, if
> > possible, but leave
> > them unpacked in my CVS tree (within Netbeans/forte) while
> > developing.
> >
> > Could someone please shed some light on the
> > application-client.xml and how
> > it's intended to be used?
> >
> > Thanx,
> >
> > Jens Stutte
> >
> > ____________________________________________
> > [EMAIL PROTECTED], http://www.netmedia.de
> >
> > NetMedia GmbH
> > Neugrabenweg 5-7
> > 66123 Saarbruecken
> > Germany
> >
> > fon: +49 (0) 681 - 3 79 88 - 0
> > fax: +49 (0) 681 - 3 79 88 - 99
> >
__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/
