headers
Cavallaro, Maria (Civ, ARL/SLAD | 2 Apr 18:15
Picon

Which tomcat to download (UNCLASSIFIED)

Classification:  UNCLASSIFIED 
Caveats: NONE

Hello,
  Can anyone help me to understand which distribution of Tomcat to
download in order to get Slide that is supposed to be bundled in?  When
I view the README for version 5.5.23 here's what is says (I'm using
Linux):
  Packaging Details (or "What Should I Download?") 
*	apache-tomcat-[version].zip or .tar.gz: base distro, all
non-embedded users download this. 
*	apache-tomcat-[version].exe: Windows installer with base distro
contents + Windows installation. 
*	apache-tomcat-[version]-admin.zip or .tar.gz: the Tomcat
Administration webapp only. 
*	apache-tomcat-[version]-compat.zip or .tar.gz: required in
addition to the base distro for using tomcat with a Java 1.4
environment. 
*	apache-tomcat-[version]-deployer.zip or .tar.gz: the standalone
Tomcat Web Application Deployer. 
*	apache-tomcat-[version]-embed.zip or .tar.gz: for using Tomcat
only as an embedded servlet container. 

I already have version 5.5.20 installed and Slide did not come "bundled
in".

Thanks!

Classification:  UNCLASSIFIED
Caveats: NONE
(Continue reading)

Permalink | Reply | 0 comments |
headers
Zeus Courtois | 2 Apr 19:01
Picon
Favicon

Re: Which tomcat to download (UNCLASSIFIED)

Hi Maria,

Now that you have downloaded and installed Tomcat 5.5.20 as you mentioned,
you just have to download Slide binaries and copy the slide.war file to the webapps folder in Tomcat.

This is the link where u can download the Slide Binaries:
http://jakarta.apache.org/site/downloads/downloads_slide.cgi

If you are using Linux then you must download the one labeled: 2.1 server tar.gz
Copy the slide.war file from this tar to your webapps folder and you should be ready to go.

Are you using the FileStore Adapter or the Database Adapter?  If you are using the database adapter you may
need to copy some *.jar files into your Tomcat/Shared folder depending on the database that you are using.

Or if you would like to install Tomcat again with the bundled Slide as you mentioned then you must have
downloaded Tomcat from the same link that I provided above.
Download the one labeled: 2.1 server Tomcat 5 bundle tar.gz.  This gives you Tomcat 5.0.28 with Slide on it.
Just install this version on Tomcat as you would install any other version, set the environment variables
(CATALINA_HOME) and start Tomcat, and it should be ready to roll. :-)

Regards,

Zeus O. Courtois

----- Original Message ----
From: "Cavallaro, Maria (Civ, ARL/SLAD)" <MCavallaro <at> arl.army.mil>
To: slide-user <at> jakarta.apache.org
Sent: Monday, April 2, 2007 9:15:18 AM
Subject: Which tomcat to download (UNCLASSIFIED)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kostis Anagnostopoulos | 4 Apr 00:32
Picon

Release the webdav client and consider moving it into a jakarta's commons Httpclient

Hi to all developers,

I hava noticed that the WebDAV client library is a very important
piece for many other projects.
But the latest stable version is 2.1, release 2 and a half years ago!
(According to this: http://apache.otenet.gr/dist/jakarta/slide/binaries/)

I would like to ask:

1) Are there any plans for releasing a newer version of slide webdav client?

2) Does anybody agree on me that the WebDAV functionality may belong
to the Apache commons HTTP-Client library?

(I hope) I'm not starting a flame-war, i just wish that this useful
project gets some stable deliverables that others can depend on!

Regards,
  Kostis
Permalink | Reply | 7 comments |
headers
Anthony Shortland | 4 Apr 07:03

FW: Out of memory error with webdav put

Since you guys may wake up before us ... is there a known issue using the
Slide Ant ³put² task to upload large files? I¹m getting an out of memory
error trying to put ~320MB.

Thanks,

Anthony.

------ Forwarded Message
From: Anthony Shortland <anthony <at> controltier.com>
Date: Tue, 03 Apr 2007 21:53:03 -0700
To: "dev <at> controltier.com" <dev <at> controltier.com>
Conversation: Out of memory error with webdav put
Subject: Re: Out of memory error with webdav put

