yeah cool, as long as it takes the HttpServlet- or is there a way to get at
that from the request object?
From the servlet you can get the ServletContext, which can then do a
getRealPath() - invaluable if you are trying to see what actually exists in
your filesystem before determining which
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5865.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On 15 Jan 2002 [EMAIL PROTECTED] wrote:
Date: 15 Jan 2002 06:25:00 -
From: [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: cvs commit: jakarta-struts/contrib/validator/web/example/WEB-INF
validation.xml web.xml
dwinterfeldt
On Mon, 14 Jan 2002, John Yu wrote:
Date: Mon, 14 Jan 2002 20:13:47 +0800
From: John Yu [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: Comptability of JSR 127 and Struts [Was: SHORT TERM PLANS]
Thanks for
On Mon, 14 Jan 2002, Donnie Hale wrote:
Date: Mon, 14 Jan 2002 23:54:33 -0500
From: Donnie Hale [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: RE: The BIG Check-In for Multi-App Support
I've finally had a chance
craigmcc02/01/15 10:39:36
Modified:src/share/org/apache/struts/config ApplicationConfig.java
Log:
Change the name of the collection used to store ActionConfig objects, to
avoid potential confusion with the collection named actions in
RequestProcessor.
Submitted by: Donnie
About a year ago we were using the Digester in a non-struts related
project, and had some pretty bad problems with classloading in an
environment using 'containers' for various modules, since it used the
old-style
Class.forName(xxx)
mechanism to load classes, instead of the recommended
craigmcc02/01/15 10:51:26
Modified:src/share/org/apache/struts/action ActionServlet.java
Log:
Refactor the common doGet() and doPost() logic (again) into a common
process() method.
Submitted by: Donnie Hale [EMAIL PROTECTED]
Revision ChangesPath
1.85 +27
craigmcc02/01/15 11:08:26
Modified:doc project.xml
Log:
In the HEAD branch, point at the *current* JavaDocs instead of the 1.0 ones.
Revision ChangesPath
1.16 +1 -1 jakarta-struts/doc/project.xml
Index: project.xml
craigmcc02/01/15 11:14:26
Added: src/share/org/apache/struts/config package.html
Log:
Package-level documentation for the org.apache.struts.config package.
Revision ChangesPath
1.1 jakarta-struts/src/share/org/apache/struts/config/package.html
I filed a bug report for this same problem.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5774
-Original Message-
From: Colin Sampaleanu [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 1:47 PM
To: [EMAIL PROTECTED]
Subject: Bad classloading, why does Struts continue to
craigmcc02/01/15 12:22:20
Modified:conf/share struts-config_1_1.dtd
src/share/org/apache/struts/config ConfigRuleSet.java
FormBeanConfig.java
Added: src/share/org/apache/struts/config FormPropertyConfig.java
Log:
Tighten up the
The patches to deal with this are straightforward. My concern is that the
context class loader is ***not*** guaranteed to be accurately set in
servlet 2.2 environments (although it is now required to be in the webapp
class loader in servlet 2.3).
Does anyone know of a current platform that
I bet that might also cure some problem's we'vwe been having...
Cheers,
Nick
-Original Message-
From: Deadman, Hal [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 12:37 PM
To: 'Struts Developers List'
Subject: RE: Bad classloading, why does Struts continue to use
Thanks. The bug report mentions the Digester only, but the problem is
not only with the usage of the Digester though, it is with Struts
itself. We have a legitimate use for Struts at several levels, and the
current use of Class.forName() for classloading in a number of places
breaks things.
FWIWs, it will work for sure with WebLogic 6.x, and Resin, both of which
I have verified, and as you mentioned it is guaranteed for any 2.3
environments.
I think you have to ask, what is going to happen if the Context
classloader is not set in some sort of environment? According to the
docs,
On Tue, 15 Jan 2002, Colin Sampaleanu wrote:
Date: Tue, 15 Jan 2002 15:35:25 -0500
From: Colin Sampaleanu [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: Bad classloading,
why does Struts continue to use
I'm a newbee to Struts and I'm perplexed as to why the various WAR files
components are being deployed in places where the JSP invocations of the
taglibs cannot access. For reference, I'm running JRun 3.1 on Win2K. Is
there a tutorial that actually works???
Mark
- Original Message -
I am going to propose that we switch to a connection pool based on the
commons-dbcp (and commons-pool) packages as the preferred data source
implementation for Struts 1.1. The existing implementation already has
equivalent functionality to what org.apache.struts.util.GenericDataSource
covers,
Craig,
I thought the context classloader was defined to be the same as the loader
you'd get via class.forName if the context classloader had not otherwise
been explicitly set. From the javadocs for getContextClassLoader:
Returns the context ClassLoader for this Thread.
Craig,
Thanks for the detailed reply. See below.
[snip[
1. I don't know if this is carved in stone yet, but IMHO this
is much more
than a 1.1 release. Perhaps not a 2.0 release, but at least a
1.5 release.
The implications of a single point release to me are minor functional
craigmcc02/01/15 19:05:22
Modified:.build-webapp.xml build.properties.sample build.xml
Log:
Include commons-dbcp.jar and commons-pool.jar with Struts, in preparation
for migration to the DBCP version of a connection pool as the preferred
standard implementation.
One other thought. Perhaps a utility method should be added (where?) that
the various Struts classes would use when needing either a new Class
instance or a new instance for a given Class.
Donnie
-Original Message-
From: Donnie Hale [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January
I downloaded the latest nightly build and this error went away. However, I
now a few new issues:
1. If I call my JSP Page directly (which is contentType=text/xml), the
html:html xhtml=true locale=true is translated to html lang=en
xml:lang=en. But when I call it with the following transform
On Tue, 15 Jan 2002, Donnie Hale wrote:
Date: Tue, 15 Jan 2002 22:05:56 -0500
From: Donnie Hale [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: RE: Bad classloading,
why does Struts continue to use
- Original Message -
From: Mark Galbreath [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Tuesday, January 15, 2002 5:04 PM
Subject: Re: Bad classloading, why does Struts continue to use
Class.forName()?
I'm a newbee to Struts and I'm perplexed as to why the
26 matches
Mail list logo
