Hi again :),
Can you try to put <richText> tag alone in its paragraph (without text before 
and after). I think there is this kind of limitation

Your template shall like :
<gendoc>
[for (sr:SecurityFunctionalRequirement | self.requirement)]
                Requirement ID : [sr.requirementId/]
                Requirement Text : // line break
<richText>[sr.requirementText/]</richText>
                [for (ts:TextSequence | sr.textSequence)]
                        Elem: [ts.textSequenceType/]
[/for]          
        [/for]
</gendoc>

Regards
Tristan FAURE


-----Message d'origine-----
De : [email protected] 
[mailto:[email protected]] De la part de Topcased user 
list where issues are discussed
Envoyé : lundi 7 février 2011 16:31
À : [email protected]
Objet : Re: [Topcased-users] Gendoc 2 and TPC 4.2.1 - richtext support not 
working

Yes I created an ecore metamodel...but, as you said, the metamodel
APIs were not accessible to the gendoc2 project...
but you gave me an idea:

This is what I tried:
1. I created a metamodel with EMF and generated the corresponding editor.
2. I ran the editor as Eclipse Application
3. I created a simple project
4. Using "EMF Example EMF Model Creation Wizard" I created a new model
instance (i.e. requirements.requirementspackage) associated to my
metamodel
5. I created a Gendoc2 template document referencing that model

Now, when I generate the document I don't get the load error anymore,
but when I try opening the generated document, MS Word 2007 says that
there is an error in the generated docx (at some line of
document.xml).

Here is the gendoc script embedded in the template document:

<gendoc>
[for (sr:SecurityFunctionalRequirement | self.requirement)]
                Requirement ID : [sr.requirementId/]
                Requirement Text : <richText>[sr.requirementText/]</richText>
                [for (ts:TextSequence | sr.textSequence)]
                        Elem: [ts.textSequenceType/]
[/for]          
        [/for]
</gendoc>


Note that, if I remove the <richText> and </richText> tags, the
problem doesn't arise anymore.

Regard,
Luca.



