<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
>
<!-- MHonArc v2.6.10 -->
	<channel>
		<title>rmf-dev</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/maillist.html</link>
		<description>rmf-dev</description>
		<language>en-us</language>
		<pubDate>Sat, 05 May 2012 04:14:50 GMT</pubDate>
		<lastBuildDate>Sat, 05 May 2012 04:14:50 GMT</lastBuildDate>
		<docs>http://blogs.law.harvard.edu/tech/rss</docs>
		<generator>MHonArc RSS 2.0 RCFile</generator>
		<managingEditor>webmaster@eclipse.org (Webmaster)</managingEditor>
		<webMaster>webmaster@eclipse.org (Webmaster)</webMaster>
		<image>
			<title>rmf-dev</title>
			<url>http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg</url>
			<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/maillist.html</link>
		</image>
 

	<item>
		<title>[rmf-dev] Project meta data is out of date for modeling.mdt.rmf</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00100.html</link>
		<description>Mark, Michael, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * There is no next/future release of this project. All Eclipse pr...</description>
		<content:encoded><![CDATA[<pre>Mark, Michael,
Projects are required to keep meta data up to date using the MyFoundation
Portal (<a  href="http://portal.eclipse.org/">http://portal.eclipse.org/</a>).  The following problems were found
with this project's meta-data:

* There is no next/future release of this project. All Eclipse projects
must have a &quot;next release&quot; planned and scheduled.


</pre>]]></content:encoded>
		<pubDate>Sat, 05 May 2012 04:00:07 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00100.html</guid>
		<author>emo@xxxxxxx (portal on behalf of emo)</author>
	</item>


	<item>
		<title>[rmf-dev] Unit Testing</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00099.html</link>
		<description> Hello Kay, Yes. But does unit testing not rely on knowledge of the expected outcome from the SUT to check the real one against? It was just a starting point, a prototype, a 'feasability study' to find out if I'm able to handle a reqif file without ProR. I...</description>
		<content:encoded><![CDATA[<table width="100%"><tr><td bgcolor="#FFFFFF" style="background-color: #FFFFFF; color: #000000; "><font color="#000000">
  
  
    Hello Kay,<br>
    <br>
    <blockquote cite=""
      type="cite">
      <blockquote type="cite">
        <pre wrap="">Generally, this looks correct for using EMF without the Eclipse
infrastructure.  It is preferrable to write code like that in the form
of a unit test, though.  
</pre>
      </blockquote>
      <pre wrap="">Yes. But does unit testing not rely on knowledge of the expected outcome from 
the SUT to check the real one against?
It was just a starting point, a prototype, a 'feasability study' to find out if 
I'm able to handle a reqif file without ProR. I didn't know what to expect.</pre>
    </blockquote>
    <br>
    You're certainly right with your reply.&nbsp; This was just a
    recommendation, and has little to do with your "real" question.<br>
    <br>
    But since you asked, let me elaborate: Because your code contained
    four "tests" (albeit without asserts), it feels natural to wrap them
    in unit tests.&nbsp; You have an implicit assert: Running the test must
    not throw an Exception.&nbsp; Rewriting it as a unit tests makes
    development a lot easier: You immediate see the results of the four
    test cases, and if an Exception is thrown, the test is marked as
    failed.&nbsp; You also see the stack trace directly in Eclipse, and run
    just one test alone.&nbsp;
    <pre wrap="">
</pre>
    <blockquote cite=""
      type="cite">
      <pre wrap="">Put it into the test suite, please :-)</pre>
    </blockquote>
    <br>
    ... And of course, that is another reason for confirming a bug with
    a test: Once added to the test suite, this problem will never pop up
    again without us noticing.&nbsp; Yes, I was planning on adding it.<br>
    <br>
    Hope this helps!<br>
    <br>
    Best,<br>
    <br>
    - Michael<br>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <center>
        <table>
          <tbody>
            <tr>
              <td align="right"><small><b>Michael Jastram</b></small></td>
              <td align="center"><small><font color="#888">+49 (162) 274
                    83 94</font></small></td>
              <td><small><a href="http://jastram.de">http://jastram.de</a></small></td>
            </tr>
            <tr>
              <td align="right"><small>Gesch&auml;ftsf&uuml;hrer</small></td>
              <td align="center"><small><font color="#888">Formal Mind
                    GmbH</font></small></td>
              <td><small><a href="http://formalmind.com">http://formalmind.com</a></small></td>
            </tr>
            <tr>
              <td align="right"><small>Wissenschaftler</small></td>
              <td align="center"><small><font color="#888">Heinrich
                    Heine Universit&auml;t D&uuml;sseldorf</font></small></td>
              <td><small><a
                    href="http://www.stups.uni-duesseldorf.de/w/Michael_Jastram">http://www.stups.uni-duesseldorf.de</a></small></td>
            </tr>
            <tr>
              <td align="right"><small>Vorsitzender</small></td>
              <td align="center"><small><font color="#888">rheinjug e.V.</font></small></td>
              <td><small><a href="http://rheinjug.de">http://rheinjug.de</a></small></td>
            </tr>
            <tr>
              <td align="right"><small>Project Lead</small></td>
              <td align="center"><small><font color="#888">Eclipse
                    Requirements Modeling Framework</font></small></td>
              <td><small><a href="http://eclipse.org/rmf">http://eclipse.org/rmf</a></small></td>
            </tr>
          </tbody>
        </table>
      </center>
    </div>
  

</font></td></tr></table>]]></content:encoded>
		<pubDate>Thu, 03 May 2012 11:01:23 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00099.html</guid>
		<author>michael@xxxxxxx (Michael Jastram)</author>
	</item>


	<item>
		<title>Re: [rmf-dev] Reading a ReqIF file</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00098.html</link>
		<description>Hi Mark, Yep! Yes. Neither the serialization nor the deserialization should do anything other than ignoring that extensions. But thinking about that, the demand of checking the referential integrity comes into my mind. Think about creating a datatype defin...</description>
		<content:encoded><![CDATA[<pre>Hi Mark, 

&gt; thank you very much for reporting this issue.
&gt; 
&gt; I recently created some more test cases which checked the behavior of the
&gt; tool extensions and figured out the same problem which you pointed out in
&gt; your email: 
&gt; (1) the serialization should not have any dependencies do the
&gt; ProR configuration model 
Yep!

&gt; (2) the serialization should not complain if
&gt; there are third party tool extensions in the model 
Yes. Neither the serialization nor the deserialization should do anything 
other than ignoring that extensions.

But thinking about that, the demand of checking the referential integrity 
comes into my mind. 
Think about creating a datatype definition within the 'core content' including 
an identifier, that will be used as a reference within the tool extensions.
When creating a model useable by ProR programmatically, there should be an 
easy to use component to check the conformance of the model with the 
requirements of ProR. It should complain if references like that above are 
incorrectly set.
Can you give me a pointer if this is still included?

&gt; (3) If an EMF package
&gt; is registered for some tool extensions then the serialization should
&gt; create the appropriate java classes
Ok. Sounds interesting. The 'EMF-book' will be on my desk before the end of 
the week, I hope...

&gt; In order to fix the handling of (third-party) tool extension I need to
&gt; properly make use of the EMF xsd:any mechanism. A bug that requests the
&gt; fix is already available:
&gt; <a  href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=376942">https://bugs.eclipse.org/bugs/show_bug.cgi?id=376942</a> Fixing this bug is
&gt; number one on my list :-)
Thanks.
 
&gt; 
&gt; Concerning your problem reading RMF 0.1.0 files in RMF 0.2.0:
&gt; * you need to update the reqif XML namespace to
&gt;   &quot;<a  href="http://www.omg.org/spec/ReqIF/20110401/reqif.xsd&quot">http://www.omg.org/spec/ReqIF/20110401/reqif.xsd&quot</a>;
&gt;   (the 0.1.0 reqif namespace did not comply to the ReqIF 1.0.1 standard)
&gt; * In RMF 0.1.0 the XML serialization of the tool extensions was using the
&gt; xsi:type concept. Unfortunately, many XML schema validation engines have
&gt; problems with this concept. (or I did not find out how to properly
&gt; configure the parser)
&gt;    Thus theRMF 0.2.0  tool extensions are written in an XML format that
&gt; doesn't require any xsi:type attributes. In order to read existing RMF
&gt; 0.1.0 files you will need to remove the tool extensions from the XML file.
Short after getting into the observed problems, I wrote a class just for this 
purpose :-)

