Skip to Content
author's profile photo Former Member
Former Member

Ugly behavoiur of JSP compiler

Hi everyone,

I'm developing a customer taglib within the EP 6.0 SP02. After deploying the sources and the corresponding JSPs I get a lot of strange and inscrutable errors from the JSP compiler:

1.) unresolved symbol in jspxth_ftl_textEdit_0 jspxth_ftl_label_53.setParent(_jspx_th_ftl_textEdit_0); The error is as far as correct as I've taken a look into the sources generated by the PRT. <b>_BUT_</b> the label tag is an empty tag and the approriate call of setParent should be setParent(null). I cannot see why the generated code contains this instruction! So much worse as the behaviour still exists even when I have deleted the textEdit tag from the corresponding JSP and using just the label tag!

2.) Another tag contains the attribute 'enable' but if I use this attribute I'm getting the error 'Unable to Find Method : enable.' Without this attribute the tag works fine! But the attribute is definitely available (in Tag-Class and TLD).

I've tested the taglib with Tomcat and it works as expected. But within the portal it comes to the errors described above. Does anyone share this experiences and/ or has maybe a solution or at least an explanation on what's going on?

Regards Lars

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Nov 17, 2005 at 09:30 PM

    Hi Lars,

    Tag-support in the portal JSP implementation is known as strange 😉 see (which I haven't checked). In general, my experience is that the JSP implementation has a many "issues" which I would call bug but each OSS message I have opened about these have been rejected with the "reason" that the portal's JSP implementation is the portal's one and known as not being 100% within the standard and specification.

    Anyhow, I would like to encourage you to open an OSS message and to insist on implementing the specification.

    Hope it helps


    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Lars,

      > there are two differend implementations of the JSP

      > stuff doe by SAP. One for the Engine and one for the

      > portal

      That is right and that is what I wanted to express with my first answer; the portal JSP implementation at many points violates the specification.

      > we have opened an OSS message

      Would be great if you would come back with the results later.

      Best regards


Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.