Hi Magnus and All Orion-Interest Subscribers,
I read the document for remote access to applications. I am wondering if
such implementation would be useful in a development environment, hope u can
help!
I already setup the rmi and everything, it works if my ejb and web are
packaged into a ear file.
However, if my ejb and web are not packaged into an ear file. it does not
work. I'm wondering if I can setup something as follows, please advise. Is
it ture that creating the ear file is my only alternative? (I prefer to
maintain the directory structure, as we r using JBuilder for debugging)
My development environment is like that:
Basically with 3 orion servers (1.5.2) (assuming with 1 ejb and 1 web
developer for right now):
1. development box (used by both EJB and WEB developer for stable stuff, and
all of them are packaged into an ear file)
2. EJB developer's local box (focus on development of a particular ejb
module, use directory structure instead of ear file)
3. Web developer's local box (focus on development of the web module, use
directory structure instead of ear file)
===============
Development Box
===============
myEAR.ear -> myEJB1.jar
-> myEJB2.jar
-> myEJB3.jar
-> myWEB.war
server.xml (for Development Box)
<application name="testApp" path="../MyEar.ear" auto-start="true" />
application.xml (for Development Box)
<module> <ejb>myEJB1.jar</ejb> </module>
<module> <ejb>mEJB2.jar </ejb> </module>
<!-- use directory structure instead for local development -->
<module> <ejb>mEJB3 </ejb> </module>
=============
EJB Developer
=============
(with local version (under development) of a particular ejb module without
creating the jar file)
.../myEar/ -> myEJB1.jar
-> myEJB2/...
-> myEJB3.jar
server.xml (for EJB Developer)
<application name="testApp" path="../MyEar/" auto-start="true" />
application.xml (for EJB Developer)
<module> <ejb>myEJB1.jar</ejb> </module>
<!-- use directory structure instead of local development -->
<module> <ejb>myEJB2</ejb> </module>
<module> <ejb>myEJB3.jar</ejb> </module>
orion-application.xml (for EJB Developer)
<ejb-module remote="true" path="myEJB1.jar" />
<ejb-module remote="true" path="myEJB3.jar" />
=============
Web Developer
=============
(with local version of web module without creating the war file)
.../myEar/ -> myEJB1.jar
-> myEJB2.jar
-> myEJB3.jar
-> myWeb/...
server.xml (for Web Developer)
<application name="testApp" path="../MyEar/" auto-start="true" />
application.xml (for WEB Developer)
<module> <ejb>myEJB1.jar</ejb> </module>
<module> <ejb>myEJB2.jar</ejb> </module>
<module> <ejb>myEJB3.jar</ejb> </module>
orion-application.xml (for WEB Developer)
<ejb-module remote="true" path="myEJB1.jar" />
<ejb-module remote="true" path="myEJB2.jar" />
<ejb-module remote="true" path="myEJB3.jar" />
===============================
Exception during ejb deployment
===============================
java.lang.NullPointerException
at com.evermind._px._hjd(Unknown Source)
at com.evermind._px._hjd(Unknown Source)
at com.evermind._px._gyd(Unknown Source)
at com.evermind._px._bb(Unknown Source)
at com.evermind._au._bb(Unknown Source)
at com.evermind._dq._qzb(Unknown Source)
at com.evermind._ck._qzb(Unknown Source)
at com.evermind._ck._at(Unknown Source)
at com.evermind.server.ApplicationServer._as(Unknown Source)
at com.evermind.server.ApplicationServer._wl(Unknown Source)
at com.evermind.server.ApplicationServer._at(Unknown Source)
at com.evermind._in.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at com.evermind._if.run(Unknown Source)
P.S.
I can deploy the about setting without RMI setting (i.e. within each box
without setup the ejb as remote). However, I want to have a consistent
stable environment (i.e. development box) that all EJB and WEB developers
can work on.
Thanks in advance!
Chris
-----Original Message-----
From: Magnus Rydin [mailto:[EMAIL PROTECTED]]
Sent: November 16, 2001 12:44 PM
To: Orion-Interest
Subject: Announcement
Announcement
------------
2 new documents available:
www.orionserver.com/docs/resource-provider/resource-provider.xml
Describes how to produce your custom Resource Provider class or use a sample
one to smoothly integrate third party resources with Orion and make these
available to your applications.
www.orionserver.com/docs/remote-access/remote-access.xml
Describes different scenarios for remote access to applications.
This document will expand in the coming week.
As said earlier, any comments/suggestions/requests for documentation can be
sent to [EMAIL PROTECTED]
upcoming docs are:
1) Additional remote scenarios
2) Application Client documentation
3) Configuring datasources
4) SSL clustering details
5) EJB clustering details
6) HTTP clustering details
7) MDB documentation
8) Orion specific deployment settings explained
WR
The Orion Team
