<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=NO-BOK link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Ricardo,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>That “unexpected error” message reveals little, and I have no clue why some templateone .properties files are published OK, while others are not. But these errors are bad news, and the fact that the .jar was missing also indicates a critical problem with the module import.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>One error here has a clear cause: <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Unable to unmarshal XML schema definition content "opencms: //system/modules/org.opencms.frontend.templateone.modules/schemas/layouts.xsd"<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It indicates a critical error in this file. Typically that would be a syntax or spelling error.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>You asked:<br>“Do I have to change something in the modules that I imported?” <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>My answer is “no”. If the module is OK on one install, you should be able to export it and import it on another install. Normally, It should work just as well there.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>*Normally*.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Here are some of the things that can cause trouble:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>- Core incompatibility (module was written for an older version of OpenCms, and does not work with the version you’re importing on)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>- Dependency issue (module depends on stuff that’s missing on the system you’re importing on)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>- ID conflict (a module resource type has an ID that’s not available on the system you’re importing on)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>- Module resource type uses widget / collector / etc. that has to be defined manually (not sure if this is relevant to you but I have experienced it)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>- Missing write permission on RFS folder(s)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It can be hard sometimes to identify the exact root of the issue. Perhaps try an import on a clean local install, and monitor the log to identify the initial error(s)?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Sorry you’re having so much trouble. I hope you’ll get everything worked out soon. (Or perhaps it’s time to ditch templateone..?)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best regards and good luck,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Paul<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> opencms-dev-bounces@opencms.org [mailto:opencms-dev-bounces@opencms.org] <b>On Behalf Of </b>Ricardo Sanchez<br><b>Sent:</b> 10. september 2015 13:06<br><b>To:</b> opencms-dev@opencms.org<br><b>Subject:</b> Re: [opencms-dev] CmsTemplateBean cannot be resolved to a type<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Thank you for your answer Paul.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>With the indications that you gave me the problem disappeared, in the WEB-INF lib the jar of templateone missed. But unfortunately after a problem always comes another, now I get the following:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>An unexpected Happened mistake, but no fault message has been provided.<o:p></o:p></p></div><div><p class=MsoNormal>Please check the bug details or contact your system administrator.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>All I did was change the path of the original file because I am now in a context of testing. The route is well written, I know it can be due, or if it is related to the problem described in the previous message.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thank you very much for your collaboration. Regards.<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>2015-09-10 10:18 GMT+02:00 Ricardo Sanchez <<a href="mailto:ricsanc1987@gmail.com" target="_blank">ricsanc1987@gmail.com</a>>:<o:p></o:p></p><div><div><div><p class=MsoNormal>Hello list:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I think I have already identified what the problem is. I imported in OpenCms modules that had in the old version that were related to templateone.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Reviewing the queue, I saw for example when importing org.opencms.frontend.templateone displayed the following message:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>Publicando ficheros ...</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 1 / 86 ) Publicando fichero /system/galleries/pics/ocms-templateone/bg_nav.jpg ... o.k.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 2 / 86 ) Publicando fichero /system/galleries/pics/ocms-templateone/head_img.jpg ... o.k.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 3 / 86 ) Publicando fichero /system/galleries/pics/ocms-templateone/logo_alkacon_150.png ... o.k.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 4 / 86 ) Publicando fichero /system/galleries/pics/ocms-templateone/logo_opencms_150.png ... o.k.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 5 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/org/opencms/frontend/templateone/workplace.properties ... fallo</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 6 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/org/opencms/frontend/templateone/workplace_de.properties ... o.k.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 7 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/org/opencms/frontend/templateone/workplace_en.properties ... fallo</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 8 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone.properties ... fallo</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 9 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone_de.properties ... o.k.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 10 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone_en.properties ... fallo</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 11 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone_form.properties ... fallo</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 12 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone_form_de.properties ... o.k.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 13 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone_form_en.properties ... fallo( 56 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/resources/icons/ic_app_htm.gif ... fallo</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>( 57 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/resources/icons/ic_app_html.gif ... fallo( 65 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/resources/menu_over.js ... fallo</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Failure = failure<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Similarly it works on other modules such as org.opencms.frontend.templateone.form importé<o:p></o:p></p></div><div><p class=MsoNormal>org.opencms.frontend.layoutpage<o:p></o:p></p></div><div><p class=MsoNormal>org.opencms.frontend.templatetwo<o:p></o:p></p></div><div><p class=MsoNormal>org.opencms.frontend.templatetwo.demo<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>When I import org.opencms.frontend.templateone.modules also displays the following error:<o:p></o:p></p></div><div><p class=MsoNormal>(3/64) Publishing file /system/modules/org.opencms.frontend.templateone.modules/classes/org/opencms/frontend/templateone/modules/workplace_en.properties ... Failure (2) File Indexing failure /system/modules/org.opencms.frontend.templateone.modules/copyresources/_configuration/layoutright ...<o:p></o:p></p></div><div><p class=MsoNormal>org.opencms.main.CmsRuntimeException: Unable to unmarshal XML schema definition content "opencms: //system/modules/org.opencms.frontend.templateone.modules/schemas/layouts.xsd".<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>What may be due? Do I have to change something in the modules that I imported? Thanks for your answers. <o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best regards.<o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>