[Helma-user] HobObject Hierarchy w/o Code?

[Philip Weaver]

 For example, here is the Root type.properties from the Address Book
tutorial. It configures children as a collection of Person HopObjects.

_children = collection(Person)
_children.accessname = ID
_children.order = LASTNAME asc

What if instead you wish for a subtoken of Root to serve any sort of
HopObject based on the token used? {root}/one/ calls the main action of the
HopObject prototype called 'One'.  {root}/two/ calls the main action of the
HopObject prototype called 'Two'. I think I understand the power of
HopObjects and collections relating to databases. But what if I want two use
Helma for a request or two just like I'd use JSPs in nested directories?

On Nov 23, 2007 10:12 PM, Philip Weaver <philmaker at gmail.com> wrote:

> This should be simple to do. I want to serve {root}/one/two/main.hac. And
> I do not create the HopObject chain in code. Does a directory structure for
> 'one/two/' belong inside the Root directory? If so, why can I not get this
> to work by default without configuring type.properties? I even tried with
> configuring type.properties to some extent. Can it reside alongside root
> and it is connected somehow via type.properties? Even if I place the 'one'
> directory directly inside root, Helma serves the actions of 'one' as actions
> of Root. Does this have to do with collections? I'm not understanding
> collections. type.properties is not well documented in general, it is not
> documented for such a basic task such as this, and I can not find any
> existing Helma examples which serve filesystem specified directories under
> root.
>
> Thanks for reading. Please help.
> Phil
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://helma.org/pipermail/helma-user/attachments/20071123/ed596ad0/attachment.html