Best regards
	Kay

</pre>]]></content:encoded>
		<pubDate>Wed, 02 May 2012 19:09:09 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00098.html</guid>
		<author>Kay_Muench@xxxxxxx (Kay M&#xFC;nch)</author>
	</item>
	<item>
		<title>Re: [rmf-dev] Reading a ReqIF file</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00097.html</link>
		<description>Hi Michael, Yes. But does unit testing not rely on knowledge of the expected outcome from the SUT to check the real one against? It was just a starting point, a prototype, a 'feasability study' to find out if I'm able to handle a reqif file without ProR. I...</description>
		<content:encoded><![CDATA[<pre>Hi Michael, 

&gt; Generally, this looks correct for using EMF without the Eclipse
&gt; infrastructure.  It is preferrable to write code like that in the form
&gt; of a unit test, though.  
Yes. But does unit testing not rely on knowledge of the expected outcome from 
the SUT to check the real one against?
It was just a starting point, a prototype, a 'feasability study' to find out if 
I'm able to handle a reqif file without ProR. I didn't know what to expect.

&gt; I rewrote your test file as a Unit test
&gt; (including a main() method that launches the unit test).
Put it into the test suite, please :-)
 
&gt; Actually, I am unsure about that myself.  I *thought* the core could
&gt; handle unrecognised ToolExtensions.  I even found the code for this in
&gt; the ReqIF core, but I am unsure why that case is not handled.
&gt; 
&gt; @Mark:  Did you have a chance to look at this?  The problem is that RMF
&gt; stops when no handler for the tool extensions is found, and RMF throws
&gt; the trace below.  I would have expected RMF to recover from this and to
&gt; attach the list of problems related to the tool extensions to the
&gt; ResourceSet.
Thanks, I've already read his comment.

Best regards
	Kay

</pre>]]></content:encoded>
		<pubDate>Wed, 02 May 2012 18:33:15 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00097.html</guid>
		<author>Kay_Muench@xxxxxxx (Kay M&#xFC;nch)</author>
	</item>
	<item>
		<title>Re: [rmf-dev] Reading a ReqIF file</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00096.html</link>
		<description>Hi Kay,thank you very much for reporting this issue.I recently created some more test cases which checked the behavior of the tool extensions and figured out the same problem which you pointed out in your email:(1) the serialization should not have any dep...</description>
		<content:encoded><![CDATA[<table width="100%"><tr><td style="">Hi Kay,<div><br></div><div>thank you very much for reporting this issue.</div><div><br></div><div>I recently created some more test cases which checked the behavior of the tool extensions and figured out the same problem which you pointed out in your email:</div><div>(1) the serialization should not have any dependencies do the ProR configuration model</div><div>(2) the serialization should not complain if there are third party tool extensions in the model</div><div>(3) If an EMF package is registered for some tool extensions then the serialization should create the appropriate java classes</div><div><br></div><div>In order to fix the handling of (third-party) tool extension I need to properly make use of the EMF xsd:any mechanism.&nbsp;</div><div>A bug that requests the fix is already available: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=376942">https://bugs.eclipse.org/bugs/show_bug.cgi?id=376942</a></div><div>Fixing this bug is number one on my list :-)</div><div><br></div><div><br></div><div>Concerning your problem reading RMF 0.1.0 files in RMF 0.2.0:</div><div>* you need to update the reqif XML namespace to</div><div>&nbsp; "<a href="http://www.omg.org/spec/ReqIF/20110401/reqif.xsd">http://www.omg.org/spec/ReqIF/20110401/reqif.xsd</a>"</div><div>&nbsp; (the 0.1.0 reqif namespace did not comply to the ReqIF 1.0.1 standard)</div><div>* In RMF 0.1.0 the XML serialization of the tool extensions was using the xsi:type concept. Unfortunately, many XML schema validation engines have problems with this concept.</div><div>&nbsp; &nbsp;(or I did not find out how to properly configure the parser)</div><div>&nbsp; &nbsp;Thus theRMF 0.2.0 &nbsp;tool extensions are written in an XML format that doesn't require any xsi:type attributes.</div><div>&nbsp; &nbsp;In order to read existing RMF 0.1.0 files you will need to remove the tool extensions from the XML file.</div><div><br></div><div>If you have further questions please let me know</div><div><br></div><div>kind regards</div><div><br></div><div>mark</div><div><br></div><div></div><blockquote type="cite"><div>Hi again,<br><br>trying to realize a small project on top of RMF, I get into some<br>trouble.<br><br>Requirement of the project is to read in a ReqIF file&nbsp;<br>and getting a 'ReqIF' object programmatically by&nbsp;<br>using reqif packages only.<br><br>With that object in memory, I would try to write the spec objects<br>into say a LaTeX-file or Wiki-pages perhaps.<br>This shall be the core for a maven plugin which generates the<br>paper-output or a collaboration-platform automatically.<br>Also this may go into an enhancement for ProR; recently I've<br>got Clayberg/Rubel's 'eclipse Plug-ins'...<br><br>My current problem is to not knowing, if I'm reading a ReqIF file in<br>the correct way, so please take a look at the attached code example.<br><br>What makes me astonished is that it seems that I'm not able to read a<br>file which was absolutely valid in ProR 0.1.0, and why do I have<br>to 'register' EPackages related to - I think - ProR to read a file<br>with 0.2.0-tool-extensions?<br><br>I think it must be possible to read ReqIF files with the reqif packages<br>ignoring any tool-extensions. Think about the 0.1.0 file<br>as written by another tool from another vendor...<br><br>Best regards<br><span class="Apple-tab-span" style="white-space: pre; ">	</span>Kay</div><div><br></div></blockquote><div><br></div><div><br></div><div><br></div><div><div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div><div><div><div><div>--</div><div>Mark Br&#xF6;rkens</div><div>Softwarearchitekt, Projekt- und Produktmanager</div><div><br></div><div><div>Telefon: &nbsp;+49 30 69 535 878</div><div>Telefax: &nbsp;+49 30 62 908 067</div></div><div>Mobil: &nbsp; &nbsp; +49 151 61301259 (bevorzugt)</div><div><br></div><div><a href="http://www.itemis.de/">http://www.itemis.de</a></div><div><a href="mailto:mark.broerkens@xxxxxxxxx">mark.broerkens@xxxxxxxxx</a></div><div><a href="https://www.xing.com/profile/mark_broerkens">https://www.xing.com/profile/mark_broerkens</a></div><div><a href="http://twitter.com/MarkBroerkens">http://twitter.com/MarkBroerkens</a></div><div><br></div><div>itemis AG</div><div>Niederlassung Berlin</div><div>Ohlauer Stra&#xDF;e 43</div><div>10999 Berlin</div><div><br></div><div>Rechtlicher Hinweis:</div><div>Amtsgericht Dortmund, HRB 20621</div><div>Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus</div><div>Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus</div></div></div></div></div></div><div><br></div></div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br></div></td></tr></table>]]></content:encoded>
		<pubDate>Wed, 02 May 2012 14:19:34 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00096.html</guid>
		<author>mark.broerkens@xxxxxxx (Mark Br&#xF6;rkens)</author>
	</item>


	<item>
		<title>Re: [rmf-dev] Reading a ReqIF file</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00095.html</link>
		<description> Hello Kay, I just had a look at your code - here are my comments: Generally, this looks correct for using EMF without the Eclipse infrastructure.  It is preferrable to write code like that in the form of a unit test, though.  I rewrote your test file as a...</description>
		<content:encoded><![CDATA[<table width="100%"><tr><td bgcolor="#FFFFFF" style="background-color: #FFFFFF; color: #000000; "><font color="#000000">
  
  
    Hello Kay,<br>
    <br>
    I just had a look at your code - here are my comments:<br>
    <br>
    <blockquote cite=""
      type="cite">
      <pre wrap="">My current problem is to not knowing, if I'm reading a ReqIF file in
the correct way, so please take a look at the attached code example.</pre>
    </blockquote>
    <br>
    Generally, this looks correct for using EMF without the Eclipse
    infrastructure.&nbsp; It is preferrable to write code like that in the
    form of a unit test, though.&nbsp; I rewrote your test file as a Unit
    test (including a main() method that launches the unit test).<br>
    <br>
    <blockquote cite=""
      type="cite">
      <pre wrap="">What makes me astonished is that it seems that I'm not able to read a
file which was absolutely valid in ProR 0.1.0, and why do I have
to 'register' EPackages related to - I think - ProR to read a file
with 0.2.0-tool-extensions?</pre>
    </blockquote>
    <br>
    Actually, I am unsure about that myself.&nbsp; I *thought* the core could
    handle unrecognised ToolExtensions.&nbsp; I even found the code for this
    in the ReqIF core, but I am unsure why that case is not handled.<br>
    <br>
    @Mark:&nbsp; Did you have a chance to look at this?&nbsp; The problem is that
    RMF stops when no handler for the tool extensions is found, and RMF
    throws the trace below.&nbsp; I would have expected RMF to recover from
    this and to attach the list of problems related to the tool
    extensions to the ResourceSet.<br>
    <br>
    org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Package
    with uri '<a class="moz-txt-link-freetext" href="http://pror.org/presentation/configuration">http://pror.org/presentation/configuration</a>' not found.
    (<a class="moz-txt-link-freetext" href="file:///home/jastram/rmf/org.eclipse.rmf/reqif-test/src/test/resources/test-1.reqif">file:///home/jastram/rmf/org.eclipse.rmf/reqif-test/src/test/resources/test-1.reqif</a>,
    392, 119)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLLoadImpl.java:83)<br>
    &nbsp;&nbsp;&nbsp; at
    org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:191)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:242)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1511)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1290)<br>
    &nbsp;&nbsp;&nbsp; at reqif.reqif_writer.App2.readPlease(App2.java:91)<br>
    &nbsp;&nbsp;&nbsp; at reqif.reqif_writer.App2.testValid0_1_0(App2.java:62)<br>
    &nbsp;&nbsp;&nbsp; at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>
    &nbsp;&nbsp;&nbsp; at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)<br>
    &nbsp;&nbsp;&nbsp; at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)<br>
    &nbsp;&nbsp;&nbsp; at java.lang.reflect.Method.invoke(Method.java:592)<br>
    &nbsp;&nbsp;&nbsp; at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)<br>
    &nbsp;&nbsp;&nbsp; at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)<br>
    &nbsp;&nbsp;&nbsp; at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)<br>
    &nbsp;&nbsp;&nbsp; at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)<br>
    &nbsp;&nbsp;&nbsp; at