2011/2/7 Topcased user list where issues are discussed
<[email protected]>:
> Are you using your metamodel ? I don't know the requirementspackage 
> extension. Are you sure the API of this metamodel is available from your 
> platform ?
>
> Tristan
>
> -----Message d'origine-----
> De : [email protected] 
> [mailto:[email protected]] De la part de Topcased 
> user list where issues are discussed
> Envoyé : lundi 7 février 2011 12:06
> À : [email protected]
> Objet : Re: [Topcased-users] Gendoc 2 and TPC 4.2.1 - richtext support not 
> working
>
> Dear Tristan, here's the error message I get during document generation:
>
> See details.
>  The execution of a script failed: The model Model can not be loaded
> from URL: 
> "file:/C:/DevelopmentTools/workspace_tpc421/org.eclipse.acceleo.module.requirements/userModels/requirements.requirementspackage"
> can not be loaded
>
> I can confirm the model is exactly located on that path.
>
> For sake of completeness, these are the configuration instructions I
> put in the template document:
>
> <config>
> <param key='workspace' value='C:\DevelopmentTools\workspace_tpc421' />
> <param key='project'
> value='${workspace}\org.eclipse.acceleo.module.requirements' />
> <param key='model'
> value='${project}\userModels\requirements.requirementspackage' />
> <output path='${project}/Generated/generated_doc.docx' />
> </config>
>
> <context model='${model}' importedBundles='topcased' searchMetamodels='true'/>
>
> Ciao,
> Luca DI COSMO
>
>
>
>
> 2011/2/7 Topcased user list where issues are discussed
> <[email protected]>:
>> Hum this sounds bad,
>>
>> Can you copy the complete message "from URL: "..." can not be loaded"."
>> Maybe it is present in the error log
>>
>>
>> Regards
>> Tristan FAURE
>>
>> -----Message d'origine-----
>> De : [email protected] 
>> [mailto:[email protected]] De la part de Topcased 
>> user list where issues are discussed
>> Envoyé : lundi 7 février 2011 11:38
>> À : [email protected]
>> Objet : Re: [Topcased-users] Gendoc 2 and TPC 4.2.1 - richtext support not 
>> working
>>
>> Hi Tristan,
>> thanks for the help.
>>
>> Actually we simply tried to render:
>>
>> <strong>hello folks</strong>
>>
>> In the UML model this formatted text has been stored by the
>> documentation editor as an annotation containing:
>>
>> &lt;strong>hello folks&lt;/strong>
>>
>>
>> By the way, if we don't include html tags in the documentation, the
>> problem arise the same.
>>
>> Thanks in advance,
>> Luca DI COSMO
>>
>>
>>
>>
>>
>> 2011/2/7 Topcased user list where issues are discussed
>> <[email protected]>:
>>> Hi,
>>> It seems some tags in your rich text context are not recognized.
>>> What kind of tags do you use ? (bold, italic ... ?)
>>>
>>> We recently had some problems with richText tag if there is text between 
>>> rich text content and xml content. Try to copy/paste(without formatting, or 
>>> using notepad), your rich text declaration.
>>>
>>> Regards
>>>
>>> Tristan FAURE
>>>
>>> -----Message d'origine-----
>>> De : [email protected] 
>>> [mailto:[email protected]] De la part de Topcased 
>>> user list where issues are discussed
>>> Envoyé : dimanche 6 février 2011 09:46
>>> À : [email protected]
>>> Objet : [Topcased-users] Gendoc 2 and TPC 4.2.1 - richtext support not 
>>> working
>>>
>>> Hello,
>>> I'm currently using TPC 4.2.1 RCP and I would like to generate .docx
>>> documents using Gendoc2.
>>> I have to populate the document with rich-text documentation coming
>>> from my model so I need to use the <richText> ... </richText> tags
>>> into the .docx template document.
>>>
>>> I followed the Gendoc2 tutorial instructions so I installed the
>>> Gendoc2 - Rich Text tag from the update site:
>>> Gendoc2 - RichText tag (optional)       1.2.0.201011301618
>>>
>>>
>>> Now, when I generate the document from the template .docx I get the
>>> following error:
>>> "The execution of a script failed: The model Model can not be loaded
>>> from URL: "..." can not be loaded"
>>>
>>> The problem did not arise before adding the "RichText tag" support and
>>> the problem persists even if I remove the <richText> tags from the
>>> template doc.
>>>
>>> Is there any compatibility issue of the Rich Text tag (v.
>>> 1.2.0.201011301618) with the Gendoc2 core (Topcased Gendoc 2
>>> v.1.2.0.201011300212) which is included by TPC 4.2.1?
>>>
>>> Is there anyone who experienced the same problem?
>>>
>>> Thanks,
>>> Luca.
>>>
>>> _______________________________________________
>>> Topcased-users mailing list
>>> [email protected]
>>> http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
>>>
>>> ________________________________
>>>
>>>
>>> Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
>>> exclusif de ses destinataires. Il peut également être protégé par le secret 
>>> professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
>>> immédiatement l'expéditeur et de le détruire. L'intégrité du message ne 
>>> pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin 
>>> ne pourra être recherchée quant au contenu de ce message. Bien que les 
>>> meilleurs efforts soient faits pour maintenir cette transmission exempte de 
>>> tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa 
>>> responsabilité ne saurait être recherchée pour tout dommage résultant d'un 
>>> virus transmis.
>>>
>>> This e-mail and the documents attached are confidential and intended solely 
>>> for the addressee; it may also be privileged. If you receive this e-mail in 
>>> error, please notify the sender immediately and destroy it. As its 
>>> integrity cannot be secured on the Internet, the Atos Origin group 
>>> liability cannot be triggered for the message content. Although the sender 
>>> endeavours to maintain a computer virus-free network, the sender does not 
>>> warrant that this transmission is virus-free and will not be liable for any 
>>> damages resulting from any virus transmitted.
>>>
>>>
>>> _______________________________________________
>>> Topcased-users mailing list
>>> [email protected]
>>> http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
>>>
>>
>> _______________________________________________
>> Topcased-users mailing list
>> [email protected]
>> http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
>>
>>
>>
>> _______________________________________________
>> Topcased-users mailing list
>> [email protected]
>> http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
>>
>
> _______________________________________________
> Topcased-users mailing list
> [email protected]
> http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
>
>
>
> _______________________________________________
> Topcased-users mailing list
> [email protected]
> http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
>

_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users



_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
  • [Topcased-users] Gendoc 2 an... Topcased user list where issues are discussed
    • Re: [Topcased-users] Ge... Topcased user list where issues are discussed
      • Re: [Topcased-users... Topcased user list where issues are discussed
        • Re: [Topcased-u... Topcased user list where issues are discussed
          • Re: [Topcas... Topcased user list where issues are discussed
            • Re: [T... Topcased user list where issues are discussed
              • Re... Topcased user list where issues are discussed
                • ... Topcased user list where issues are discussed
                • ... Topcased user list where issues are discussed
                • ... Topcased user list where issues are discussed
                • ... Topcased user list where issues are discussed
                • ... Topcased user list where issues are discussed
                • ... Topcased user list where issues are discussed

Reply via email to