I've just created JDK-8021257 to track this. Yes - the ORB.init issue
can be corrected easily but more issues fall out from that. One example
: [1]. All calling sites into creation of com.sun.corba.se.impl classes
need to be examined.
regards,
Sean.
[1]
java.lang.NoClassDefFoundError: Could not initialize class
com.sun.corba.se.impl.ior.iiop.MaxStreamFormatVersionComponentImpl
at
com.sun.corba.se.spi.ior.iiop.IIOPFactories.makeMaxStreamFormatVersionComponent(IIOPFactories.java:174)
at
com.sun.corba.se.impl.transport.SocketOrChannelAcceptorImpl.addToIORTemplate(SocketOrChannelAcceptorImpl.java:361)
at
com.sun.corba.se.impl.transport.CorbaTransportManagerImpl.addToIORTemplate(CorbaTransportManagerImpl.java:238)
On 24/07/13 02:01, Alan Bateman wrote:
On 15/07/2013 01:14, Seán Coffey wrote:
Mandy,
Looks fine to me. I agree that we should back it out for 7u40. I
would think we want to leave the change in jdk8 and continue the
investigation and resolving the JCK failures for jdk8. Is that what
you are thinking? If so, we don't need to back it out from jdk8.
I was hoping to back out the fix for both jdk7u40 and jdk8. The setup
to reproduce is quite simple (modify package list in java.security)
and I think it's not necessary to have JCK failures in jdk8 for the
short to medium term as a result.
Have you created a new bug to track doing a more complete fix? It
looks like ORB.init should be straight-forward to fix to work even if
the package for the default implementation is on the restricted list.
-Alan
