What java.net.HttpURLConnection has to do with Tomcat and comet is
that HttpURLConnection is Java's implementation of an http client and
will likely be used by people developing comet apps for Tomcat. In my
case, I want to use it because I can't use raw sockets on my applet
client due to permissio
On page 120 of the servlet spec., it is stated referring to the
element in the section of an
application's web.xml:
~
The form-login-page element defines the location in the web app where
the page that can be used for login can be found. The path begins with
a leading / and is interpreted relat
"Eric B." <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
> I have a simple filter whose goal is to set the content type for a page.
> However, when I check the actual headers that are returned by the server,
> I see that they have been overridden by something in Tomcat; I'm
I'm not sure what HttpURLConnection has to do with Tomcat or comet.
and yes, asynchronous writes are possible, just not after the END or
ERROR events have been issued
Filip
Peter Warren wrote:
Does that mean that HttpURLConnection cannot be used for comet
requests with asynchronous (i.e. dela
"Bill Barker" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> "Caldarale, Charles R" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>>> Subject: Filtering the apache clients
>>>
>>> Is there any way of configuri
Does that mean that HttpURLConnection cannot be used for comet
requests with asynchronous (i.e. delayed) responses?
It would seem so to me since HttpURLConnection always sends an END
message before reading from the server and since the server can no
longer write to the client after closing the com
We have signed the applet properly but it changes nothing.
The first DLL, created with JNI, works well. Because : there are several
fonctions in the second DLL (this one in language C). The first function
(which doesn't use threads) works well but when we call the second
function (which uses m
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker
> Subject: Re: Filtering the apache clients
>
> This won't work, since under AJP/1.3 the "Remote Address" is
> the address of the client that connects to Apache, not the
> address of the Apache machine.
Ahah - thanks for the corre
You mean in all cases it runs client-side? Then it's not a tomcat
related problem. Applet, to be able to run JNI, must be properly signed
and run with security authorisation needed. Moreover, the JNI libraries
must be installed on client.
Claire Dugenet a écrit :
Hello,
In the two case (with
Always getting this error message while shutting down tomcat.
ERROR: transport error 202: bind failed: Address already in use
["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
["debugInit.c",L500]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports
On Fri, 2008-01-18 at 20:36 +, Neha Agrawal wrote:
> hi
>my tomcat5.5 server works correctly with APR
> as it showing default web pages for both 8180 and 8443
> ports..
>
> but when i try to open catalina.out file in the logs
> directory it hangs the terminal..file shows no data..
> when
Hello,
In the two case (with or without Tomcat), we call it with a button
because we use the same applet. Normally, the applet is independant of
Tomcat but it makes a difference when we use this applet with Tomcat
(http://localhost:8080 ...) or whithout Tomcat (file:///C:/ ...).
We have try
12 matches
Mail list logo
