<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'>Good morning Ricardo and the rest of y’all,<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’s a bit unclear to me what you mean here.<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'>If you are talking about ...<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'>... the xsd files themselves (e.g. mytype.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'>xsd files *are* just text files. They don’t have a more specific type, and should appear in the OpenCms workplace as type “plain”.<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'>... xmlcontent files (e.g. resources of type “mytype”):<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'>If these appear as the “plain” or “uknown” type in the OpenCms workplace, it means the resource type is not recognized by OpenCms. Either because the resource type is not properly installed, OR your servlet container has not been re-deployed after the install. Your log should contain the info you need. Try restarting the servlet container (i.e. Tomcat) and keep an eye on {OPENCMS_HOME}/WEB-INF/logs/opencms.log – look for errors during OpenCms startup. Also, you may want to check the error you get when you try to edit one of your unrecognized resource types.<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'>If you don’t mind me asking; Exactly *how* did you migrate your modules from the old system to the new one...? (It seems to me all your errors so far have been somehow related to broken module installs.)<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'>Cheers,<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> 16. september 2015 10:04<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>Good morning community:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I've found part of the solution to this problem. I looked at the part that says that the pointer was importing to a null reference and I realized that it was related to the xsd that is created in the module itself we use for our website.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>We have created 12 different types of content created and when I go to the folder from where the use I see that they all appear as text file and not the kind I want to use, that is, it does not recognize me the xsd.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I found a solution that is right click on the resource you want to modify, go to Advanced > Change type and there you can select the new type. As you will understand this task to make migrating from an older version is quite tedious because I have thousands of news, folders, and others ... My question is ... is there any way that recognizes the xsd directly without having to go changing by hand recourse to appeal?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>For if you serve as a reference, the structure of our own module is:<o:p></o:p></p></div><div><p class=MsoNormal>- Classes (here we have the properties to our workspace defined for Spanish and English)<o:p></o:p></p></div><div><p class=MsoNormal>- Elements<o:p></o:p></p></div><div><p class=MsoNormal>- Galleries (where are pdfs, images, other files that are part of the web)<o:p></o:p></p></div><div><p class=MsoNormal>- XmlSchemaDefinitions (where are our own xsd created)<o:p></o:p></p></div><div><p class=MsoNormal>- The JSP that serve as reference for templates<o:p></o:p></p></div><div><p class=MsoNormal>- Lib (folder which is currently empty)<o:p></o:p></p></div><div><p class=MsoNormal>- Resources (where css, js and images are)<o:p></o:p></p></div><div><p class=MsoNormal>- Templates (JSP templates)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Within XMLSchemaDefinitions, they are xsd:<o:p></o:p></p></div><div><p class=MsoNormal>- Contenido.xsd<o:p></o:p></p></div><div><p class=MsoNormal>- Curso.xsd<o:p></o:p></p></div><div><p class=MsoNormal>- Directorio.xsd<o:p></o:p></p></div><div><p class=MsoNormal>- Documento.xsd<o:p></o:p></p></div><div><p class=MsoNormal>- Enlaces.xsd<o:p></o:p></p></div><div><p class=MsoNormal>- Imagenes.xsd<o:p></o:p></p></div><div><p class=MsoNormal>- Noticias.xsd<o:p></o:p></p></div><div><p class=MsoNormal>- Ponente.xsd<o:p></o:p></p></div><div><p class=MsoNormal>- Pregunta.xsd<o:p></o:p></p></div><div><p class=MsoNormal>- Titulo.xsd<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>What am I missing? Any change in a configuration file?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks for your comprehension. Best regards.<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>2015-09-14 14:15 GMT+02:00 Ricardo Sanchez <<a href="mailto:ricsanc1987@gmail.com" target="_blank">ricsanc1987@gmail.com</a>>:<o:p></o:p></p><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 imported the templateone, I assure that within it is the class that needs to function properly and still no go. I give you an example of the error message shown me:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>Stacktrace:<o:p></o:p></p></div><div><p class=MsoNormal>Motivo: Unable to compile class for JSP:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>An error occurred at line: 16 in the jsp file: /WEB-INF/jsp/offline/system/modules/org.opencms.frontend.templatetwo/templates/main.jsp<o:p></o:p></p></div><div><p class=MsoNormal>CmsTemplateLayout cannot be resolved to a type<o:p></o:p></p></div><div><p class=MsoNormal>13: // be found at the following VFS location:<o:p></o:p></p></div><div><p class=MsoNormal>14: // /system/modules/org.opencms.frontend.templatetwo/java_src/CmsTemplateLayout.java<o:p></o:p></p></div><div><p class=MsoNormal>15:<o:p></o:p></p></div><div><p class=MsoNormal>16: CmsTemplateLayout cms = new CmsTemplateLayout(pageContext, request, response);<o:p></o:p></p></div><div><p class=MsoNormal>17: pageContext.setAttribute("cms", cms);<o:p></o:p></p></div><div><p class=MsoNormal>18: %><o:p></o:p></p></div><div><p class=MsoNormal>19: <cms:template element="head"><o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>As I said before, the .java file is located in the appropriate folder. I'm a little desperate because I am incapable of finding a solution. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thank you. A greeting.<o:p></o:p></p></div></div><div><div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>2015-09-10 13:06 GMT+02:00 Ricardo Sanchez <<a href="mailto:ricsanc1987@gmail.com" target="_blank">ricsanc1987@gmail.com</a>>:<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><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></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>