org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)<br>
    &nbsp;&nbsp;&nbsp; at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)<br>
    &nbsp;&nbsp;&nbsp; at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)<br>
    &nbsp;&nbsp;&nbsp; at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)<br>
    &nbsp;&nbsp;&nbsp; at
    org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)<br>
    &nbsp;&nbsp;&nbsp; at
    org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)<br>
    &nbsp;&nbsp;&nbsp; at
    org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)<br>
    &nbsp;&nbsp;&nbsp; at
    org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)<br>
    &nbsp;&nbsp;&nbsp; at org.junit.runners.ParentRunner.run(ParentRunner.java:236)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)<br>
    Caused by: org.eclipse.emf.ecore.xmi.PackageNotFoundException:
    Package with uri '<a class="moz-txt-link-freetext" href="http://pror.org/presentation/configuration">http://pror.org/presentation/configuration</a>' not
    found.
    (<a class="moz-txt-link-freetext" href="file:///home/jastram/rmf/org.eclipse.rmf/reqif-test/src/test/resources/test-1.reqif">file:///home/jastram/rmf/org.eclipse.rmf/reqif-test/src/test/resources/test-1.reqif</a>,
    392, 119)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.getPackageForURI(XMLHandler.java:2591)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.getFactoryForPrefix(XMLHandler.java:2422)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.rmf.internal.serialization.ReqIFXMLSAXHandler.handleObject(ReqIFXMLSAXHandler.java:117)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.rmf.internal.serialization.ReqIFXMLSAXHandler.processElement(ReqIFXMLSAXHandler.java:82)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:1001)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:712)<br>
    &nbsp;&nbsp;&nbsp; at
