It's alpha. http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.17-alpha/
John > -----Original Message----- > From: Denise Mangano [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 13, 2002 9:35 AM > To: 'Tomcat Users List' > Subject: RE: [OT] Apache-Tomcat mod_jk > > > Do you know where I could get Tomcat 4.1.17 release? > > Denise Mangano > Help Desk Analyst > Complus Data Innovations, Inc. > > > -----Original Message----- > From: Brandon Cruz [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 12, 2002 5:56 PM > To: Tomcat Users List > Subject: RE: [OT] Apache-Tomcat mod_jk > > > I would recommend using a different version of Tomcat than > 4.1.12. 4.1.12 > seems to have a few bugs that have been fixed by the 4.1.17 > release. If you > are using a connector (coyote), versions prior to 4.1.17 had > a bug with the > coyote connector. > > Hope you can save you some of the time I just spent figuring > these things > out over the past week or so. > > > > -----Original Message----- > From: Mike W-M [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 12, 2002 4:22 PM > To: Tomcat Users List > Subject: Re: [OT] Apache-Tomcat mod_jk > > > Denise, > > In application scenarios like this (and particularly because > you seem to > have multiple systems on the go) the thing that you need to > consider is > <i>transactions</i>. You need to consider what happens if > there's a failure > at any stage in the process, the aim being to ensure that > there's no way you > can: > i) charge the customer when it looks like you haven't > ii) charge them but fail to keep a record of it > iii) not charge them but make it look like you have... > iv) etc. > Across multiple systems this can be difficult! (Particularly > if there are > flat-files involved - it's a lot easier to do if you're only using > (transactional) databases.) > Of course it's not actually necessary to work-around all the potential > problems if the business are prepared to take the risk.... > > Apologies if you knew all that already! > > Mike. > > > > > ----- Original Message ----- > From: "Denise Mangano" <[EMAIL PROTECTED]> > To: "'Tomcat Users List'" <[EMAIL PROTECTED]> > Sent: Thursday, December 12, 2002 9:41 PM > Subject: RE: Apache-Tomcat mod_jk > > > Well I took the novice route and started all over again. I got Tomcat > 4.1.12 itself back up and running, but without mod_jk > installed. I haven't > had a chance to get back to trying again today, but I will > tomorrow. If I > run into the same problems, I will post my entire server.xml file, and > hopefully all you nice people will find something that my > untrained eyes > cant. > > Maybe a little background on my project will help determine > exactly what it > is that I need. I have a site running on Apache 1.3.27 > (mostly HTML, some > XML) on RedHat 7.3. This site, through a connector, is > pulling information > from a UNIX system. That part works fine. I get to the last > screen, where > the connection to UNIX is broken, but not before I am passed > a transaction > number. I then direct the user to an HTML form, where I > collect all their > credit card information. This is the point I am at now. > What I need to do > from here is collect the info and transmit it to the payment processor > through an API call, which I will either use servlet or JSP. > Then I will > display an updated page that varies depending on what the > response is from > the payment processor. All this over a secure connection of > course (which > from what I understand will be another battle). I then have > to send the > info I receive back to the UNIX system to be updated. (If > anyone has any > experience in a similar situation or any input regarding this > project it is > definitely welcome). > > Hope the background paints a clearer picture... Will post > tomorrow when I > try to set up mod_jk again. > > Thanks! > > > Denise Mangano > Help Desk Analyst > Complus Data Innovations, Inc. > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
