[opencms-dev] CmsTemplateBean cannot be resolved to a type

[Paul-Inge Flakstad]

Hi Ricardo,

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.

One error here has a clear cause:
Unable to unmarshal XML schema definition content "opencms: //system/modules/org.opencms.frontend.templateone.modules/schemas/layouts.xsd"

It indicates a critical error in this file. Typically that would be a syntax or spelling error.

You asked:
“Do I have to change something in the modules that I imported?”
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.

*Normally*.

Here are some of the things that can cause trouble:
- Core incompatibility (module was written for an older version of OpenCms, and does not work with the version you’re importing on)
- Dependency issue (module depends on stuff that’s missing on the system you’re importing on)
- ID conflict (a module resource type has an ID that’s not available on the system you’re importing on)
- 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)
- Missing write permission on RFS folder(s)

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)?

Sorry you’re having so much trouble. I hope you’ll get everything worked out soon. (Or perhaps it’s time to ditch templateone..?)

Best regards and good luck,
Paul

From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Ricardo Sanchez
Sent: 10. september 2015 13:06
To: opencms-dev at opencms.org
Subject: Re: [opencms-dev] CmsTemplateBean cannot be resolved to a type

Thank you for your answer Paul.

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:

An unexpected Happened mistake, but no fault message has been provided.
Please check the bug details or contact your system administrator.

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.

Thank you very much for your collaboration. Regards.

2015-09-10 10:18 GMT+02:00 Ricardo Sanchez <ricsanc1987 at gmail.com<mailto:ricsanc1987 at gmail.com>>:
Hello list:

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.

Reviewing the queue, I saw for example when importing org.opencms.frontend.templateone displayed the following message:

Publicando ficheros ...
( 1 / 86 ) Publicando fichero /system/galleries/pics/ocms-templateone/bg_nav.jpg ... o.k.
( 2 / 86 ) Publicando fichero /system/galleries/pics/ocms-templateone/head_img.jpg ... o.k.
( 3 / 86 ) Publicando fichero /system/galleries/pics/ocms-templateone/logo_alkacon_150.png ... o.k.
( 4 / 86 ) Publicando fichero /system/galleries/pics/ocms-templateone/logo_opencms_150.png ... o.k.
( 5 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/org/opencms/frontend/templateone/workplace.properties ... fallo
( 6 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/org/opencms/frontend/templateone/workplace_de.properties ... o.k.
( 7 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/org/opencms/frontend/templateone/workplace_en.properties ... fallo
( 8 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone.properties ... fallo
( 9 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone_de.properties ... o.k.
( 10 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone_en.properties ... fallo
( 11 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone_form.properties ... fallo
( 12 / 86 ) Publicando fichero /system/modules/org.opencms.frontend.templateone/classes/templateone_form_de.properties ... o.k.
( 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
( 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

Failure = failure

Similarly it works on other modules such as org.opencms.frontend.templateone.form importé
org.opencms.frontend.layoutpage
org.opencms.frontend.templatetwo
org.opencms.frontend.templatetwo.demo

When I import org.opencms.frontend.templateone.modules also displays the following error:
(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 ...
org.opencms.main.CmsRuntimeException: Unable to unmarshal XML schema definition content "opencms: //system/modules/org.opencms.frontend.templateone.modules/schemas/layouts.xsd".

What may be due? Do I have to change something in the modules that I imported? Thanks for your answers.

Best regards.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20150911/8cce6831/attachment.htm>