org.eclipse.rmf.internal.serialization.ReqIFXMLSAXHandler.startElement(ReqIFXMLSAXHandler.java:59)<br>
    &nbsp;&nbsp;&nbsp; at
    org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
    Source)<br>
    &nbsp;&nbsp;&nbsp; at
    org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
    Source)<br>
    &nbsp;&nbsp;&nbsp; at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
    Source)<br>
    &nbsp;&nbsp;&nbsp; at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
    Source)<br>
    &nbsp;&nbsp;&nbsp; at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)<br>
    &nbsp;&nbsp;&nbsp; at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)<br>
    &nbsp;&nbsp;&nbsp; at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)<br>
    &nbsp;&nbsp;&nbsp; at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
    Source)<br>
    &nbsp;&nbsp;&nbsp; at
    org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
    Source)<br>
    &nbsp;&nbsp;&nbsp; at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)<br>
    &nbsp;&nbsp;&nbsp; at
    org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:181)<br>
    &nbsp;&nbsp;&nbsp; ... 28 more<br>
    <br>
    <br>
    Best,<br>
    <br>
    - Michael<br>
    <br>
    <blockquote cite=""
      type="cite">
      <pre wrap="">

I think it must be possible to read ReqIF files with the reqif packages
ignoring any tool-extensions. Think about the 0.1.0 file
as written by another tool from another vendor...