Hacking ad to up the heap-size didn¹t help:

+ java -Xmx756m -Xms256m -classpath
/export/home/shopintuit/ctier/pkgs/antdepo-20070327/classes:/export/home/sho
pintuit/ctier/pkgs/antdepo-20070327/pkgs/apache-ant-1.7.0/lib/xerces-2.6.0.j
ar:/export/home/shopintuit/ctier/pkgs/antdepo-20070327/pkgs/apache-ant-1.7.0
/lib/xml-apis.jar -Dcmdr.classname=org.antdepo.cli.ADCmdrMain
-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol
-Djavax.net.ssl.trustStore=/export/home/shopintuit/ctier/etc/truststore
-Djavax.net.ssl.trustStoreType=jks
-Dantdepo.base=/export/home/shopintuit/ctier
-Dantdepo.home=/export/home/shopintuit/ctier/pkgs/antdepo-20070327
-Dant.home=/export/home/shopintuit/ctier/pkgs/antdepo-20070327/pkgs/apache-a
nt-1.7.0 -Dcontext.user=shopintuit
-Dframework.userinfo=/export/home/shopintuit/.frameworkUser
(Continue reading)

Permalink | Reply | 0 comments |
headers
Oliver Zeigermann | 4 Apr 09:53
Picon

Re: Release the webdav client and consider moving it into a jakarta's commons Httpclient

Maybe it is a good idea to move the WebDAV client library to Jakarta
Commons. However, there must be an individual driving the process.

Oliver

2007/4/4, Kostis Anagnostopoulos <ankostis <at> gmail.com>:
> Hi to all developers,
>
> I hava noticed that the WebDAV client library is a very important
> piece for many other projects.
> But the latest stable version is 2.1, release 2 and a half years ago!
> (According to this: http://apache.otenet.gr/dist/jakarta/slide/binaries/)
>
> I would like to ask:
>
> 1) Are there any plans for releasing a newer version of slide webdav client?
>
> 2) Does anybody agree on me that the WebDAV functionality may belong
> to the Apache commons HTTP-Client library?
>
>
> (I hope) I'm not starting a flame-war, i just wish that this useful
> project gets some stable deliverables that others can depend on!
>
>
> Regards,
>   Kostis
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe <at> jakarta.apache.org
(Continue reading)

Permalink | Reply | 6 comments |
headers
Martin van den Bemt | 5 Apr 00:42
Gravatar

Re: Release the webdav client and consider moving it into a jakarta's commons Httpclient

Does it also make technical sense or are there no shared deps between server and client ?
Willing to drive this (the only things I did in Slide was working on the client). At the earliest I
would do this after or at apachecon, since I am really swamped till the end of the month

Mvgr,
Martin

Oliver Zeigermann wrote:
> Maybe it is a good idea to move the WebDAV client library to Jakarta
> Commons. However, there must be an individual driving the process.
> 
> Oliver
> 
> 2007/4/4, Kostis Anagnostopoulos <ankostis <at> gmail.com>:
>> Hi to all developers,
>>
>> I hava noticed that the WebDAV client library is a very important
>> piece for many other projects.
>> But the latest stable version is 2.1, release 2 and a half years ago!
>> (According to this: http://apache.otenet.gr/dist/jakarta/slide/binaries/)
>>
>> I would like to ask:
>>
>> 1) Are there any plans for releasing a newer version of slide webdav
>> client?
>>
>> 2) Does anybody agree on me that the WebDAV functionality may belong
>> to the Apache commons HTTP-Client library?
>>
>>
(Continue reading)

Permalink | Reply | 5 comments |
headers
Oliver Zeigermann | 5 Apr 12:19
Picon

Re: Release the webdav client and consider moving it into a jakarta's commons Httpclient

It does make sense also from the technical view. AFAIK client and
server are independent developments.

Oliver

