The IIOP module should be working. There are no (major) problems known.
Of course, more testing is needed... Right now there is just one iiop
test in the testsuite. More are coming soon.
So far JBoss/IIOP provides basic RMI/IIOP access to EJBs. Transactions
and security aren't there yet.
To build and run JBoss/IIOP:
- Check out jboss-all from the CVS repository
- Build everything as usual, then build the IIOP module and the
testsuite:
./build/build.sh
./build/build.sh -Dmodules=iiop
./build/build.sh -Dmodules=testsuite
(The second build above is necessary because IIOP is not part of
the default build).
- Edit $JBOSS_HOME/server/default/conf/jboss-service.xml and uncomment
the mbean entry for RMI/IIOP.
- Put in your environment a JAVA_OPTS entry with
"-Xbootclasspath/p:$JBOSS_HOME/lib/jacorb.jar" in it. On Linux (bash),
you would say something like
export JAVA_OPTS=-Xbootclasspath/p:$JBOSS_HOME/lib/jacorb.jar
If you are using a HotSpot JVM, you should also put "-server" at
the very start of your JAVA_OPTS (the JBoss startup script does
not add "-server" to a pre-existing JAVA_OPTS entry):
export JAVA_OPTS="-server -Xbootclasspath/p:$JBOSS_HOME/lib/jacorb.jar"
- Use the run.sh script to start the JBoss server as usual.
- To specify that an EJB should be deployed in an IIOP container,
include in its jboss.xml file an configuration-name entry for one
of the IIOP container configurations:
IIOP CMP 2.x EntityBean
IIOP CMP EntityBean
IIOP Stateless SessionBean
IIOP Stateful SessionBean
IIOP BMP EntityBean
For instance:
<jboss>
<enterprise-beans>
<session>
<ejb-name>HelloWorld</ejb-name>
<jndi-name>helloworld/Hello</jndi-name>
<configuration-name>IIOP Stateless SessionBean</configuration-name>
</session>
</enterprise-beans>
</jboss>
- To run the IIOP testcases in test directory testdir, go to the
testsuite directory and say
./build.sh -Dtest=testdir iiop-test
or
./build.sh -Dtest=testdir iiop-test-nojars
Right now there is just one iiop testdir: helloiiop.
It is also possible to deploy EJBs in an IIOP container _without_ having
to specify an IIOP configuration in the bean's jboss.xml. To do this,
you must have an "IIOP server configuration". The very same jar file
can then deployed in JRMP and in IIOP containers. This is the way I have
been using JBoss/IIOP most of the time. (It is also the reason I have
just one IIOP testcase targeted at the default server configuration.)
More on this in another message...
Enjoy,
Francisco
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
