Re: [C2] build problem with servlet 2.3

[Sam Ruby <ru...@us.ibm.com>]

Potential candidate catalog/repository item...

- Sam Ruby
---------------------- Forwarded by Sam Ruby/Raleigh/IBM on 02/26/2001
10:17 AM ---------------------------

Berin Loritsch <bl...@apache.org> on 02/26/2001 09:47:32 AM

Please respond to cocoon-dev@xml.apache.org

To:   cocoon-dev@xml.apache.org
cc:
Subject:  Re: [C2] build problem with servlet 2.3



"Morrison, John" wrote:
>
> Could we not use the code from struts?  That's apache code (so no license
> problems) and encourages (project) re-use?

I understand the idea.  But let me put it very simply--again.

The Struts API does not allow for invisible operation with Cocoon.
The MaybeUpload package extends the HttpServletRequest object, so
is seamlessly integrated with no ugly hacks.

The Struts API requires that we access the functionality in a
"sideways" manner.  What I mean by this is that instead of simply
extending the HttpServletRequest like the two other major utilities
do (O'Reilly and MaybeUpload), you must access separate classes.
This complicates matters more than it helps.  If you want to develop
the glue code to handle the Struts integration inside the
HttpRequest objects so that we don't have to have multiple interfaces
to learn, then by all means please do so.

All I want to do is use the HttpRequest object with (at most) two
extra methods (getFile and getFiles) to obtain the File handles that
were uploaded.

>
> > -----Original Message-----
> > From: Berin Loritsch [mailto:bloritsch@apache.org]
> > Sent: 26 February 2001 2:38 pm
> > To: cocoon-dev@xml.apache.org
> > Subject: Re: [C2] build problem with servlet 2.3
> >
> >
> > Paul Russell wrote:
> > >
> > > * Berin Loritsch (bloritsch@apache.org) wrote :
> > > > Speaking of which--would it be more beneficial to
> > everyone if we included
> > > > the sourcecode to MaybeUpload instead of the jar?  With
> > the license it is
> > > > possible as long as the source files retain the license
> > information in their
> > > > headers.
> > >
> > > Are we allowed to do that? I thought we could only have
> > non-APL stuff
> > > as libs. Anyone remember where the documentation for this
> > kind of thing
> > > is?
> >
> > Well, I don't know about Apache rules on this one, but the license
> > permits it.  We may have to do something like that for a wrapper
> > around the wrapper... Or simply extend it for the Servlet23
> > environment.
> >
> > I just don't want several copies of files floating around based on
> > different versions of servlet specs...
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
> =======================================================================
> Information in this email and any attachments are confidential, and may
> not be copied or used by anyone other than the addressee, nor disclosed
> to any third party without our permission.  There is no intention to
> create any legally binding contract or other commitment through the use
> of this email.
>
> Experian Limited (registration number 653331).
> Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org