Best regards
	Kay
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
rmf-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rmf-dev@xxxxxxxxxxx">rmf-dev@xxxxxxxxxxx</a>
<a class="moz-txt-link-freetext" href="http://dev.eclipse.org/mailman/listinfo/rmf-dev">http://dev.eclipse.org/mailman/listinfo/rmf-dev</a>
</pre>
    </blockquote>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <center>
        <table>
          <tbody>
            <tr>
              <td align="right"><small><b>Michael Jastram</b></small></td>
              <td align="center"><small><font color="#888">+49 (162) 274
                    83 94</font></small></td>
              <td><small><a href="http://jastram.de">http://jastram.de</a></small></td>
            </tr>
            <tr>
              <td align="right"><small>Gesch&auml;ftsf&uuml;hrer</small></td>
              <td align="center"><small><font color="#888">Formal Mind
                    GmbH</font></small></td>
              <td><small><a href="http://formalmind.com">http://formalmind.com</a></small></td>
            </tr>
            <tr>
              <td align="right"><small>Wissenschaftler</small></td>
              <td align="center"><small><font color="#888">Heinrich
                    Heine Universit&auml;t D&uuml;sseldorf</font></small></td>
              <td><small><a
                    href="http://www.stups.uni-duesseldorf.de/w/Michael_Jastram">http://www.stups.uni-duesseldorf.de</a></small></td>
            </tr>
            <tr>
              <td align="right"><small>Vorsitzender</small></td>
              <td align="center"><small><font color="#888">rheinjug e.V.</font></small></td>
              <td><small><a href="http://rheinjug.de">http://rheinjug.de</a></small></td>
            </tr>
            <tr>
              <td align="right"><small>Project Lead</small></td>
              <td align="center"><small><font color="#888">Eclipse
                    Requirements Modeling Framework</font></small></td>
              <td><small><a href="http://eclipse.org/rmf">http://eclipse.org/rmf</a></small></td>
            </tr>
          </tbody>
        </table>
      </center>
    </div>
  

