10.1.3.2 migration results in "not a registered TLD namespace error".

Question

After migrating from 10.1.3.1 to 10.1.3.2 JDEV I received the following error message in many jsps:
Error(11): "http://jakarta.apache.org/taglibs/xtags-1.0" is not a registered TLD namespace.
Error(5): "http://jakarta.apache.org/taglibs/dbtags" is not a registered TLD namespace.
These were not standard taglibs; they were part of the old application. I got the same errors in 10.1.3.1 but got around them by registering the taglibs.
Here's the web.xml entries from 10.1.3.2. They are identical to the web.xml entries from 10.1.3.1
<taglib version="2">
<taglib-uri>http://jakarta.apache.org/taglibs/xtags-1.0</taglib-uri>
<taglib-location>/WEB-INF/xtags.tld</taglib-location>
</taglib>
<taglib version="2">
<taglib-uri>http://jakarta.apache.org/taglibs/dbtags</taglib-uri>
<taglib-location>/WEB-INF/dbtags.tld</taglib-location>
</taglib>
Any ideas? other places to check?

Answer 1

Your suggestion helped to resolve my issue. However, in addition to the steps you outlined I had to go into JDev 10.1.3.2 -> Project Properties -> Libraries -> Edit ->
and edit the library properties to add classpath and sourcepath entries.
I'd still like to know why the migration from 10.1.3.1 unmapped the libraries.
--- Original Message ---
Hello Stephen,
Here is what I did:
JDev 10.1.3.2 -> Project Properties -> JSP Tag Libraries ->
Distributed Libraries -> Add -> User -> New
and you can import the tld/jar file and it will register the
library in Jdev.
After that it works fine, although you have to put (jaxp,
xalan, crimson, dom4j) in your project lib.
This setting are good enough for Jdev runtime, but when you
deploy the application on the server, you also need to have
web.xml changes as per you mentioned.
Hope this helps, otherwise let me know and I can send my working
project with JSPs to you.
Regards,
Chintan