I'm sure Miguel will give your suggestion (and contribution!) due
consideration when he puts together more detailed development plans for the
Ganymede release... at this point, the OCL Tools component has yet to be
provisioned. :(

One area where the UML API is particularly weak on is protecting itself
in cases where exceptions are triggered precisely because something has
made the model ill-formed - e.g., a circular containment hierarchy, a
circular generalization hierarchy, etc... In some cases (e.g., circular
containment induced from a package merge operation gone bad), we can
even induce an infinite loop in the exception handling code that
attempts to undo the mess. I observed these things in the Eclipse 3.2
environment I work with (uml 2.0.4) From the CVS logs, I am not sure if
the issues are still there or not. If they are, is this the sort of
issue that could be considered for the MDT 1.1 plan?

If possible, could you please raise specific defects (with steps to
reproduce the problem).
Contributions from the community regarding filling out the various
validation functions is always welcomed ;).

Cheers,
- James.

"Nicolas Rouquette" <nicolas.rouquette@jpl.nasa.gov> wrote in message
news:47315E30.4040903@jpl.nasa.gov...
> Hi Kenn,
>
> One area where the UML API is particularly weak on is protecting itself in
> cases where exceptions are triggered precisely because something has made
> the model ill-formed - e.g., a circular containment hierarchy, a circular
> generalization hierarchy, etc... In some cases (e.g., circular containment
> induced from a package merge operation gone bad), we can even induce an
> infinite loop in the exception handling code that attempts to undo the
> mess. I observed these things in the Eclipse 3.2 environment I work with
> (uml 2.0.4) From the CVS logs, I am not sure if the issues are still there
> or not. If they are, is this the sort of issue that could be considered
> for the MDT 1.1 plan?
>
> Cheers,
> -- Nicolas.
>
>
> Kenn Hussey wrote:
>> A draft of the development plan for MDT 1.1, targeted for June 2008 as
>> part of the Ganymede simultaneous release, has been posted at
>> http://www.eclipse.org/modeling/mdt/docs/plans/mdt_project_p lan_1_1.html.
>> Feedback is welcome.
>>
>> Kenn
>>
>>

I'm sure Miguel will give your suggestion (and contribution!) due
consideration when he puts together more detailed development plans for the
Ganymede release... at this point, the OCL Tools component has yet to be
provisioned. :(

One area where the UML API is particularly weak on is protecting itself
in cases where exceptions are triggered precisely because something has
made the model ill-formed - e.g., a circular containment hierarchy, a
circular generalization hierarchy, etc... In some cases (e.g., circular
containment induced from a package merge operation gone bad), we can
even induce an infinite loop in the exception handling code that
attempts to undo the mess. I observed these things in the Eclipse 3.2
environment I work with (uml 2.0.4) From the CVS logs, I am not sure if
the issues are still there or not. If they are, is this the sort of
issue that could be considered for the MDT 1.1 plan?

If possible, could you please raise specific defects (with steps to
reproduce the problem).
Contributions from the community regarding filling out the various
validation functions is always welcomed ;).

Cheers,
- James.

"Nicolas Rouquette" <nicolas.rouquette@jpl.nasa.gov> wrote in message
news:47315E30.4040903@jpl.nasa.gov...
> Hi Kenn,
>
> One area where the UML API is particularly weak on is protecting itself in
> cases where exceptions are triggered precisely because something has made
> the model ill-formed - e.g., a circular containment hierarchy, a circular
> generalization hierarchy, etc... In some cases (e.g., circular containment
> induced from a package merge operation gone bad), we can even induce an
> infinite loop in the exception handling code that attempts to undo the
> mess. I observed these things in the Eclipse 3.2 environment I work with
> (uml 2.0.4) From the CVS logs, I am not sure if the issues are still there
> or not. If they are, is this the sort of issue that could be considered
> for the MDT 1.1 plan?
>
> Cheers,
> -- Nicolas.
>
>
> Kenn Hussey wrote:
>> A draft of the development plan for MDT 1.1, targeted for June 2008 as
>> part of the Ganymede simultaneous release, has been posted at
>> http://www.eclipse.org/modeling/mdt/docs/plans/mdt_project_p lan_1_1.html
>> Feedback is welcome.
>>
>> Kenn
>>
>>