</font></td></tr></table><pre>package reqif.reqif_writer;

import java.io.IOException;
import java.util.UUID;

import org.eclipse.emf.common.util.EList;
import org.eclipse.emf.common.util.URI;
import org.eclipse.emf.ecore.EObject;
import org.eclipse.emf.ecore.EPackage;
import org.eclipse.emf.ecore.xmi.XMLResource;
import org.eclipse.emf.ecore.xml.namespace.XMLNamespacePackage;
import org.eclipse.rmf.reqif10.ReqIF;
import org.eclipse.rmf.reqif10.ReqIF10Package;
import org.eclipse.rmf.reqif10.datatypes.DatatypesPackage;
import org.eclipse.rmf.reqif10.xhtml.XhtmlPackage;
import org.eclipse.rmf.serialization.ReqIFResourceFactoryImpl;
import org.eclipse.rmf.serialization.ReqIFResourceSetImpl;
import org.junit.Test;
import org.junit.runner.JUnitCore;
import org.junit.runner.Result;
import org.junit.runner.notification.Failure;


public class App2 {
	
	public static final String VALID_0_1_0 = &quot;src/test/resources/test-1.reqif&quot;;
	public static final String VALID_0_2_0 = &quot;src/test/resources/TC3000_E000_S10_Reference_20120412_2336_broerkens.reqif&quot;;
	public static final String VALID_REQIF = &quot;src/test/resources/TC1300_without_namespaceprefix.reqif&quot;;
	public static final String TARGET_NAME_BASE = &quot;work/test-dest-&quot;;

	/**
	 * Allows running unit tests as Java application
	 * @param args
	 */
	public static void main(String[] args) {
		Result result = JUnitCore.runClasses(App2.class);
		if (!result.wasSuccessful()) {
			System.out.println(&quot;\nFAILURES: \n&quot;);
			for (Failure failure: result.getFailures()) {
				System.out.println(failure);
				
			}
		}
	}

	/** Returns a unique test file name */
	private String generateTargetName() {
		return TARGET_NAME_BASE + UUID.randomUUID() + &quot;.reqif&quot;;
	}

	@Test
	public void testValidReqif() throws Exception {
		registerEPackageStd();
		ReqIF reqif = readPlease(VALID_REQIF);
		justWritePlease(generateTargetName(), reqif);

	}

	@Test
	public void testValid0_1_0() throws Exception {
		registerEPackageStd();
		ReqIF reqif = readPlease(VALID_0_1_0);
		justWritePlease(generateTargetName(), reqif);

	}

