[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dsdp-mtj-dev] MTJ Model


Can you please point us at the explanation you gave before (mentioned by Kevin)? Maybe we can read up on this before the meeting.

During the meeting - It would be good if you could get us all on the same page. I agree we should take a few minutes to address this central component of MTJ.
Is there any presentations you have which you can send out before the meeting?

Please assume that most of us are not familiar with the details of EMF.



Arto.Laurila@xxxxxxxxx wrote:
The current MTJ services are using an EMF based model, that is initially created with any EMF compatible tool.
The tools that Kevin is referring here and what e.g. I have used is the a bit older Rational Rose tool to create the UML model.
I think that even some very old version of Rose can be used with this.
Thus the same model can be done with other tools, like IBM Rational Architect or Modeler or what ever (or even directly with the EMF).
When thinking the current MTJ architecture, there is certainly needed to discuss that does team members have experience on EMF or not.
In case of that would be replaced, it pretty much means that the whole MTJ internal architecture have to be recoded also.
As comparing to other Eclipse based projects, some of those are not using EMF at all and they do model their data model e.g. with plain java.
As it is e.g. with EclipseME (Craig, correct me if I'm wrong).
Why the EMF has been used here, well that enables to have a Eclipse compatible and working data layer, where the initial design is done
with UML and the the MTJ related EMF layer is generated from the UML file. That saves a lot of coding & testing time.
In my part I have to say that if the EMF layer is dropped, I may have problems to participate to create the same functionality again from Nokia
point of view.

    *From:* dsdp-mtj-dev-bounces@xxxxxxxxxxx
    [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] *On Behalf Of *ext
    Raniere Hugo-wha006
    *Sent:* 14. marraskuuta 2007 16:33
    *To:* Mobile Tools for The Java Platform mailing list
    *Subject:* RE: [dsdp-mtj-dev] MTJ Model

    Hi Kevin,

    I’m one of the guys at Motorola intending to work in MTJ. I agree
    with you that having this kind of dependencies may not be good for
    the project, and one of the tasks we are proposing in this MTJ
    reboot is to have an new proposed architecture by beginning of
    next year. For sure we can review the data model for this new
    proposed architecture.

    During the meeting we are also going to talk about the proposed
    planning (more info on mtj wiki). If the meeting time is not
    enough to discuss about the data model, we can set a new activity
    in the planning to analyze the data model.

    Best regards,



    *From:* dsdp-mtj-dev-bounces@xxxxxxxxxxx
    [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Kevin M
    *Sent:* Wednesday, November 14, 2007 11:11 AM
    *To:* dsdp-mtj-dev@xxxxxxxxxxx
    *Subject:* [dsdp-mtj-dev] MTJ Model


    I realize this is a little late for today's meeting, but I would
    like to suggest that as part of the reset, we open the idea of the
    current data model behind the MTJ project. The model stores all of
    the relational data about devices and setup. The model is
    generated using a Rational product, and then converted using the
    EMF project. Arto provided instructions at the very end of our
    relationship explaining how this code is generated, but this ties
    us to a commercial product that many of our participants might not
    have in the future, and makes modifications to the underlaying
    data structure difficult to maintain my team members.

    Kevin Horowitz
    Expeditor Tools Development
    Workplace Portal and Collaboration Software
    IBM - Boca Raton, +1-561-862-2113


dsdp-mtj-dev mailing list