You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/06/24 08:11:28 UTC

DO NOT REPLY [Bug 29780] New: - Why we need a jkMain static attibute?

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29780>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29780

Why we need a jkMain static attibute?

           Summary: Why we need a jkMain static attibute?
           Product: Tomcat 5
           Version: 5.0.25
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:Coyote
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: pr@objektpark.de


Hey,

I see following code at JkMain

 public JkMain()
    {
        JkMain.jkMain=this;
        modules.put("channelSocket", "org.apache.jk.common.ChannelSocket");

...

}


..
   public static JkMain getJkMain() {
        return jkMain;
    }
...


But nobody use this code and I think we not need this dependency!
Every Service. AJP connector can have its own jkMain env and nothing must be shared.

regards
peter

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org