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; } } }

Problem validating struts taglib

brizrobbo

Hi Folks,

I am just trying to get struts working as another webapp on my Teamsite DEV machine (TS 6.7.1, Solaris 10).

I am using the "customer_samples_src" structure as a bit of a stub, and I am "mapping" the typical struts structure into this structure to create a new webapp called 'struts-blank':

 ./etc/struts-bean.tld
  struts-config.xml
  struts-html.tld
  struts-logic.tld
  struts-nested.tld
  struts-tiles.tld
  tiles-defs.xml
  validation.xml
  validator-rules.xml
  web.xml
  webapp.ver

./lib/struts.jar

./src/resources/MessageResources.properties
    application.properties

./web/struts_blank/index.jsp

Normally the tag-libs in a Struts application go into ./WEB-INF and as far as I can see ./etc is really ./WEB-inf in the TS world.

Anyway, when I rebuild the webapp, I get this:

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

init: 

compile:
  [jar] Building jar: /Interwoven/TeamSite/local/config/lib/content_center/hello_world_out/hello_world.jar

validate:

BUILD FAILED
/Interwoven/TeamSite/local/config/lib/content_center/reference/build.xml:58: Could not validate document /Interwoven/TeamSite/local/config/lib/content_center/struts_blank_src/etc/struts-bean.tld

Total time: 2 seconds
Exception in /Interwoven/TeamSite/bin/make_toolkit.ipl: Failure while running Ant at /Interwoven/TeamSite/bin/make_toolkit.ipl line 170.

So I am thinking that my thinking is wrong :-). Any pointers would be gratefully appreciated.

Find more posts tagged with

Comments

thatfish

If you look at where the target directory of the application:-
IWHOME/httpd/webapps/content_center (there is a WEB-INF folder here)

You need to keep custom code under
customer_src

Reading the make_toolkit code may be of some help.

Bjorn

Reading the make_toolkit code may be of some help.

Excellent advice from thatfish. Note the line number the error provides, too, for build.xml, which in this case is probably going to tell you that XML validation is turned on. This will help you starting digging. Since the problem is with validation, my first guess is that it's looking for a DTD or something that it can't find.

brizrobbo

Hi Thatfish and Bjorn,

Thanks for your response. The samer erro happens regardless of whether you are using customer_src or any other toolkit.

I have jumped into the relevent lines of code in the make_toolkit.ipl, per:

run_ant($build_file, $target, $toolkit, $basedir, $opts{debug},
  $jsp_precompile, $opts{native_ant}) == 0
 || die("Failure while running Ant");

It's obviously an ant problem.

When I run ant outside of make_toolkit.ipl I get the same error.

Then, digging into the buildfile, I see the offending bit of configuration.

So, how I solved:

1. Download all the relevent DTDs and put them ./etc
2. Add the correct line for the struts-config_1_1.xml dtd in build.xml,
3. Change the DOCTYPEs for all the XML files and taglibs to make relative
4. Re-run make_toolkit.ipl

thatfish

Good stuff !

Of course if you have included iwov code/config changes (step 3) then you'll probably have to track these as they may get wiped in any upgrade.

Thanks for keeping the thread updated with your solution.

Bjorn

Hi Thatfish and Bjorn,

So, how I solved:

1. Download all the relevent DTDs and put them ./etc
2. Add the correct line for the struts-config_1_1.xml dtd in build.xml,
3. Change the DOCTYPEs for all the XML files and taglibs to make relative
4. Re-run make_toolkit.ipl

That makes good sense. I remember seeing something similar (and having a similar solution) when including our own log4j.xml configuration that our own classes were using.

I would heed thatfish's recommendation about version control for anything that's IW and would get changed in an upgrade. I've been bitten more than once by this type of thing. My own darn fault of course.

And thanks for documenting your fix -- this is way more helpful for people in the future.