On Jun 25, 2008, at 12:05 PM, Jason Warner wrote:
I took a look at the classloader being used. It only contains one
instance of UniqueId in any of the parent classloaders. I took a
quick look at the changes between Wadi 2.0-M10 and 2.0, and there is
indeed a significant amount of
It seems my understanding of how classloaders work is not as thorough as it
could be. From what I can see, juli doesn't include a UniqueId class, so
I'm not sure how we could get a conflict there. Could you explain how that
could be happening? I could take a look at it for a bit today, though I
On Jun 27, 2008, at 9:55 AM, Jason Warner wrote:
It seems my understanding of how classloaders work is not as
thorough as it could be. From what I can see, juli doesn't include
a UniqueId class, so I'm not sure how we could get a conflict
there. Could you explain how that could be
I took a look at the classloader being used. It only contains one instance
of UniqueId in any of the parent classloaders. I took a quick look at the
changes between Wadi 2.0-M10 and 2.0, and there is indeed a significant
amount of change. In fact, this error stems from a class that didn't even
I've been messing around a little bit with clustering by following the
directions for clustering configuration for jetty[1] but modifying the
instructions to work with tomcat. I've found that the sample app linked in
the example deploys succesfully on the 2.1.1 release but not on the latest
On Jun 23, 2008, at 12:16 PM, Jason Warner wrote:
I've been messing around a little bit with clustering by following
the directions for clustering configuration for jetty[1] but
modifying the instructions to work with tomcat. I've found that the
sample app linked in the example deploys
Hi Kevan,
Thanks for the reply. I was able to deploy succesfully on 2.1.2-SNAPSHOT
with Jetty just fine so it appears to be just Tomcat. I'll follow your
advice about using the debugger and post anything useful I come across.
On Mon, Jun 23, 2008 at 2:37 PM, Kevan Miller [EMAIL PROTECTED]
