Yes, the iiop stuff is now generated by a default build.
I have changed a couple of files (jboss-services.xml and run.sh)
in order to run it. Please see the patchfile attached.
Should I commit these changes?
Cheers,
Francisco
PS: David Jencks is getting a very strange error from rmic.
Are you also getting this error?
On Mon, 15 Apr 2002, Jason Dillon wrote:
> I setup the build system to include jboss.net & iiop in the default
> builds. Please look at the configuration that is generated and make
> sure that iiop stuff will work with a default build.
>
> Note, this is on HEAD.
>
> --jason
>
>
> Francisco Reverbel wrote:
>
> >Will it include the iiop stuff? Jason and I were talking about
> >making it part of the default build.
> >
> >User feedback would be a good thing for me at this point.
> >
> >Best,
> >
> >Francisco
> >
> >On Sun, 14 Apr 2002, Scott M Stark wrote:
> >
> >>I'm creating the 3.0 branch for the RC1 release at midnight
> >>(GMT-0700). Do not commit any changes to main after
> >>22:00 -0700 until the branch is announced to be complete.
> >>
> >>xxxxxxxxxxxxxxxxxxxxxxxx
> >>Scott Stark
> >>Chief Technology Officer
> >>JBoss Group, LLC
> >>xxxxxxxxxxxxxxxxxxxxxxxx
> >>
> >>
> >>
> >>_______________________________________________
> >>Jboss-development mailing list
> >>[EMAIL PROTECTED]
> >>https://lists.sourceforge.net/lists/listinfo/jboss-development
> >>
> >
>
>
>
Index: server/src/etc/conf/default/jboss-service.xml
===================================================================
RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/jboss-service.xml,v
retrieving revision 1.44
diff -u -r1.44 jboss-service.xml
--- server/src/etc/conf/default/jboss-service.xml 14 Apr 2002 19:42:56 -0000
1.44
+++ server/src/etc/conf/default/jboss-service.xml 16 Apr 2002 16:17:34 -0000
@@ -110,7 +110,7 @@
<!-- ==================================================================== -->
<!-- RMI/IIOP -->
<!-- ==================================================================== -->
- <!-- Uncomment to use the iiop module with JacORB
+
<mbean code="org.jboss.iiop.CorbaORBService"
name="jboss:service=CorbaORB">
<attribute name="ORBClass">org.jacorb.orb.ORB</attribute>
@@ -120,7 +120,6 @@
<attribute
name="PortableInterceptorInitializerClass">org.jboss.ejb.plugins.iiop.server.CodebaseInterceptorInitializer</attribute>
<attribute name="Verbosity">1</attribute>
</mbean>
- -->
<!-- ==================================================================== -->
<!-- The deployers... -->
Index: system/src/bin/run.sh
===================================================================
RCS file: /cvsroot/jboss/jboss-system/src/bin/run.sh,v
retrieving revision 1.5
diff -u -r1.5 run.sh
--- system/src/bin/run.sh 5 Apr 2002 00:00:12 -0000 1.5
+++ system/src/bin/run.sh 16 Apr 2002 16:17:34 -0000
@@ -110,7 +110,17 @@
fi
fi
-# Setup JBoss sepecific properties
+# If the JVM is not HOTSPOT enabled, then assume it is an IBM JVM
+# (IBM JVMs need jacorb.jar in the classpath)
+if [ "x$HAS_HOTSPOT" = "x" ]; then
+ JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_HOME/lib/jacorb.jar"
+fi
+
+# Use JacORB as the default ORB
+JAVA_OPTS="$JAVA_OPTS -Dorg.omg.CORBA.ORBClass=org.jacorb.orb.ORB"
+JAVA_OPTS="$JAVA_OPTS -Dorg.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSingleton"
+
+# Setup JBoss specific properties
JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME"
# For Cygwin, switch paths to Windows format before running java
