https://issues.apache.org/bugzilla/show_bug.cgi?id=50523
Summary: Unsuccessfully Deployed WebApplication Has Not Removed
From JMX Server When Undeployed
Product: Tomcat 7
Version: 7.0.5
Platform: PC
OS/Version: Linux
https://issues.apache.org/bugzilla/show_bug.cgi?id=48661
William Leung changed:
What|Removed |Added
CC||l...@21cn.com
--
Configure bugmai
On 27.12.2010 21:22, Christopher Schultz wrote:
So the plan would be to have users convert values like this:
127\.0\.0\.1, 10\.10\.10\.1, 192\.168\.1\.[0-9]+
to this:
(127\.0\.0\.1|10\.10\.10\.1|192\.168\.1\.[0-9]+)
which is equivalent to
127\.0\.0\.1|10\.10\.10\.1|192\.168\.1\.[0-9]+
if w
Tim,
On 12/25/2010 3:34 PM, Tim Funk wrote:
> I am thinking from an admin point of view. While you can combine OR
> conditionals in regex's - when you get something more complicated - you
> may encounter a nasty nesting of () to get all the nested OR's correct.
One can always use more, simpler |
Mark,
On 12/24/2010 1:34 PM, Mark Thomas wrote:
> There are a number of configuration properties defined as "comma
> separated regular expressions". As someone pointed out at at ApacheCon
> that is a little odd. It stops "," being used in an expression and is
> inefficient.
A comma can still be u
https://issues.apache.org/bugzilla/show_bug.cgi?id=27717
Jeremy Boynes changed:
What|Removed |Added
Attachment #26445|0 |1
is obsolete|
On 25.12.2010 20:53, Mark Thomas wrote:
On 25/12/2010 01:49, Tim Funk wrote:
+0.5 - I wonder if in some cases - it may be preferable to use a
property called split which lets the user define the separator which we
can pass to String.split(). [Which OTOH may be more confusing (yet
powerful) since
