|
From: Sandro M. <naa...@gm...> - 2006-02-06 20:55:34
|
On 2/6/06, Sandro Magi <naa...@gm...> wrote:
>
> On 2/4/06, Tyler Close <ty...@wa...> wrote:
> >
> >
> > 7. how the waterken server manages mutable state
> >
> > After that, I think we've got a good list.
> >
> > Perhaps the "Hello World!" example should be just that:
> >
> > public final class
> > Hello {
> > public static String
> > getGreeting() { return "Hello World!"; }
> > }
>
>
>
> I'm working through these now. The invocation of Hello-class-new<https://=
waterken.naasking.homeip.net/http/localhost/magi/Hello-class-new>doesn't su=
cceed; there is an XML parsing error of some sort.
>
> See and click "submit":
> https://waterken.naasking.homeip.net/wwwsandro/?key=3Dyrlx-qhrn-biqy
>
Here is the class description after the above is loaded:
https://waterken.naasking.homeip.net/wwwsandro/?key=3Dtppd-alyt-2opn
I notice that "getGreeting()" has been translated to simply "greeting". Do
you impose a naming convention on Java classes in order to enforce this, eg=
.
all methods starting with "get" will have that prefix removed?
Here is the interface for the mutable Hello example:
https://waterken.naasking.homeip.net/wwwsandro/?key=3Dnyb2-e3ra-e6sg
Here "setGreeting()" translates to "set_greeting". Where can I look for the
translation rules?
Sandro
|