| [ohf-dev] Re: ohf-dev Digest, Vol 18, Issue 13 |
Send ohf-dev mailing list submissions to
ohf-dev@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/ohf-dev
or, via email, send a message with subject or body 'help' to
ohf-dev-request@xxxxxxxxxxx
You can reach the person managing the list at
ohf-dev-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ohf-dev digest..."
Today's Topics:
1. Re: inconsistency in documentation (John Thomas)
2. FW: Generate xml instance (Brandon Ulrich)
----------------------------------------------------------------------
Message: 1
Date: Wed, 13 Jun 2007 12:44:25 -0700
From: "John Thomas" < jthomas119@xxxxxxxxx>
Subject: Re: [ohf-dev] inconsistency in documentation
To: "Open Healthcare Framework Mailing list" < ohf-dev@xxxxxxxxxxx>
Message-ID:
<7d39db9c0706131244q5fdb8b38u86ec3e0b8a8e7f95@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I have also updated the instructions in the Wiki. Sorry for the confusion
On 6/12/07, Vincent David <vincent@xxxxxxxxxxxxx> wrote:
> Hello,
>
> I'm recently trying to install the development package of STEM on a
> Mac running Eclipse 3.3RC4.
>
> While working my way through the installation and setup docs a ran
> over an inconsistency on following page:
>
> http://wiki.eclipse.org/index.php/STEM_Eclipse_Setup
>
> It says in the chapter "Installing Eclipse Features" how to configure
> eclipse.contrib to point to:
>
> "...\eclipse-contrib\eclipse"
>
> However, in chapter "UMLet" one is instructed to install named
> plugin to another desination:
>
> "..\eclipse-contrib\tools-plugins\eclipse"
>
> Hence the ant variable eclipse.contrib pointing to the old
> destination is now inconsistent, and executing "update.xml" from the
> plugin "org.eclipse.ohf.stem.internal.data" pops up with errors.
> Pointing eclipse.contrib to mentioned new destination fixes the bug.
>
> thx
>
> Vincent David_______________________________________________
> ohf-dev mailing list
> ohf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ohf-dev
>
--
John
------------------------------
Message: 2
Date: Thu, 14 Jun 2007 08:43:29 +0200
From: Brandon Ulrich <bulrich@xxxxxxxxxxxxxxxxxxx >
Subject: [ohf-dev] FW: Generate xml instance
To: OHF Developers List <ohf-dev@xxxxxxxxxxx>
Message-ID: < C296B031.FF96%bulrich@xxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
Forwarding the resolution to Aysegul¹s problem in case anyone has similar
issues.
--
Brandon Ulrich, bulrich@xxxxxxxxxxxxxxxxxxx
B2 International Ltd., http://www.b2international.com
Tel +44 113 350-2594
------ Forwarded Message
From: Aysegul Cetin <aysegulcetin@xxxxxxxxx>
Reply-To: Aysegul Cetin <aysegulcetin@xxxxxxxxx>
Date: Wed, 13 Jun 2007 12:01:54 +0300
To: <ravi.natarajan@xxxxxxx>
Cc: <tooling@xxxxxxxxxxxxx>
Subject: Re: Generate xml instance
Firstly, thanks a lot for your help.
We solved the problem and here is the solution for the one who interested
in:
We changed RMIM Designer version to 4.3.0.2 <http://4.3.0.2> .
We used xml output of RMIM Designer to feed V3 Generator.
Then V3 Generator generated MIF 1.0 version and we changed MIF version to
2.0 using MIF Converter of OHF.
Then message instance editor easily generated xml instances.
The problem is because of generated tags of MIF files. MIF tags were
starting with serializedStaticModel and at the newer version tags are
starting with staticModel which solves our problem.
We also tried to generate xml instances using RoseTree. Rose Tree generates
instances withouth class, mood and type classes. I think that example
database(dtExamp.mdb) at Rose Tree is not enough for generating instances
completely.
have a nice day.
Aysegul Avci
On 6/13/07, ravi.natarajan@xxxxxxx < ravi.natarajan@xxxxxxx
<mailto:ravi.natarajan@xxxxxxx > > wrote:
> Hello,
>
> The MIF instance editor come with inbuilt mif 1.0 to mif 2.0
> conversion. The conversion is xslt driven with functionality to persist the
> same. The help documentation within the plug-in explains in details how to
> create the instance from MIF. You cannot create instance from xsd within the
> MIF instance editor alternatively you can use tools like xmlspy to help you in
> this. If there are errors related to MIF validation you may have problems
> within your main MIF 1.0 artifact created using the v3Generator.Which version
> of the v3Generator you are using are your models in HMD format ?. If you post
> your error's and artefacts within the OHF site where some one can look into
> and provide you more suggestions.
>
>
> regards
> Ravi Natarajan
> Sr.Integration Architect
> Comms and Messaging
>
> Technology Office
> NHS Connecting for Health
> Tel: +44 (0)113 2806533
> Mobile: +44 (0)7770408642
> ravi.natarajan@xxxxxxx
>
> NHS Connecting for Health supports the NHS in providing better, safer care by
> delivering computer systems and services which improve the way patient
> information is stored and accessed.
>
>
>
> From: owner-tooling@xxxxxxxxxxxxx [mailto:owner-tooling@xxxxxxxxxxxxx] On
> Behalf Of Aysegul Cetin
> Sent: 12 June 2007 18:20
> To: tooling@xxxxxxxxxxxxx
> Subject: Generate xml instance
>
> Hi all,
> We want to generate xml instance from mif file using OHF eclipse plugin but
> face several problems.
> We follow these steps:
> 1- we generate mif files using V3Generator tool
> 2- we use these mifs and open "message instance editor" to generate xml
> instances at eclipse
> 3-editor says that mif 2.0 version is only supported.
> 4- we convert our mifs 1.0 to 2.0 using plugin then message instance editor
> can not validate mif because of "derivedFrom" element at xml file.
>
> How do we convert our mifs 1.0 to 2.0 truely?
>
> Is there a way to generate xml instances form Mifs or Xsd's. ?
>
> Thanks a lot.
>
>
> ************************************************ To access the Archives of
> this or other lists or change your list settings and information, go to:
> http://www.hl7.org/listservice
> **********************************************************************
> This message may contain confidential and privileged information.
> If you are not the intended recipient please accept our apologies.
> Please do not disclose, copy or distribute information in this e-mail
> or take any action in reliance on its contents: to do so is strictly
> prohibited and may be unlawful. Please inform us that this message has
> gone astray before deleting it. Thank you for your co-operation.
>
> NHSmail is used daily by over 100,000 staff in the NHS. Over a million
> messages are sent every day by the system. To find out why more and
> more NHS personnel are switching to this NHS Connecting for Health
> system please visit www.connectingforhealth.nhs.uk/nhsmail
> < http://www.connectingforhealth.nhs.uk/nhsmail>
> **********************************************************************
>
************************************************ To access the Archives of
this or other lists or change your list settings and information, go to:
http://www.hl7.org/listservice
------ End of Forwarded Message
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/listinfo/ohf-dev/attachments/20070614/b0886940/attachment.html
------------------------------
_______________________________________________
ohf-dev mailing list
ohf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ohf-dev
End of ohf-dev Digest, Vol 18, Issue 13
***************************************