Smaller mapping files

0 views
Skip to first unread message

Dmitriy Nagirnyak

unread,
Aug 3, 2008, 11:22:36 PM8/3/08
to
Hi,

Is there an option (out of the box) in ECO to separate mapping XML into smaller
parts?
One of these ways:
- File per class.
- File per modeled package.
- File per number of classes.

Are there any considerations by ECO Team to add support for it if it's NA
yet?

Cheers,
Dmitriy.


Peter Morris

unread,
Aug 4, 2008, 3:31:06 AM8/4/08
to
In the meantime what about creating smaller XML files yourself, embedding
them as resources, and then building the XML document in memory at app
startup? Would that work?

Dmitriy Nagirnyak

unread,
Aug 4, 2008, 7:33:56 PM8/4/08
to
Hello Peter,

> In the meantime what about creating smaller XML files yourself,
> embedding them as resources, and then building the XML document in
> memory at app startup? Would that work?
>

That would, but the aim is to make mapping maintenance easier.
This way it doesn't look like it's easier.

Do you think I should add this to mantis?

Cheers.


Peter Buchmann

unread,
Aug 6, 2008, 9:44:06 AM8/6/08
to
Hello Dmitry,

> That would, but the aim is to make mapping maintenance easier.
> This way it doesn't look like it's easier.
>
> Do you think I should add this to mantis?
>

this is somehow similar to my mantis issue #0000209: improve XML OR mapping:

> As for now the XML OR mapping file has to contain all classes within the
> EcoSpace.
> In a project with lots of classes and only a few classes with non standard
> OR mapping it is necessary to map all classes, even when most of them have
> standard
> mapping.
> It would be a noticable improvement when only classes should need to be
> mapped
> when they difer from standard mapping. The lowest granularity could be a
> class (table). A manual change of attributes would only be necessary in
> those few
> classes.
>
> Problems could occur with associations. Therefor a syntax checker could
> make shure that all associations and classes are mapped correctly.
>
> In addition to that ECO could create the standard XML mapping for single
> classes
> instead of the complete model. Or even better: ECO could support the user
> with
> an expert to create the OR mapping for one class.

In this point, I also see some chances to improve ECO. Maybe in ECO 6 or 7?

Peter Buchmann

Dmitriy Nagirnyak

unread,
Aug 6, 2008, 8:36:54 PM8/6/08
to
Hello Peter,

> this is somehow similar to my mantis issue #0000209: improve XML OR
> mapping:
>

I like this a lot.

> In this point, I also see some chances to improve ECO. Maybe in ECO 6
> or 7?
>

I doubt it is going to implemented very soon. Unfortunately.


Reply all
Reply to author
Forward
0 new messages