Re: MidgardConfigFile

Hi,

On 1/6/06, Piotras <[email protected]> wrote:
> For ad-hoc remote database or *pure* desktop application both solutions (mine and
> yours are bad ).  In such case , configuration should be handled quite different way
> and probably explicit object's setters should be added.

That's all I ask. Specify a way to do this and I'll be perfectly happy. :-)

Think about how to implement backwards compatibility with the
MidgardDatabase etc. directives with the new GObject configuration
mechanism. When you've solved that, you'll probably also have a
solution for the above use case.

I won't go any deeper into the implementation details.

> I was rather asking about problems with update, create , get_by_xxx methods.

These are all things that I'm currently unable to use because of the
unsolved higher-level issues. For example all the create, update, and
delete methods are totally useless to me until there is a clear
definition of how they are really supposed to work with MultiLang
content. (And don't answer this with a simple example, I need a clear
document that answers the conceptual issues I raised in the recent
MultiLang thread.)

My current solution is to implement all the missing or incompletely
specified functionality in Java in a somewhat deterministic way, but
this is certainly not acceptable in the long run.

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - [email protected]
Software craftmanship, JCR consulting, and Java development