I don't like that - tomcat is supposed to depend
only on JDK1.1 and a minimal number of extensions
( jaxp is the only required extension ).
All non-jdk1.1, non-standard extensions can be used,
but shouldn't be required to build standalone tomcat.
I don't know if it's too late to change this - it
seems
we just need to replace
sc.setSocketFactory(new
org.apache.tomcat.net.SSLSocketFactory());
with
sc.setAttribute( "socketFactory",
"org.apache.tomcat.net.SSLSocketFactory");
and remove the import line.
I know it's not the the easiest solution, but I think
it's worth the added complexity - it is still a
requirement to support JDK1.1 and work with a minimal
set of library ( and JSSE is a very special one
anyway, export, etc).
Costin
--- Mike Anderson <[EMAIL PROTECTED]> wrote:
> I updated my source from CVS yesterday and all of
> the sudden I couldn't build. I got an error saying
> javax.net.ServeSocketFactory not found in import
> when trying to build
>
src\share\org\apache\tomcat\net\SSLSocketFactory.java.
> I looked at the build.xml and it looked like it
> shouldn't even be trying to build
> SSLSocketFactory.java since I didn't have the jsse
> classes in my classpath. However, looking in the
> EmbededTomcat.java that was checked in on 11/17, it
> now does an import of org.apache.tomcat.net.* and
> directly references
> org.apache.tomcat.net.SSLSocketFactory. Is there a
> way to fix this or are we now going to need to add
> the jsse jars to the build classpath? If I do need
> to add the jsse jars, we should probably update the
> README to mention this so that others don't pull
> their hair out like I did for a while today.
>
> Thanks,
>
> Mike Anderson
> Senior Software Engineer
> Platform Services Group
> [EMAIL PROTECTED]
> Novell, Inc., the leading provider of Net services
> software
> www.novell.com
>
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/