https://issues.apache.org/bugzilla/show_bug.cgi?id=43957
Richard Fearn <[EMAIL PROTECTED]> changed:
What|Removed |Added
Status|RESOLVED|CLOSED
---
https://issues.apache.org/bugzilla/show_bug.cgi?id=44871
Summary: Cookie parsing issue
Product: Tomcat 5
Version: 5.5.26
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Compone
https://issues.apache.org/bugzilla/show_bug.cgi?id=44679
Filip Hanik <[EMAIL PROTECTED]> changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
https://issues.apache.org/bugzilla/show_bug.cgi?id=44871
Filip Hanik <[EMAIL PROTECTED]> changed:
What|Removed |Added
Status|NEW |RESOLVED
On Apr 22, 2008, at 6:25 PM, Paul Benedict wrote:
Is that enough so that web applications, either as a whole or in
partial,
can be upgraded without stopping them? It's my understanding that if
web
applications are loaded in an OSGi classloader, these kind of things
are
possible.
I've hea
I'm not an expert, but I think I can tell you that yes, "hello world"
applications can be upgraded without stopping, real
applications can't.
As long as you use sessions or statics or you make config changes -
you have to restart the webapp.
OSGI is good of having 2 versions of a bundle running at
> OSGI is good of having 2 versions of a bundle running at the same time
> - but it won't help you much, the servlet
> engine needs to know where to send the requests, it has no clue a
> request should go to the old version or the new.
May be additions to servlet specs should be planned, ie, b
> I've heard various claims of this nature from osgi zealots, but when
> talking to apparent experts the only things resembling this they seemed to
> know about were grad student experiments that did not have production use as
> even a far-in-the-future goal. Do you know of any actual examples of
