RE: rmic with -poa option
David R Robison <[email protected]>
| Newsgroups | gmane.comp.java.mx4j.devel |
|---|---|
| Message-ID | <[email protected]> |
I finally got the test to run. Using the rmic -poa argument, all test passed with the following exceptions: 1) RemoteNotificationClientHandlerTest testNotificationDelivery Failure expected:<2> but was:<1> junit.framework.AssertionFailedError: expected:<2> but was:<1> at test.mx4j.remote.RemoteNotificationClientHandlerTest.testNotificationDelivery(RemoteNotificationClientHandlerTest.java:231) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2)IIOPAdaptorTest 8 of 9 tests failed with javax.naming.NameAlreadyBoundException 3) JRMPAdaptorTest 2 tests failed with error during JRMP connection establishment; nested exception is: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found 4) test.mx4j.tools.remote.soap 48 of 56 tests failed for various reasons. Most likely I did not have the right soap jars in the classpath. I think that the change in the build.xml to use -poa should be OK and not cause problems with anything that is currently working. David Robison Quoting "Bordet, Simone" <[email protected]>: > Hi David, > > have you tried to run with -poa under Sun's ORB delivered with the JDK > ? > > If that also works OK, I have no problem in modifying the build. > > Let me know. > > Simon > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > David R Robison > > Sent: Monday, June 21, 2004 13:39 > > To: [email protected] > > Subject: [Mx4j-devel] rmic with -poa option > > > > When trying to use mx4j with jacORB I have a problem that the > > stubs generated > > with rmic generate the iiop interface but not the poa > > interface. JacORB no > > longer support the BOA (used by the -iiop) and requires the > > POA (generated by > > the -poa option). Changing the rmic task in build.xml to the > > following makes > > JacORB compatable: > > > > <rmic base="${core.classes.dir}" > > classname="javax.management.remote.rmi.RMIServerImpl" > > classpathref="classpath" > > debug="yes" iiop="yes" > > > <compilerarg value="-poa" /> > > </rmic> > > <rmic base="${core.classes.dir}" > > classname="javax.management.remote.rmi.RMIConnectionImpl" > > classpathref="classpath" debug="yes" iiop="yes" > > > <compilerarg value="-poa" /> > > </rmic> > > > > Would there be a problem making this change in future version of > mx4j? > > > > Thanks, > > David Robison > > > > > > -- > > David R Robison Open Roads Consulting, Inc. 708 S. Battlefield > Blvd., > > Chesapeake, VA 23322 phone: (757) 546-3401 e-mail: > > [email protected] web: > http://openroadsconsulting.com > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > > Learn from the experts at JavaOne(SM), Sun's Worldwide Java > Developer > > Conference, June 28 - July 1 at the Moscone Center in San > > Francisco, CA > > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority > > Code NWMGYKND > > _______________________________________________ > > Mx4j-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/mx4j-devel > > > > > ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com