nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Generator broken in 7.0?

josephbreese

Can anybody with 7.0 verify that the <Generator> tag is working?

I have a requirement to display a list of languages to a page designer when a component is inserted into a page and double-clicked, this list of languages will change in the future and we want to automatically generate this data for all components that will use this data. Here is a hard coded example:

[HTML]

English
en_US

Spanish
es_US

French
fr_CA

[/HTML]

Obviously this is not ideal for us. As we would have to update hundreds of components and then selectively update or replace them on over 10,000 pages.

So I wrote a little piece of Java that returns a Dom4j Document:


public Document getAvailableLanguages(RequestContext context)
{
 Document doc = Dom4jUtils.newDocument();
 Element Options = doc.addElement("Options");
 Element Option = Options.addElement("Option");
  Option.addElement("Display").addText("English");
  Option.addElement("Value").addText("en_US");
 Option = Options.addElement("Option");
  Option.addElement("Display").addText("Spanish");
  Option.addElement("Value").addText("es_US");
 Option = Options.addElement("Option");
  Option.addElement("Display").addText("French");
  Option.addElement("Value").addText("fr_CA");

 return doc;
}

This is the XML the above code returns when called from a component prefix tag:
[HTML]

English
en_US

Spanish
es_US

French
fr_CA

[/HTML]
The Document returned by Java must have a wrapper around the <Option> tags as a Document must have only one root element. This wrapper is suggested to be <Options> but when this is hard coded into the content XML, I get a validation error:

[HTML]

Blah
blah

Blah2
blah2

[/HTML]
Displays this error:
Component preview failed.

Could not load component data XML into XMLDOM.

com.interwoven.livesite.common.xml.ValidationError mColumn[10] mLine[8] mSystemID[null] mPublicID[null] mType[ERROR] mMessage[cvc-complex-type.2.4.a: Invalid content was found starting with element 'Options'. One of '{Font, Image, Date, Option, ContentTypes, DCR, Site, Generator, PropertyPrefix}' is expected.]

Ignoring this I created a simple Datum Generator:
[HTML]

[/HTML]
Which results in this error:
Component preview failed.
Could not load component XML into XMLDOM.
Datum ID=[blah]
Must have least one option

Isn't the point of a <Generator> to NOT use any <Option> tags? So I figure this is a glitch just like External Components requiring external Java to run when you use external parameters and do what is suggested:

[HTML]

English
en_US

[/HTML]
Results in this error message:
Component preview failed.

Could not load component data XML into XMLDOM.

com.interwoven.livesite.common.xml.ValidationError mColumn[103] mLine[7] mSystemID[null] mPublicID[null] mType[ERROR] mMessage[cvc-complex-type.2.4.a: Invalid content was found starting with element 'Generator'. One of '{Option}' is expected.]

So does anybody have any input?

Find more posts tagged with

Comments

vpatel


public Document getAvailableLanguages(RequestContext context)
{
 Document doc = Dom4jUtils.newDocument();
 Element Options = doc.addElement("Options");
 Element Option = Options.addElement("Option");
  Option.addElement("Display").addText("English");
  Option.addElement("Value").addText("en_US");
 Option = Options.addElement("Option");
  Option.addElement("Display").addText("Spanish");
  Option.addElement("Value").addText("es_US");
 Option = Options.addElement("Option");
  Option.addElement("Display").addText("French");
  Option.addElement("Value").addText("fr_CA");

 return doc;
}

Instead of code above, try something like this:


public Document getAvailableLanguages(PropertyContext context){
 Document doc = Dom4jUtils.newDocument();

 Element options = doc.addElement("Options");

 GeneratorUtils.addOption(options, "English", "en_US");
 GeneratorUtils.addOption(options, "Spanish", "es_US"); 
 GeneratorUtils.addOption(options, "French", "fr_CA"); 

 return doc;
}

Couple of things to note:
1. It is NOT RequestContext -- rather PropertyContext
2. This is unrelated but consider naming your Java variables according to Java standards (i.e. Element options = ... and NOT Element Options = ....).

josephbreese

Instead of code above, try something like this:
...
message trimmed for brevity
...

Viral, thanks for the suggestions. However, these suggestions do not solve one of the original problems:


Component preview failed.
Could not load component XML into XMLDOM.
Datum ID=[blah]
Must have least one option

