> > On Friday, April 26, 2002, at 04:26 PM, Colin Sampaleanu wrote: > > > Now the ApplicationServlet class is definitely there, in fact I have > > used the same .war file in Resin with some success (problems mentioned > > in another email). Has anybody seen this happening under WebLogic. This > > is a completely standard setup, similar to how Struts is configured, or > > any number of other web-apps. This is probably a WebLogic issue,
As noted elsewhere, looks like WebLogic can't handle certain filenames. > > but on > > the other hand I've never seen anything like this happen under WL, so I > > am thinking it has somehting to do with this confuguration... I am > > quite willing and able to trace deeper into this, but unfortunatley due > > to a deadline and a bus. trip next week can only allocate some hours to > > it in about a week and a half from now... > > > > Thanks for any info, > > Hi Colin, > > I'm using Tapestry with WebLogic 6.1(SP1) for a bigger project at work. > So far I have only had problems with the inspector. The inspector, once > activated (clicked on it and opened the satellite window), eats up all > the memory (256MB for the VM) within one minute (more or less). This is interesting! I've never noticed the Inspector doing anything bad like this. One thing the Inspector does, on the Engine tab, is serialize the application engine, then deserialize and dump it out. That could eat up a bit of cycles while it runs ... but not megabytes! > > Cheers, > > Marcus > -- [EMAIL PROTECTED] http://tapestry.sf.net _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
