The classes are, but the .tld files are separate (old way).
Norris Shelton Sun Certified Java Programmer
Brad wrote:
Norris Shelton wrote:
> >> Appears to work for me. >> >> Norris Shelton >> Sun Certified Java Programmer >> >> >> >> >> Brad wrote: >> >>> Anyone else seeing this? Mine is defined in web.xml. It worked in 2026 >>
hmm. And you have an entry in the web.xml to point to the actual tld?
Norris Shelton wrote:
The classes are, but the .tld files are separate (old way).
Norris Shelton Sun Certified Java Programmer
Brad wrote:
>> Norris Shelton wrote: >> >>> Appears to work for me. >>> >>> Norris Shelton >>> Sun Certified Java Programmer >>> >>> >>> >>> >>> Brad wrote: >>> >>>> Anyone else seeing this? Mine is defined in web.xml. It worked in 2026 >>> >>> >> Are yours in libraries?
hmm. And you have an entry in the web.xml to point to the actual tld?
>
Norris Shelton wrote:
> >> The classes are, but the .tld files are separate (old way). >> >> Norris Shelton >> Sun Certified Java Programmer >> >> >> >> >> Brad wrote: >> >>> Norris Shelton wrote: >>> >>>> Appears to work for me. >>>> >>>> Norris Shelton >>>> Sun Certified Java Programmer >>>> >>>> >>>> >>>> >>>> Brad wrote: >>>> >>>>> Anyone else seeing this? Mine is defined in web.xml. It worked in >>>>> 2026 >>>> >>>> >>>> >>> Are yours in libraries? >>
Never mind, I filed it. Also, the workaround I suggested earlier isn't the only thing needed to fix it. I'm not exactly sure what combination of things fixed it.
Are you saying your taglibs are being resolved now? Or you just can't reproduce my 'workaround'? Just wondering if you found a fix because mine aren't working again and I wasted half the morning trying to fix it and it's driving me f***ing nuts!
Appears to work for me.
Norris Shelton
Sun Certified Java Programmer
Brad wrote:
Norris Shelton wrote:
>> Anyone else seeing this? Mine is defined in web.xml. It worked in 2026
Are yours in libraries?
The classes are, but the .tld files are separate (old way).
Norris Shelton
Sun Certified Java Programmer
Brad wrote:
>
>> Appears to work for me.
>>
>> Norris Shelton
>> Sun Certified Java Programmer
>>
>>
>>
>>
>> Brad wrote:
>>
>>> Anyone else seeing this? Mine is defined in web.xml. It worked in 2026
>>
hmm. And you have an entry in the web.xml to point to the actual tld?
Norris Shelton wrote:
>> Norris Shelton wrote:
>>
>>> Appears to work for me.
>>>
>>> Norris Shelton
>>> Sun Certified Java Programmer
>>>
>>>
>>>
>>>
>>> Brad wrote:
>>>
>>>> Anyone else seeing this? Mine is defined in web.xml. It worked in 2026
>>>
>>>
>> Are yours in libraries?
Let me clarify.
web.xml:
http://www.appriss.com/customtags/webappsecurity /WEB-INF/lib/webappsecurity.jar ]]>
*.jsp:
<%@ taglib prefix="webappsecurity"
uri="http://www.appriss.com/customtags/webappsecurity" %>
The .jar contains the classes and a MANIFEST.MF and a taglib.tld in
inside the .jar under META-INF\
In another project, I have the following in my web.xml:
http://java.sun.com/jsp/jstl/core /WEB-INF/tld/c.tld ]]>
.jsp:
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
with the library under WEB-INF/lib
Norris Shelton
Sun Certified Java Programmer
Brad wrote:
>
>
>> The classes are, but the .tld files are separate (old way).
>>
>> Norris Shelton
>> Sun Certified Java Programmer
>>
>>
>>
>>
>> Brad wrote:
>>
>>> Norris Shelton wrote:
>>>
>>>> Appears to work for me.
>>>>
>>>> Norris Shelton
>>>> Sun Certified Java Programmer
>>>>
>>>>
>>>>
>>>>
>>>> Brad wrote:
>>>>
>>>>> Anyone else seeing this? Mine is defined in web.xml. It worked in
>>>>> 2026
>>>>
>>>>
>>>>
>>> Are yours in libraries?
>>
Doesn't work here either, my tlds are separate, and added to the relative path, AND my libs are added to the project AND deployed to the exploded dir.
No such luck.
R
Found my problem. My tld's encoding was set to ISO-8859-1. I changed it
to UTF-8 and all is well.
Robert S. Sfeir wrote:
I'd still consider this a bug.
R
Agreed. Did you file it?
Robert S. Sfeir wrote:
Actually, that doesn't appear to be the solution/work around. It's not
working again.
Robert S. Sfeir wrote:
Never mind, I filed it. Also, the workaround I suggested earlier isn't
the only thing needed to fix it. I'm not exactly sure what combination
of things fixed it.
Brad wrote:
>> I'd still consider this a bug.
>>
>> R
No, you can reproduce it, I can't :)
R
Are you saying your taglibs are being resolved now? Or you just can't
reproduce my 'workaround'? Just wondering if you found a fix because
mine aren't working again and I wasted half the morning trying to fix it
and it's driving me f***ing nuts!
Robert S. Sfeir wrote:
I already told Brad this over IM. So here is how you get things to work. This is really buggy, and a pain in the butt to trouble shoot.
the problem is that:
1- You have to create a new project
2- After you create the new project and setup the directories click apply
this will create it
but
it's corrupted or something
so what I do is I create a run/debug instance for Tomcat
if you do that, you will notice that the module shows up in red under J2EE
so what I do is go back into the path
fake a change
make it resave
and all is well after that
it's really screwed up... I'm sure they're working on it.
Also as a final note, if you have a JSP open, and the taglibs are fixed, they STILL show up in red. That caching problem is back JB folks!
R
fck,fck,fck,fck,fck,fck,fck,fck,f*ck
I just spent an hour recreating my project and trying to get this piece
of crap to work to no avail.
Robert S. Sfeir wrote:
Okay, I don't know what you did between 2026 and 2051 but it broke
taglib resolution for me. Put it back please!!
Brad wrote:
Still broken in 2072!
Brad wrote:
Oh, here's the bug I filed:
http://www.intellij.net/tracker/idea/viewSCR?publicId=33481
Brad wrote:
>> Anyone else seeing this? Mine is defined in web.xml. It worked in 2026