| 1.0.1a XML import/export [message #22789] |
Wed, 08 November 2006 07:17  |
Eclipse User |
|
|
|
Hi
is there any information to be found concerning the XML import/export
functionality which is add to the 1.0.1 release ?
thanks
Danny
|
|
|
|
|
|
|
|
|
| Re: 1.0.1a XML import/export [message #23481 is a reply to message #23295] |
Mon, 13 November 2006 01:37  |
| Eclipse User |
|
|
|
ok, thanks for the answer
Looks like this feature will not be of help to me.
My need is frequently updating existing content in existing packages
And that, if at all possible, without human intervention.
Shilpa Toraskar wrote:
> That's the indended behaviour assuming you didn't create new
> MethodPackage. From your reply, it looks like you created new element
> into existing MethodPackage. In that case, It will get rid of all
> existing content elements under that package. But if you have new
> package, and new elements underneath, and if you use MERGE option it
> should get merged.
> After doing that, you may want to use copy/move UI operation to move
> elements under appropriate package you want. I know it's not seamless.
> There are APIs available to do copy/move but I must say unfortunately,
> it's not intuitive. You really have to understand underline structure to
> use that.
> --
> Shilpa
>
|
|
|
| Re: 1.0.1a XML import/export [message #567875 is a reply to message #22789] |
Wed, 08 November 2006 21:29 |
| Eclipse User |
|
|
|
Sorry, we have not written anything up on it so far. You can ask here and
we can help you through it.
--
Thanks and best regards,
Peter Haumer.
____________________________________________________________ __
PETER HAUMER
IBM | Eclipse Process Framework Committer
____________________________________________________________ __
"danny" <danny.foncke@smals-mvm.be> wrote in message
news:eishst$l4e$1@utils.eclipse.org...
> Hi
>
> is there any information to be found concerning the XML import/export
> functionality which is add to the 1.0.1 release ?
>
> thanks
>
> Danny
|
|
|
| Re: 1.0.1a XML import/export [message #567905 is a reply to message #22921] |
Thu, 09 November 2006 03:27 |
| Eclipse User |
|
|
|
Peter Haumer wrote:
> Sorry, we have not written anything up on it so far. You can ask here and
> we can help you through it.
>
OK, as a first: what do I want (need) to do with it, let me explain briefly:
We use another content tool, of our own making, and 'some' content needs
to find its way into EPF.
And this on a regular basis (like every night)
And if possible automatically (we don't we to 're-type' the content in
EPF (and certainly not at night) )
So our tool exports every day new and/or changed content and EPF imports it.
However, the content is very fine grained. I mean the 'tool' can for
example export a 'role' or a 'concept' etc... which needs to be inserted
into an existing EPF method library.
I thought the XML import might be of assistance
Or is there another way ?
thanks
Danny
|
|
|
|
|
| Re: 1.0.1a XML import/export [message #568083 is a reply to message #22921] |
Fri, 10 November 2006 03:43 |
| Eclipse User |
|
|
|
First tests :
-> I have a very small library consisting of
1 concept
2 guidelines linked to the concept
1 checklist linked to the concept
1 custom category having assigned the above concept to it
1 configuration
-> I export as XML : works
-> I edit the exported XML to end up with 1 ContentElement
In that element I change the name and I put the id to "" (in
<ContentElement> and in <Presentation>)
In the XML I also leave the :
<uma:MethodLibrary ....>
<MethodPlugin ......>
<MethodPackage .......>
in which the new ContentElement finds a place
-> I import the newly formed XML - with MERGE option checked
* no reported problems
* the new element is imported, id's are generated
* ALL THE REST IS GONE, with exception of the configuration, in which an
error is reported about a missing resource (which at that point is
correct of course)
Before filing any bugzilla issues I wanted to verify if this was the
intended use of XML import ?
Peter Haumer wrote:
> Sorry, we have not written anything up on it so far. You can ask here and
> we can help you through it.
>
|
|
|
| Re: 1.0.1a XML import/export [message #568149 is a reply to message #23209] |
Fri, 10 November 2006 12:57 |
| Eclipse User |
|
|
|
That's the indended behaviour assuming you didn't create new
MethodPackage. From your reply, it looks like you created new element into
existing MethodPackage. In that case, It will get rid of all existing
content elements under that package. But if you have new package, and new
elements underneath, and if you use MERGE option it should get merged.
After doing that, you may want to use copy/move UI operation to move
elements under appropriate package you want. I know it's not seamless.
There are APIs available to do copy/move but I must say unfortunately,
it's not intuitive. You really have to understand underline structure to
use that.
--
Shilpa
|
|
|
| Re: 1.0.1a XML import/export [message #568360 is a reply to message #23295] |
Mon, 13 November 2006 01:37 |
| Eclipse User |
|
|
|
ok, thanks for the answer
Looks like this feature will not be of help to me.
My need is frequently updating existing content in existing packages
And that, if at all possible, without human intervention.
Shilpa Toraskar wrote:
> That's the indended behaviour assuming you didn't create new
> MethodPackage. From your reply, it looks like you created new element
> into existing MethodPackage. In that case, It will get rid of all
> existing content elements under that package. But if you have new
> package, and new elements underneath, and if you use MERGE option it
> should get merged.
> After doing that, you may want to use copy/move UI operation to move
> elements under appropriate package you want. I know it's not seamless.
> There are APIs available to do copy/move but I must say unfortunately,
> it's not intuitive. You really have to understand underline structure to
> use that.
> --
> Shilpa
>
|
|
|
Powered by
FUDForum. Page generated in 0.09502 seconds
Home