On 16/05/2013 23:47, Rossen Stoyanchev wrote:
> Is this expected to run successfully?
Yes. And it does so when I run it locally.
> I am seeing failures when running with `wstest -m fuzzingserver`.
If 9.1.3 fails consistently for you then I suggest using Wireshark to
look at what is going on.
M
Author: markt
Date: Fri May 17 07:47:58 2013
New Revision: 1483679
URL: http://svn.apache.org/r1483679
Log:
Update expected behaviour comment
Modified:
tomcat/trunk/test/org/apache/catalina/startup/TestHostConfigAutomaticDeployment.java
Modified:
tomcat/trunk/test/org/apache/catalina/start
https://issues.apache.org/bugzilla/show_bug.cgi?id=54928
Mark Thomas changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
Author: markt
Date: Fri May 17 11:32:28 2013
New Revision: 1483743
URL: http://svn.apache.org/r1483743
Log:
Add warning about 'hidden' DIRs in the appBase
Modified:
tomcat/trunk/java/org/apache/catalina/startup/HostConfig.java
tomcat/trunk/java/org/apache/catalina/startup/LocalStrings.pro
Author: markt
Date: Fri May 17 11:32:42 2013
New Revision: 1483744
URL: http://svn.apache.org/r1483744
Log:
Start the addition tests
Modified:
tomcat/trunk/test/org/apache/catalina/startup/TestHostConfigAutomaticDeployment.java
Modified:
tomcat/trunk/test/org/apache/catalina/startup/TestHo
Arlo Louis O'Keeffe created MTOMCAT-223:
---
Summary: Proxy settings are ignored
Key: MTOMCAT-223
URL: https://issues.apache.org/jira/browse/MTOMCAT-223
Project: Apache Tomcat Maven Plugin
Hi,
Developing some sample apps with websockets and tomcat 8 revealed two
issues I’d like to discuss here.
1. There is no proxy support in the implementation of
WebSocketContainer.connectToServer calls. While playing around with the
code it was relatively easy to add this in the implementat
On 17/05/2013 13:07, Niki Dokovski wrote:
> Hi,
>
> Developing some sample apps with websockets and tomcat 8 revealed two
> issues I’d like to discuss here.
>
> 1. There is no proxy support in the implementation of
> WebSocketContainer.connectToServer calls. While playing around with the
>
On Fri, May 17, 2013 at 3:35 PM, Mark Thomas wrote:
> On 17/05/2013 13:07, Niki Dokovski wrote:
> > Hi,
> >
> > Developing some sample apps with websockets and tomcat 8 revealed two
> > issues I’d like to discuss here.
> >
> > 1. There is no proxy support in the implementation of
> > WebSoc
Author: markt
Date: Fri May 17 13:16:34 2013
New Revision: 1483786
URL: http://svn.apache.org/r1483786
Log:
Add redeployResources entries for files that don't exist with a last modified
time of zero to detect the addition a WAR or XML when just a DIR exists
Modified:
tomcat/trunk/java/org/ap
Author: markt
Date: Fri May 17 13:16:49 2013
New Revision: 1483787
URL: http://svn.apache.org/r1483787
Log:
More addition test cases
Modified:
tomcat/trunk/test/org/apache/catalina/startup/TestHostConfigAutomaticDeployment.java
Modified:
tomcat/trunk/test/org/apache/catalina/startup/TestHo
https://issues.apache.org/bugzilla/show_bug.cgi?id=54928
--- Comment #5 from rstoyanc...@yahoo.com ---
OK, thanks. For what it's worth, from brief experimentation calling complete()
in this scenario on Jetty and Glassfish doesn't cause any exceptions. Not sure
that means it works but if it doesn't
Author: markt
Date: Fri May 17 14:15:29 2013
New Revision: 1483816
URL: http://svn.apache.org/r1483816
Log:
Add dummy reload resources to trigger a reload if a WAR or DIR is added to an
XML
Add dummy redploy resources to trigger a redeploy if an XML is added to a WAR
Modified:
tomcat/trunk/j
Author: markt
Date: Fri May 17 14:15:48 2013
New Revision: 1483817
URL: http://svn.apache.org/r1483817
Log:
More addition test cases
Modified:
tomcat/trunk/test/org/apache/catalina/startup/TestHostConfigAutomaticDeployment.java
Modified:
tomcat/trunk/test/org/apache/catalina/startup/TestHo
Author: markt
Date: Fri May 17 18:58:11 2013
New Revision: 1483949
URL: http://svn.apache.org/r1483949
Log:
Add the remaining addition tests and refactor some duplicate code.
Modified:
tomcat/trunk/test/org/apache/catalina/startup/TestHostConfigAutomaticDeployment.java
Modified:
tomcat/tru
On 16/05/2013 21:50, Mark Thomas wrote:
The final (for now) changes are:
> 1. unpackWARs now applies to external WARs as well as WARs located in
> the Host's appBase.
>
> 2. If a WAR is modified (located in the Host's appBase or externally)
> and there is a context.xml file present in the Host's
https://issues.apache.org/bugzilla/show_bug.cgi?id=51294
--- Comment #24 from Mark Thomas ---
The implementation work is complete in trunk. Now is the time to test it and
provide feedback. It will be proposed to back-ported to 7.0.x after a suitable
period (at least several weeks - probably longe
> From: Mark Thomas [mailto:ma...@apache.org]
> Subject: Re: Automatic deployment changes
> 3. A warning is generate if a DIR in the appBase is ignored because
> there is a matching WAR and unpackWARs==false.
The doc at [1] contains this statement:
Note: After deployment, if both a WAR and a DI
On 17/05/2013 20:22, Caldarale, Charles R wrote:
>> From: Mark Thomas [mailto:ma...@apache.org]
>> Subject: Re: Automatic deployment changes
>
>> 3. A warning is generate if a DIR in the appBase is ignored because
>> there is a matching WAR and unpackWARs==false.
>
> The doc at [1] contains this
[Tomcat 7.0.x]
I wonder why UserDatabaseRealm use always global JNDI:
==
Context context = getServer().
getGlobalNamingContext();
database = (UserDatabase) context.lookup(resourceName);
=
but DataSourceRealm is more flexible:
==
if (localDataSource) {
context = ContextB
20 matches
Mail list logo
