I know people generally hate vague handwaving bug reports, but when I moved my application using Seaside and Wakom from 7069 to 7158, I found that it no longer started the listener port automatically, and that classes I changed wouldn't show up in my web app until another stop and restart. So, something has been introduced to destabilize some working stuff. Is there anything known about this, or anything I could do to narrow it down? For now, I moved back to 7069 to get the rest of my work done.
On Mon, Oct 22, 2007 at 07:25:45AM -0700, Randal L. Schwartz wrote:
I know people generally hate vague handwaving bug reports, but when I moved my application using Seaside and Wakom from 7069 to 7158, I found that it no longer started the listener port automatically, and that classes I changed wouldn't show up in my web app until another stop and restart. So, something has been introduced to destabilize some working stuff. Is there anything known about this, or anything I could do to narrow it down? For now, I moved back to 7069 to get the rest of my work done.
perhaps the problem is with 7142, which broke a number of working things. Try an image before that, like 7137
"Matthew" == Matthew Fulmer tapplek@gmail.com writes:
Matthew> perhaps the problem is with 7142, which broke a number of Matthew> working things. Try an image before that, like 7137
Thanks, I'll try that later today when I have my smalltalk task on the top of the stack again. Apparently, I have a case of the mondays. :)
squeak-dev@lists.squeakfoundation.org
-
Matthew Fulmer -
merlyn＠stonehenge.com