Thanks for the info... however, after upgrading to JRun 3.1 we ran into a serious JNDI conflict error. Apparently upgrading to JRun 3.1 created a conflict with all of the JDBC configurations we had in our 3.0 version. We tried everything we knew to try and fix it but ultimately ended up going back to 3.0.
We now have a working Struts 1.0 app on our JRun 3.0 server so I'm not sure we will be "testing" any new configurations any time soon. We are still waiting for Macromedia to add the user account feature to the 4.0 version.... why they took it out we'll never know. We have version 4.0 but haven't installed it because of the reason..... Thanks again.... -----Original Message----- From: Huw Richards [mailto:[EMAIL PROTECTED] Sent: Monday, November 10, 2003 3:19 PM To: Struts Users Mailing List Subject: RE: Struts Config for JRun FYI.... I previously had struts 1.1 running on jrun 3.1. See this email in the archive (which refers to struts 1.0.2 but the change works for 1.1) http://marc.theaimsgroup.com/?l=struts-user&m=103652624602001&w=2 Let me know if you need more help. H. -----Original Message----- From: David Liles [mailto:[EMAIL PROTECTED] Sent: Sunday, November 09, 2003 11:51 PM To: Struts Users Mailing List Subject: Struts Config for JRun FYI.... ___________________________________________________________ *** WARNING *** This email has been received from the internet. Check any attachments for viruses before opening them. ___________________________________________________________ I'm not sure if this is old news or not, but hopefully it might be of help to others.... I've spent most of the weekend trying to configure a Struts 1.1 web app on a JRun 3.x server. When I would try and start the web app the event log would show an error indicating that it could not instantiate org.apache.struts.action.ActionServlet. I spent the better part of the weekend trying to figure out why this was happening. I develop locally with JBuilder 7 and when testing, the app worked fine; it only bombed when deployed to the JRun server. After countless hours searching, I found an old posting that said JRun 3.x could not support Struts 1.1.... it would only support version 1.0. This being the case, I downloaded the 1.0 version and commenced to converting all of the necessary class files. Once the conversion was complete, I deployed the "new" web app version to the JRun server and it worked. I do however have one "glitch" I'm trying to resolve.... For some reason I must now use the full package names when referring to various bean classes, even if I import them into the JSP.... For example, <%@ page import="biz.minimoon.beans.*" %> doesn't seem to do any good.... I still have to reference classes individually with the entire package name when I want to use them.... This is even true if I import java.util.* in order to use a Collection or ArrayList, I still have to use the entire package name in order for it to work.... If anyone has any suggestions for my remaining bug, I'd appreciate it. Thanks, Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___________________________________________________________ CONFIDENTIALITY NOTE This message may contain confidential and privileged information. If you think, for any reason, that this message may have been addressed to you in error, you must not disseminate, copy or take any action in reliance on it and we would ask you to notify us immediately by return email to "[EMAIL PROTECTED]". http://www.oprig.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