	@Test
	public void testValid0_2_0() throws Exception {
		registerEPackageStd();
		ReqIF reqif = readPlease(VALID_0_2_0);
		justWritePlease(generateTargetName(), reqif);

	}

	private static void registerEPackageStd() {
		EPackage.Registry.INSTANCE.clear();
		EPackage.Registry.INSTANCE.put(ReqIF10Package.eNS_URI,
				ReqIF10Package.eINSTANCE);
		EPackage.Registry.INSTANCE.put(XhtmlPackage.eNS_URI,
				XhtmlPackage.eINSTANCE);
		EPackage.Registry.INSTANCE.put(DatatypesPackage.eNS_URI,
				DatatypesPackage.eINSTANCE);
		EPackage.Registry.INSTANCE.put(XMLNamespacePackage.eNS_URI,
				XMLNamespacePackage.eINSTANCE);
	}

	private static ReqIF readPlease(final String fileName) throws IOException {
		ReqIFResourceSetImpl resourceSet = aResourceSetPlease();
		URI uri = URI.createURI(fileName, true);
		XMLResource resource = (XMLResource) resourceSet.createResource(uri);
		resource.load(null);

		EList&lt;EObject&gt; rootObjects = resource.getContents();

		if (rootObjects.isEmpty())
			throw new RuntimeException(&quot;Oops! Empty!&quot;);

		ReqIF reqif = (ReqIF) rootObjects.get(0);

		return reqif;
	}

	private static ReqIFResourceSetImpl aResourceSetPlease() {

		ReqIFResourceSetImpl resourceSet = new ReqIFResourceSetImpl();
		resourceSet.getResourceFactoryRegistry().getExtensionToFactoryMap()
				.put(&quot;reqif&quot;, new ReqIFResourceFactoryImpl());

		return resourceSet;
	}

	private static void justWritePlease(final String destFileName, ReqIF reqif)
		throws IOException {
		System.out.println(&quot;Writing: &quot; + destFileName);

	ReqIFResourceSetImpl resourceSet = aResourceSetPlease();
	URI uri = URI.createURI(destFileName, true);
	XMLResource resource = (XMLResource) resourceSet.createResource(uri);
	resource.getContents().add(reqif);
	resource.save(null);
}
}
</pre>]]></content:encoded>
		<pubDate>Tue, 01 May 2012 19:19:46 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00095.html</guid>
		<author>michael@xxxxxxx (Michael Jastram)</author>
	</item>


	<item>
		<title>[rmf-dev] Reading a ReqIF file</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00094.html</link>
		<description>Hi again, trying to realize a small project on top of RMF, I get into some trouble. Requirement of the project is to read in a ReqIF file and getting a 'ReqIF' object programmatically by using reqif packages only. With that object in memory, I would try to...</description>
		<content:encoded><![CDATA[<pre>Hi again,

trying to realize a small project on top of RMF, I get into some
trouble.

Requirement of the project is to read in a ReqIF file 
and getting a 'ReqIF' object programmatically by 
using reqif packages only.

With that object in memory, I would try to write the spec objects
into say a LaTeX-file or Wiki-pages perhaps.
This shall be the core for a maven plugin which generates the
paper-output or a collaboration-platform automatically.
Also this may go into an enhancement for ProR; recently I've
got Clayberg/Rubel's 'eclipse Plug-ins'...

My current problem is to not knowing, if I'm reading a ReqIF file in
the correct way, so please take a look at the attached code example.

What makes me astonished is that it seems that I'm not able to read a
file which was absolutely valid in ProR 0.1.0, and why do I have
to 'register' EPackages related to - I think - ProR to read a file
with 0.2.0-tool-extensions?

I think it must be possible to read ReqIF files with the reqif packages
ignoring any tool-extensions. Think about the 0.1.0 file
as written by another tool from another vendor...

Best regards
	Kay
</pre><p><strong>Attachment:
<a href="zipKhui9OyqLS.zip" ><tt>reqif-test.zip</tt></a></strong><br>
<em>Description:</em> Zip archive</p>
]]></content:encoded>
		<pubDate>Sun, 29 Apr 2012 16:21:53 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00094.html</guid>
		<author>Kay_Muench@xxxxxxx (Kay M&#xFC;nch)</author>
	</item>


	<item>
		<title>Re: [rmf-dev] RMF SDK update site (source included)</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00093.html</link>
		<description>Hi Mark,or just point to the last successful update site build: https://hudson.eclipse.org/hudson/job/rmf-nightly/lastSuccessfulBuild/artifact/update-site/ Best regards,Lukas2012/4/28 Mark Br&amp;#xF6;rkens &amp;lt;mark.broerkens@xxxxxxxxx&amp;gt; </description>
		<content:encoded><![CDATA[Hi Mark,<br><br>or just point to the last successful update site build: <br><br><a href="https://hudson.eclipse.org/hudson/job/rmf-nightly/lastSuccessfulBuild/artifact/update-site/">https://hudson.eclipse.org/hudson/job/rmf-nightly/lastSuccessfulBuild/artifact/update-site/</a><br>
<br>Best regards,<br>Lukas<br><br><div class="gmail_quote">2012/4/28 Mark Br&#xF6;rkens <span dir="ltr">&lt;<a href="mailto:mark.broerkens@xxxxxxxxx" target="_blank">mark.broerkens@xxxxxxxxx</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<div><div><div><div><div><div><div>Hi RMF developers,</div></div></div></div></div></div><div><br></div></div><div>for your information:&#xA0;</div><div>If you are building applications on top of RMF and you were missing source code, you can now point your target platform to the update site on hudson.</div>
</div></span></div></span></div></span></span></div><div>Build 185 contains the sources as well.</div><div><br></div><div>update-site URL:</div><div><a href="https://hudson.eclipse.org/hudson/job/rmf-nightly/185/artifact/update-site/" target="_blank">https://hudson.eclipse.org/hudson/job/rmf-nightly/185/artifact/update-site/</a></div>
<div><br></div><div>regards,</div><div><br></div><div>Mark</div>
<br></div><br>_______________________________________________<br>
rmf-dev mailing list<br>
<a href="mailto:rmf-dev@xxxxxxxxxxx">rmf-dev@xxxxxxxxxxx</a><br>
<a href="http://dev.eclipse.org/mailman/listinfo/rmf-dev" target="_blank">http://dev.eclipse.org/mailman/listinfo/rmf-dev</a><br>
<br></blockquote></div><br>
]]></content:encoded>
		<pubDate>Sat, 28 Apr 2012 16:12:58 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00093.html</guid>
		<author>lukas.ladenberger@xxxxxxx (Lukas Ladenberger)</author>
	</item>
	<item>
		<title>[rmf-dev] RMF SDK update site (source included)</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00092.html</link>
		<description>Hi RMF developers,for your information: If you are building applications on top of RMF and you were missing source code, you can now point your target platform to the update site on hudson.Build 185 contains the sources as well.update-site URL:https://huds...</description>
		<content:encoded><![CDATA[<table width="100%"><tr><td style=""><div><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div><div><div><div><div>Hi RMF developers,</div></div></div></div></div></div><div><br></div></div><div>for your information:&nbsp;</div><div>If you are building applications on top of RMF and you were missing source code, you can now point your target platform to the update site on hudson.</div></div></span></div></span></div></span></span></div><div>Build 185 contains the sources as well.</div><div><br></div><div>update-site URL:</div><div><a href="https://hudson.eclipse.org/hudson/job/rmf-nightly/185/artifact/update-site/">https://hudson.eclipse.org/hudson/job/rmf-nightly/185/artifact/update-site/</a></div><div><br></div><div>regards,</div><div><br></div><div>Mark</div>
<br></td></tr></table>]]></content:encoded>
		<pubDate>Sat, 28 Apr 2012 15:01:15 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00092.html</guid>
		<author>mark.broerkens@xxxxxxx (Mark Br&#xF6;rkens)</author>
	</item>


	<item>
		<title>[rmf-dev] Welcome Ingo Weigelt as a new modeling.mdt.rmf Committer</title>
		<link>http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00091.html</link>
		<description>modeling.mdt.rmf Committers, This automatically generated message marks the completion of all the legal paperwork and webmaster provisioning for Ingo Weigelt. Ingo Weigelt is a new full Committer on the modeling.mdt.rmf project. Welcome! </description>
		<content:encoded><![CDATA[<pre>modeling.mdt.rmf Committers,
This automatically generated message marks the completion of all the legal
paperwork and webmaster provisioning for Ingo Weigelt. Ingo Weigelt is a
new full Committer on the modeling.mdt.rmf project.

Welcome!

</pre>]]></content:encoded>
		<pubDate>Tue, 24 Apr 2012 13:38:01 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/rmf-dev/msg00091.html</guid>
		<author>michael@xxxxxxx (portal on behalf of Michael Jastram)</author>
	</item>

 
	</channel>
	</rss>
<!-- MHonArc v2.6.10 -->

