[Pharo-users] Problem to connect Seaside and Pharo

Sven Van Caekenberghe sven at stfx.eu
Sun Oct 25 15:03:42 EDT 2015


You have to do (Do it) the #initialize as well, like

MyExample initialize.

Or browse the method and highlight the body and evaluate it (Do it).

> On 25 Oct 2015, at 20:00, Justine STIENNE <justine.stienne at gmail.com> wrote:
> 
> Oh sorry it was not for this conversation. I tried to do what you said, but it doesn't work again.
> 
> Justine
> 
> 2015-10-25 19:55 GMT+01:00 Justine STIENNE <justine.stienne at gmail.com>:
> The installation is ok ! :-) But i cant open the file bak that you give me :-/
> 
> 2015-10-25 18:53 GMT+01:00 Sven Van Caekenberghe <sven at stfx.eu>:
> Hi,
> 
> > On 25 Oct 2015, at 18:46, Justine STIENNE <justine.stienne at gmail.com> wrote:
> >
> > Hello,
> >
> > I have a problem to connect Seaside and Pharo. I explain :
> >
> > ZnZincServerAdaptor is running. When I open localhost:8080, it works. When I want to configure a new entry, I can't find the class that I made on Pharo. I have put the method canBeRoot with true as return value on a class but I can't find it. Can you help me ?
> >
> > Thanks in advance,
> > Justine
> 
> #canBeRoot is just an indication, it has no real effect on its own.
> 
> Traditionally, WAComponent subclasses register themselves explicitly using #initialize on the class side, like this:
> 
> initialize
>   WAAdmin register: self asApplicationAt: self handlerName
> 
> Look for the senders of #register:asApplicationAt: to see what I mean.
> 
> Sven
> 
> 
> 





More information about the Pharo-users mailing list