Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.5.2
-
Component/s: Tool Integrations
-
Labels:None
-
Environment:Operating System: Linux
Platform: PC
Description
JDeveloper sometimes will fail to add JspLibrary for ICEFaces Components.
one of the thing is that they copy jar file that contains tld file to local
project directory for tld file reference. Oracle does not use jar:file protocol
but a String value.
Further, it will compare with global Jsp Library Manager with local one. It more
likely fail. Since IDE code is updated with latest version number but not the
tld file.
so IDE parses the tld file.
Therefore, prefix and version is important in actual tld file.
Also, according to dtd
http://java.sun.com/dtd//web-jsptaglibrary_1_2.dtd
display-name is important
display-name the display-name element contains a short name that
is intended to be displayed by tools
If tld does not provide display-name in tld,, then IDE will guess or other fail
back situations ...
Need to look into more ...
one of the thing is that they copy jar file that contains tld file to local
project directory for tld file reference. Oracle does not use jar:file protocol
but a String value.
Further, it will compare with global Jsp Library Manager with local one. It more
likely fail. Since IDE code is updated with latest version number but not the
tld file.
so IDE parses the tld file.
Therefore, prefix and version is important in actual tld file.
Also, according to dtd
http://java.sun.com/dtd//web-jsptaglibrary_1_2.dtd
display-name is important
display-name the display-name element contains a short name that
is intended to be displayed by tools
If tld does not provide display-name in tld,, then IDE will guess or other fail
back situations ...
Need to look into more ...
Can this be fixed for 1.5.3?