[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [dsdp-mtj-dev] MTJ Model
|
There are a number of people on right
now...
US Toll
free: | +1-877-825-8522
|
Int'l or US Toll:
| +1-770-615-1247
|
Finland:
| 0800770232
|
Brazil:
| 0800-891-6245
|
Passcode:
| 4293495# |
Ken Wallis
Team Lead - RAD Tools, Research In
Motion
905-629-4746 x4369
Hi
I cannot access to the telco, cause I get
innformation thta the access code is invalid?
Are others able to
participate?
-Arto
The description of generating the
model code is in CVS at dev.eclipse.org
/cvsroot/dsdp/org.eclipse.mtj/mtj-home/docs/MTJ_model_codegen.ppt
It is a decent start to get you generating
the model, although a few of the steps are missing or in the wrong
order.
The architecture documents
that you should be looking at for more basic understanding are in the same
directory, You will need to check the datestamps from CVS to determine
which one is the last, but look at the MTJ Release 1 Architecture* documents
for an intro, or the presentations we have one the eclipse/MTJ website that we
gave at EclipseCon.
kevin
--
Kevin
Horowitz
khorowit@xxxxxxxxxx
Expeditor Tools Development
Workplace
Portal and Collaboration Software
IBM - Boca Raton,
+1-561-862-2113
From:
| Christian Kurzke
<christian@xxxxxxxxxxxx>
|
To:
| Mobile Tools for The Java Platform
mailing list <dsdp-mtj-dev@xxxxxxxxxxx>
|
Date:
| 11/14/2007 10:43 AM
|
Subject:
| Re: [dsdp-mtj-dev] MTJ
Model |
Arto,
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.
Thanks!
-Christian
Arto.Laurila@xxxxxxxxx
wrote:
> Hi,
> 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.
> -Arto
>
>
------------------------------------------------------------------------
>
*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,
>
> Hugo
>
>
------------------------------------------------------------------------
>
>
*From:* dsdp-mtj-dev-bounces@xxxxxxxxxxx
>
[mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Kevin M
> Horowitz
>
*Sent:* Wednesday, November 14, 2007 11:11 AM
>
*To:* dsdp-mtj-dev@xxxxxxxxxxx
> *Subject:* [dsdp-mtj-dev]
MTJ Model
>
>
> Hi,
>
>
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
> --
> Kevin Horowitz
>
khorowit@xxxxxxxxxx
> Expeditor Tools
Development
> Workplace Portal and Collaboration
Software
> IBM - Boca Raton,
+1-561-862-2113
>
>
------------------------------------------------------------------------
>
>
_______________________________________________
> dsdp-mtj-dev mailing
list
> dsdp-mtj-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
>
_______________________________________________
dsdp-mtj-dev
mailing list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.