2007/4/5, Martin van den Bemt <mllist <at> mvdb.net>:
> Does it also make technical sense or are there no shared deps between server and client ?
> Willing to drive this (the only things I did in Slide was working on the client). At the earliest I
> would do this after or at apachecon, since I am really swamped till the end of the month
>
> Mvgr,
> Martin
>
> Oliver Zeigermann wrote:
> > Maybe it is a good idea to move the WebDAV client library to Jakarta
> > Commons. However, there must be an individual driving the process.
> >
> > Oliver
> >
> > 2007/4/4, Kostis Anagnostopoulos <ankostis <at> gmail.com>:
> >> Hi to all developers,
> >>
> >> I hava noticed that the WebDAV client library is a very important
> >> piece for many other projects.
> >> But the latest stable version is 2.1, release 2 and a half years ago!
> >> (According to this: http://apache.otenet.gr/dist/jakarta/slide/binaries/)
> >>
> >> I would like to ask:
> >>
> >> 1) Are there any plans for releasing a newer version of slide webdav
(Continue reading)

Permalink | Reply | 4 comments |
headers
Oliver Zeigermann | 6 Apr 13:39
Picon

Re: Release the webdav client and consider moving it into a jakarta's commons Httpclient

If anyone is willing to do some work in the client: Is it easily
possible to add form based authentication to allow access to Exchange
servers having this form of authentication?

More info can be found here:

http://www.infinitec.de/articles/exchange/webdavwithfba.aspx

Cheers
Oliver

2007/4/5, Oliver Zeigermann <oliver <at> zeigermann.de>:
> It does make sense also from the technical view. AFAIK client and
> server are independent developments.
>
> Oliver
>
> 2007/4/5, Martin van den Bemt <mllist <at> mvdb.net>:
> > Does it also make technical sense or are there no shared deps between server and client ?
> > Willing to drive this (the only things I did in Slide was working on the client). At the earliest I
> > would do this after or at apachecon, since I am really swamped till the end of the month
> >
> > Mvgr,
> > Martin
> >
> > Oliver Zeigermann wrote:
> > > Maybe it is a good idea to move the WebDAV client library to Jakarta
> > > Commons. However, there must be an individual driving the process.
> > >
> > > Oliver
(Continue reading)

Permalink | Reply | 0 comments |
headers
Martin van den Bemt | 7 Apr 15:41
Gravatar

Re: Release the webdav client and consider moving it into a jakarta's commons Httpclient

So technically it is ok to separate them.

Slide is doing better on activity atm and I rather focus on increasing that activity and in the end
move to a Slide TLP, then splitting up Slide to commons, leaving Slide with just the server part and
possibly no future of becoming TLP and therefor no future.
Also I wonder if commons is a place where the slide client has any life expectancy, since people
interested in webdav are hanging around here and not necessarily at commons.

Though choice.

Mvgr,
Martin

Oliver Zeigermann wrote:
> It does make sense also from the technical view. AFAIK client and
> server are independent developments.
> 
> Oliver
> 
> 2007/4/5, Martin van den Bemt <mllist <at> mvdb.net>:
>> Does it also make technical sense or are there no shared deps between
>> server and client ?
>> Willing to drive this (the only things I did in Slide was working on
>> the client). At the earliest I
>> would do this after or at apachecon, since I am really swamped till
>> the end of the month
>>
>> Mvgr,
>> Martin
>>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Darren Hartford | 9 Apr 14:39

RE: Release the webdav client and consider moving it into a jakarta's commons Httpclient

From a user standpoint, moving the slide client to commons does make
sense.  As a library user and from an application developer you would
either be:

1) working on a content storage, at which point working with Slide
Server.

2) working on accessing internal or external WebDAV repositories, at
which point only interested in the webdav-client.  

2a) This also has a double-benefit when looking at commons-vfs that you
get a 'commons-webdav' library instead of, presently, downloading the
slide source tree to compile a recent webdav client lib with several
bugfixes that are not in an existing binary yet.

Bonus)  Since the Apache Jackrabbit project also has a WebDAV client
library, would be a very good opportunity to bring the two different
client libraries together under one 'commons-webdav' (or whatever it
will be called).

As to with commons-httpclient, or as its own commons-library, that is
open for discussion.  WebDAV has a dependency on commons-httpclient, but
since WebDAV has its own level of domain knowledge above and beyond
normal HTTP, keeping it on its own does not seem unreasonable (again,
based on the domain knowledge needed).

My two coppers,
-D 

> -----Original Message-----
(Continue reading)

Permalink | Reply | 1 comment |

Gmane