JSSE can be used as an application bundled extension and does not
need to be in the vm lib/ext directory. The JSSE security provider
has to be registered via construct like:
Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
if you don't edit the VM lib/security/java.security properties file. We
are not doing this currently in the JBoss security configuration service
setup so the bundled JSSE jars are not sufficient. I'm currently adding
this.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Peter Braswell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 24, 2002 7:43 PM
Subject: [JBoss-dev] JSSE and UDDI integration
> All,
> I'm working on getting UDDI integration into the
> jboss.net stuff. I'm currently using UDDI4J for the
> publishing APIs. Publishing web services requires
> HTTPS. UDDI4J requires JSSE. The stand alone
> examples I've been working with require the jsse.jar
> file to reside in jre/lib/ext. Simple inclusion in
> the CP won't suffice.
>
> My question: in the Jboss environment, is this
> limitation overcome? I notice jsse.jar in the /lib
> directory... I'm hoping through the miracle of jb
> classloading/security management and all, I can safely
> just go off and use those api w/o having jsse live in
> jre/lib/ext?? I also understand that in 1.4 this is
> not an issue...?
>
> thx,
> peter
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Games - play chess, backgammon, pool and more
> http://games.yahoo.com/
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
