|
Re: XML output merging [message #30909 is a reply to message #30803] |
Tue, 14 August 2007 13:08 |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Francis,
It would seem that for the common thing, you'd have module A as the
input and that would invoke that once for the module, while for the
component-level thing, you'd have each component as the input to the
template and do it once per component...
Francis wrote:
> Given the following example structure of a model:
> <module name="A">
> <component name="1"/>
> <component name="2"/>
> </module>
> I should be able to generate the components individually
> (transformations are invoked separately). But I also need to generate
> a common XML file. For example:
> 1. Generate component 1.
> 2. The output of the common XML file is:
> <root>
> <componentlist module="A">
> <app>1</app>
> </componentlist>
> </root>
> 3. Generate component 2.
> 4. The expected output of the common XML file is:
> <root>
> <componentlist module="A">
> <app>1</app>
> <app>2</app>
> </componentlist>
> </root>
>
> Question: How do I achieve this in JET? Is it possible to do xml
> merging? I'm using version 0.7.1.
>
> Thanks,
> Francis
>
|
|
|
Re: XML output merging [message #30979 is a reply to message #30909] |
Tue, 14 August 2007 15:01 |
Francis Gavino Messages: 57 Registered: July 2009 |
Member |
|
|
Ed,
Thanks for the reply. If I understood it correctly, the solution below
works when the module-level model is available in the transformation, or
when all components are available. But in the case where only the specific
component is available in the model passed to the template as input, can
that entry be merged if the common xml file is already existing?
BR,
Francis
Ed Merks wrote:
> Francis,
> It would seem that for the common thing, you'd have module A as the
> input and that would invoke that once for the module, while for the
> component-level thing, you'd have each component as the input to the
> template and do it once per component...
> Francis wrote:
>> Given the following example structure of a model:
>> <module name="A">
>> <component name="1"/>
>> <component name="2"/>
>> </module>
>> I should be able to generate the components individually
>> (transformations are invoked separately). But I also need to generate
>> a common XML file. For example:
>> 1. Generate component 1.
>> 2. The output of the common XML file is:
>> <root>
>> <componentlist module="A">
>> <app>1</app>
>> </componentlist>
>> </root>
>> 3. Generate component 2.
>> 4. The expected output of the common XML file is:
>> <root>
>> <componentlist module="A">
>> <app>1</app>
>> <app>2</app>
>> </componentlist>
>> </root>
>>
>> Question: How do I achieve this in JET? Is it possible to do xml
>> merging? I'm using version 0.7.1.
>>
>> Thanks,
>> Francis
>>
|
|
|
Re: XML output merging [message #31052 is a reply to message #30979] |
Tue, 14 August 2007 17:13 |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Francis,
Nothing generic is going to be smart enough to know how to merge the
specific results properly.
Francis wrote:
> Ed,
>
> Thanks for the reply. If I understood it correctly, the solution below
> works when the module-level model is available in the transformation,
> or when all components are available. But in the case where only the
> specific component is available in the model passed to the template as
> input, can that entry be merged if the common xml file is already
> existing?
>
> BR,
> Francis
>
> Ed Merks wrote:
>
>> Francis,
>
>> It would seem that for the common thing, you'd have module A as the
>> input and that would invoke that once for the module, while for the
>> component-level thing, you'd have each component as the input to the
>> template and do it once per component...
>
>
>> Francis wrote:
>>> Given the following example structure of a model:
>>> <module name="A">
>>> <component name="1"/>
>>> <component name="2"/>
>>> </module>
>>> I should be able to generate the components individually
>>> (transformations are invoked separately). But I also need to
>>> generate a common XML file. For example:
>>> 1. Generate component 1.
>>> 2. The output of the common XML file is:
>>> <root>
>>> <componentlist module="A">
>>> <app>1</app>
>>> </componentlist>
>>> </root>
>>> 3. Generate component 2.
>>> 4. The expected output of the common XML file is:
>>> <root>
>>> <componentlist module="A">
>>> <app>1</app>
>>> <app>2</app>
>>> </componentlist>
>>> </root>
>>>
>>> Question: How do I achieve this in JET? Is it possible to do xml
>>> merging? I'm using version 0.7.1.
>>>
>>> Thanks,
>>> Francis
>>>
>
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02897 seconds