The DTD does not understand that a generator tag can be used as a replacement to an option tag, however another error message indicates that a generator tag is valid:


Component preview failed. 
Could not load component data XML into XMLDOM. 
com.interwoven.livesite.common.xml.ValidationError mColumn[10] mLine[8] mSystemID[null] mPublicID[null] mType[ERROR] mMessage[cvc-complex-type.2.4.a: Invalid content was found starting with element 'Options'. One of '{Font, Image, Date, Option, ContentTypes, DCR, Site, Generator, PropertyPrefix}' is expected.]

At this point I'd love to get to the Preview of the component and get runtime errors, then I can try the PropertyContext you suggested, or Hashtable input parameters listed in documentation.

Is there a way to bypass the DTD validation of a component so I can see if the issue lies within the DTD?

AlexC

1. "Must have at least 1 option" means your generator failed to execute, check the logs please.
2. Options in a Datum MUST be associated with a Generator.

You have several ways of doing options described here, which are you using?

Can you look at impl.zip for the sample generator example, (I believe it is called SampleGenerators.java in that file). It demonstrates how to use them correctly.

josephbreese

1. "Must have at least 1 option" means your generator failed to execute, check the logs please.
2. Options in a Datum MUST be associated with a Generator.

You have several ways of doing options described here, which are you using?

Can you look at impl.zip for the sample generator example, (I believe it is called SampleGenerators.java in that file). It demonstrates how to use them correctly.

Alex, thanks for the input but please forgive my newbie-ness. Can you tell me which log files I should be looking through? I can figure out things by time stamp.

<gripe>
It would be really nice if you guys (Autonomy/Interwoven) would return more descriptive/accurate error messages and possibly the log file to look through.
</gripe>

All those methods and code snippets in my original post are to show the process I've gone through so it doesn't appear that I want you guys to do my work for me.

My solutions and testing thus far is:
1. We can hard code (bad idea)
2. Ultimately I want to use a Generator, so I tried to hard code what a generator *would* output into a SelectSingle Datum and that failed validation upon save.
3. I ignored the warning from the above trial and just made the Generator call and I got another error stating I need an "Option" tag in a Select Datum

Is there a way to side skirt the document validation in the component editor when clicking the save button?

AlexC

Open /Interwoven/TeamSite/httpd/webapps/content_center/WEB-INF/conf/livesite/log4j.xml

Set com.interwoven.livesite to DEBUG

Repeat your test and then check:

/Interwoven/TeamSite/local/logs/iwui/content_center.log
/Interwoven/TeamSite/local/logs/iwui/servletd_out.log

josephbreese

Open /Interwoven/TeamSite/httpd/webapps/content_center/WEB-INF/conf/livesite/log4j.xml

Set com.interwoven.livesite to DEBUG

Repeat your test and then check:

/Interwoven/TeamSite/local/logs/iwui/content_center.log
/Interwoven/TeamSite/local/logs/iwui/servletd_out.log

thanks, i'll post details shortly

josephbreese

Open /Interwoven/TeamSite/httpd/webapps/content_center/WEB-INF/conf/livesite/log4j.xml

Set com.interwoven.livesite to DEBUG

Repeat your test and then check:

/Interwoven/TeamSite/local/logs/iwui/content_center.log
/Interwoven/TeamSite/local/logs/iwui/servletd_out.log

Alex, thanks for the tips. Everything is working as expected. Our logging was set to "info" or warn, and was displaying a descriptive error message, I just didn't know where to look.

Thanks again.

vpatel

Alex, thanks for the tips. Everything is working as expected. Our logging was set to "info" or warn, and was displaying a descriptive error message, I just didn't know where to look.

Thanks again.

Have you tried the 2 log files that Alex pointed out in his previous post? Anything of interest in there?

Also, let's try to make this real simple and see how can we get you over this hurdle. Please post your component and Java class.

josephbreese

Have you tried the 2 log files that Alex pointed out in his previous post? Anything of interest in there?

Also, let's try to make this real simple and see how can we get you over this hurdle. Please post your component and Java class.

My message got clipped somehow, anyway. I looked through the logs listed and the error messages were returning a much better and more descriptive message than the pop-ups. From there is was just making sure the method was using PropertyContext as input parameters as you previously indicated, however I was a doubter in this being the solution as the pop-up message was not anywhere close to describing the problem.

Anyway, thanks Viral and Alex for your help. I'm off to discover more issues with our implementation