Error while running maketoolkit

Hi,

I am installing TS 6.7.2, but getting the following error while running maketoolkit.ipl,

Buildfile: //local/config/lib/content_center/reference/build.xml

init:

compile:

validate:

BUILD FAILED

/local/config/lib/content_center/reference/build.xml:68: Could not validate document /local/config/lib/content_center/customer_src/etc/web.xml

Total time: 0 seconds
Exception in /bin/make_toolkit.ipl: Failure while running Ant at /bin/make_toolkit.ipl line 173.

Environment details,
OS : Linux 5
TS : Sitepublisher 6.7.2 sp2

Thanks,
Raam

Find more posts tagged with

Comments

Adam Stoller

...
BUILD FAILED
<iw-home>/local/config/lib/content_center/reference/build.xml:68: Could not validate document <iw-home>/local/config/lib/content_center/customer_src/etc/web.xml

Total time: 0 seconds
Exception in <iw-home>/bin/make_toolkit.ipl: Failure while running Ant at <iw-home>/bin/make_toolkit.ipl line 173.

Hmm - well, have you looked at the web.xml file?

Based on the error message, that's the first place I'd look.

nipper

Hmm - well, have you looked at the web.xml file?

Based on the error message, that's the first place I'd look.

Actually that *may* not be the issue. I am seeing this as well on a 7.0 Beta system, web.xml was never modified. I suspect there is an environment issue, variables or some sort. I have not had the chance to debug mine yet, though I will post if I see results. I plan to crack open the make_toolkit script and see where it is looking for the DTD for web.xml, that is my first guess.

Bjorn

BUILD FAILED
/local/config/lib/content_center/reference/build.xml:68: Could not validate document /local/config/lib/content_center/customer_src/etc/web.xml

Total time: 0 seconds
Exception in /bin/make_toolkit.ipl: Failure while running Ant at /bin/make_toolkit.ipl line 173.

This is a guess, but is based on something I remember having to do with 6.7.2, albeit on a Windows implementation. Anyways, I am guessing the validation is failing because a path for a required resource was changed, but never updated in the ANT build script (build.xml). If I remember, the location of some of the servlet jars (that would hold the DTD for the web deployment descriptor, web.xml, for example) moved between versions of Tomcat.

So for starters, open \iw-home\local\config\lib\content_center\reference\build.xml (this is the windows path, but you get the idea) and look for references to jar files, specifically jsp-api.jar and servlet-api.jar. Then see if those paths actually exists on the filesystem. I am guessing they have been moved from ${iw-home}/servletd/common/lib to ${iw-home}/servletd/lib, and the paths would need to be changed in build.xml.

Migrateduser

For me it broke when we applied 6.7.2 SP2. I'm on Windows and ended up doing the following:

Modifying web.xml in the customer_src directory like this:

[HTML]
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"e:/iw-home/local/config/lib/content_center/customer_src/etc/web-app_2_3.dtd">[/HTML]

I then got the DTD and put it customer_src/etc.

After that make_toolkit.ipl runs fine.

Bjorn

For me it broke when we applied 6.7.2 SP2. I'm on Windows and ended up doing the following:

Modifying web.xml in the customer_src directory like this:

[HTML]
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"e:/iw-home/local/config/lib/content_center/customer_src/etc/web-app_2_3.dtd">[/HTML]

I then got the DTD and put it customer_src/etc.

After that make_toolkit.ipl runs fine.

The DTD exists in servlet-api.jar. ANT can find it to do the validation as long as it is given the proper location via the classpath element in the build script. If it's not (say, because someone at Interwoven forgot to update it even though its location changed!), then you get the validation error.

loanReport.rptdesign

Migrateduser

The DTD exists in servlet-api.jar. ANT can find it to do the validation as long as it is given the proper location via the classpath element in the build script. If it's not (say, because someone at Interwoven forgot to update it even though its location changed!), then you get the validation error.

Oh yeah. My "solution" is not ideal, but since I was pretty sure somebody at Autonomy dropped the ball, I spent my 10 minutes on it and moved on...

nipper

Oh yeah. My "solution" is not ideal, but since I was pretty sure somebody at Autonomy dropped the ball, I spent my 10 minutes on it and moved on...

So what causes it not to be read from the war file ? We had to do the same in a server that did not have internet access. Or was it really just going to http://java.sun.com/dtd/web-app_2_3.dtd regardless ?

Bjorn

So what causes it not to be read from the war file ? We had to do the same in a server that did not have internet access. Or was it really just going to http://java.sun.com/dtd/web-app_2_3.dtd regardless ?

Here's my understanding of it, based on Ant and what worked for me.

Nothing is being read from a WAR file at all, in this case. The way the validation is done is that the Ant build script uses an xmlcatalog type with a classpath that points to the jar in the servlet engine's lib directory. Look in the build.xml for the element "xmlcatalog", specifically under the "validate" target. So when it sees the URI for the DTD in web.xml, it first checks the filesystem for that DTD/resource, then the given classpath (which is probably wrong and the source of this issue...pointing to a jar that doesn't exist because it's been moved), then tries a bunch of other ways to resolver it. If you're a Java guy, it might be safe to think of it working like a pre-made EntityResolver.

Also see Ant doc for that core type: http://ant.apache.org/manual/CoreTypes/xmlcatalog.html. I think Ant has really good documentation.

"An XMLCatalog is a catalog of public resources such as DTDs or entities that are referenced in an XML document. Catalogs are typically used to make web references to resources point to a locally cached copy of the resource.

This allows the XML Parser, XSLT Processor or other consumer of XML documents to efficiently allow a local substitution for a resource available on the web. "