Simple java archive type deployment is invalid in Jdeveloper 9031

Question

Hi All,
If I choose a Simple Java archive type of deployment of a jsp tag lib project in Jdeveloper the archive does not include the directory layout recursively. Ex. I get this.
c:\> jar tvf test.jar
64 Sat Jan 01 23:53:48 PST 2000 META-INF/MANIFEST.MF
1300 Sat Jan 01 23:53:48 PST 2000 META-INF/autodate.tld
5772 Sat Jan 01 23:53:48 PST 2000 test/autodate.class
Where if I do it the archiving from the comman line. i.e
c:\> jar cvf test.jar META-INF test
I get
0 Wed Feb 26 20:52:42 PST 2003 META-INF/
68 Wed Feb 26 20:52:42 PST 2003 META-INF/MANIFEST.MF
1300 Wed Feb 26 20:12:42 PST 2003 META-INF/autodate.tld
0 Wed Feb 26 20:12:42 PST 2003 test/
5772 Wed Feb 26 20:12:42 PST 2003 test/autodate.class
The latter is a valid archive that I can use for taglib deployment. The former, i.e the Jdev deployed archive does not work. The jsp does not find the tag library.
What is the archiving tool that jdeveloper uses??
Why is it different from doing a command line archive??
Is there anyway I can instruct the deployment tool to include the directory tree in the archive??
- Manish

Answer 1

Hi Lynn,
The Archive looks exactly the same and the jsp fails to find the tld from the classpath.
64 Fri Apr 04 13:53:48 PST 2000 META-INF/MANIFEST.MF
1300 Fri Apr 04 13:36:48 PST 2000 META-INF/autodate.tld
5772 Fri Apr 04 13:42:48 PST 2000 test/autodate.class
Note, this is a problem only when using the Tag lib autodiscovery mechanism of JSP 1.2 where the tld can exist anywhere in the classpath under META-INF and the path is not explicitly specified in the jsp.
- Manish
- Manish