Issue 231 in glassdb: WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default returns a WADispatcher

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 231 in glassdb: WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default returns a WADispatcher

glassdb
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium GLASS-Server Version-GLASS0.231

New issue 231 by [hidden email]:  
WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default  
returns a WADispatcher
http://code.google.com/p/glassdb/issues/detail?id=231

WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default  
returns a WADispatcher

I've deployed a Seaside application and don't want any of the default  
WADispatcher functionality. That is I only want to serve up my application  
and I'm not interested in /config, /browse, /files

One way of achieving this is to use a WAApplication in place of  
WADispatcher. However the maintenance Gem calls  
WABasicDevelopment>>#reapSeasideCache which assumes WADispatcher>>#default  
returns a WADispatcher when it calls #handlers which is implemented on  
WADispatcher but not on WAApplication.

Reply | Threaded
Open this post in threaded view
|

Re: Issue 231 in glassdb: WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default returns a WADispatcher

glassdb

Comment #1 on issue 231 by [hidden email]:  
WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default  
returns a WADispatcher
http://code.google.com/p/glassdb/issues/detail?id=231

I've checked in a fix: Seaside-GemStone-Basic-Development-NickAger.25

Reply | Threaded
Open this post in threaded view
|

Re: Issue 231 in glassdb: WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default returns a WADispatcher

glassdb
Updates:
        Labels: -Version-GLASS0.231 Version-1.0-beta.6 Milestone-1.0-beta.8.6

Comment #2 on issue 231 by [hidden email]:  
WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default  
returns a WADispatcher
http://code.google.com/p/glassdb/issues/detail?id=231

Thanks,

Nic I'll pick this puppy up in the config shortly...

Reply | Threaded
Open this post in threaded view
|

Re: Issue 231 in glassdb: WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default returns a WADispatcher

glassdb
Updates:
        Labels: -GLASS-Server GLASS-Seaside30

Comment #3 on issue 231 by [hidden email]:  
WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default  
returns a WADispatcher
http://code.google.com/p/glassdb/issues/detail?id=231

(No comment was entered for this change.)

Reply | Threaded
Open this post in threaded view
|

Re: Issue 231 in glassdb: WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default returns a WADispatcher

glassdb
Updates:
        Status: Fixed
        Labels: Fixed-1.0-beta.8.6

Comment #4 on issue 231 by [hidden email]:  
WABasicDevelopment>>#reapSeasideCache, assumes WADispatcher>>#default  
returns a WADispatcher
http://code.google.com/p/glassdb/issues/detail?id=231

integrated fixes into Seaside 3.0.4:

Name: ConfigurationOfSeaside30-DaleHenrichs.291
Author: DaleHenrichs
Time: 02/11/2011, 17:45:28
UUID: 3f8954b2-2e16-41cf-847d-b0bf6321eddd
Ancestors: ConfigurationOfSeaside30-DaleHenrichs.290