jakarta-tomcat-connectors/jk will no longer build

[Patrick Luby]

Remy,

Since the org.apache.catalina.connector.HttpResponseBase was removed 
from jakarta-tomcat-catalina, a clean Tomcat 5 build now breaks when 
compiling jakarta-tomcat-connectors/jk. Does HttpResponseBase need to be 
added back?:

Thanks,

Patrick

 [javac] Compiling 44 source files to 
/export/pluby/tomcat/jakarta-tomcat-connectors/jk/build/classes
 [javac] 
/export/pluby/tomcat/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/Ajp13Request.java:75:
cannot resolve symbol
 [javac] symbol  : class HttpRequestBase
 [javac] location: package connector
 [javac] import org.apache.catalina.connector.HttpRequestBase;
 [javac]  ^
 [javac] 
/export/pluby/tomcat/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/Ajp13Request.java:86:
 
cannot resolve symbol


-- 

Patrick Luby Email: [EMAIL PROTECTED]
Sun Microsystems Phone: 408-276-7471
901 San Antonio Road, USCA14-303
Palo Alto, CA 94303-4900



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: jakarta-tomcat-connectors/jk will no longer build

[Costin Manolache]

Patrick Luby wrote:

> Remy,
> 
> Since the org.apache.catalina.connector.HttpResponseBase was removed
> from jakarta-tomcat-catalina, a clean Tomcat 5 build now breaks when
> compiling jakarta-tomcat-connectors/jk. Does HttpResponseBase need to be
> added back?:

No, the tomcat4 package shouldn't compile with tomcat5.

I think we need a way to distinguish tomcat4 from tomcat5 in the
conditions. Or a flag that is set by the tomcat5 build ( probably 
better ).

Costin

> 
> Thanks,
> 
> Patrick
> 
>  [javac] Compiling 44 source files to
> /export/pluby/tomcat/jakarta-tomcat-connectors/jk/build/classes
>  [javac]
> 
/export/pluby/tomcat/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/Ajp13Request.java:75:
> cannot resolve symbol
>  [javac] symbol  : class HttpRequestBase
>  [javac] location: package connector
>  [javac] import org.apache.catalina.connector.HttpRequestBase;
>  [javac]  ^
>  [javac]
> 
/export/pluby/tomcat/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/Ajp13Request.java:86:
> cannot resolve symbol
> 
> 

-- 
Costin



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: jakarta-tomcat-connectors/jk will no longer build

[Patrick Luby]

Costin,

Costin Manolache wrote:


No, the tomcat4 package shouldn't compile with tomcat5.

I think we need a way to distinguish tomcat4 from tomcat5 in the
conditions. Or a flag that is set by the tomcat5 build ( probably 
better ).


I added a "org.apache.ajp.tomcat5" package in 
jakarta-tomcat-connectors/jk. This package contains no classes as the 
"org.apache.ajp.tomcat4" classes will need to be ported so that they do 
not use the HttpRequestBase class.

Also, I made jakarta-tomcat-connectors/jk/build.xml handle concurrent 
building of the "tomcat4" and "tomcat5" packages when both Tomcat 4.x 
and Tomcat 5 are present. This was what was causing my build to break: 
build.xml was automatically detecting my Tomcat 4 build even when I had 
"catalina.home" set to my Tomcat 5 build.

So, everything now builds fine except that the Ajp13 connector will not 
work with Tomcat 5 since there are no "tomcat5" classes at this time.

Patrick

--

Patrick Luby Email: [EMAIL PROTECTED]
Sun Microsystems Phone: 408-276-7471
901 San Antonio Road, USCA14-303
Palo Alto, CA 94303-4900



--
To unsubscribe, e-mail:   
For additional commands, e-mail: