|
Re: RMF Standalone [message #997320 is a reply to message #997246] |
Sat, 05 January 2013 19:26 |
|
Hi Peter,
What you did is not enough, as it will invoke the default persister (which writes xmi, as you have noticed). We have a few unit tests that write .reqif and don't even need to run as Eclipse Plug-In-Tests. If you look at them, you should be able to figure it out fairly quickly.
Specifically, have a look at the following, which is a very simple example that does exactly what you want (I believe):
org.eclipse.rmf.reqif10.tests/src/org/eclipse/rmf/reqif10/tests/uc000/tc1000
Hope this helps!
- Michael
|
|
|
|
Re: RMF Standalone [message #997448 is a reply to message #997348] |
Mon, 07 January 2013 14:51 |
Peter Pedron Messages: 3 Registered: January 2013 |
Junior Member |
|
|
OK some findings I found out during testing:
In order to serialize a ReqIF model in a standalone app, you have to use the ReqIFResourceSetImpl. That is NOT enough though: you have to register as well the appropriate ResourceFactory to the ResourceSet:
ResourceSet set = new ReqIFResourceSetImpl();
set.getResourceFactoryRegistry().getExtensionToFactoryMap().put("reqif", new ReqIFResourceFactoryImpl());
Using an eclipse-plugin project environment, everything is well initilialized and works transparently if the plugin depends on the pror.editor plugin.
There you can use the simple ResourcSetImpl without any factory registrations.
It would be interesting to know what the pror.editor does in order to enable this transparent use of the resourceset, I haven't figured it out yet...
Cheers,
Peter
[Updated on: Tue, 08 January 2013 13:38] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.04206 seconds