Oops, I got had by a deployment thing, (orion didn't recompile the jsp file when the TEI class changed...).  The thing that actually fixed the jsp compile problem was changeing the tei class from
           new VariableInfo("eCTSResult",
                            "String",
                            true,
                            VariableInfo.NESTED),

to            new VariableInfo("eCTSResult",
                            "java.lang.String",
                            true,
                            VariableInfo.NESTED),

The import didn't have anything to do with it.   :(

I've also figured out how to get access to the jsp source files:
In your config/global-web-application.xml file there is an <orion-web-app> node.  Add the property:
development="true" there, and to any other web-xml files in your applicatio-deployments tree as necessary.  This will cause orion to keep copies of the jsp.java files in your persistence directory tree, however it will name them wrong :(
My debugger looks for a source file of the same name of the class where the jvm is breakstopped so it necessary to rename the source files so that they conform to the name of the class within so that the ide will find them, (in this case NetBeans).  If you do that you can actually step through the code.
All tHis being said, there is still one catch:  Even with development mode turned on Orion is compiling the jsp.java files without the "-g" debugging switch so you don't have access to all the variable info.  Outside of using an external compiler for jsp's I don't see how to switch debugging on...
If I find out I'll post it here  :=)

WCN

Wendell Nichols wrote:

Well I made the jsp page work by explicitly importing "java.lang.String", as opposed to "java.lang.*" as I had done for other servers.  Because this shouldn't bother other servers I'm ok with it.
I still need to have access to the jsp.java files for debugging purposes before Orion will be an acceptable server for me...

Wendell Nichols
Amdahl Software Ltd.
Fujitsu Appserv.

Wendell Nichols wrote:

When I access a jsp page which uses a tag library I get an error:
 
500 Internal Server Error

Error parsing JSP page /ectsdemo/TagLibDemos/booklist.jsp line 15

Bean type 'String' not found

I suspect that this is a problem creating the java file from the jsp page related to the tag extra info class...  At any rate I can't find the source or class files that Orion generates from jsp pages so it's impossible to proceed.  Does anyone know how to make Orion place java and class files for jsp pages somewhere where they can be viewed and debugged?
I see jsp cache files which are probably some sort of java archive internal to Orion, but these don't help me as I can't open them...

Incidentally the jsp line that produced the above error looks like:

<ects:eCTSTaglet name="BOOKLIST" >

The taglib entry for eCTSTaglet:
  <tag>
     <name>eCTSTaglet</name>
     <tagclass>com.Amdahl.eCTS20.ects2taglet</tagclass>
     <teiclass>com.Amdahl.eCTS20.ects2tagletTEI</teiclass>
     <bodycontent>JSP</bodycontent>
     <info>
        Run a named taglet.
     </info>
    <attribute>
       <name>name</name>
       <required>true</required>
    </attribute>
    <attribute>
       <name>resultString</name>
       <required>false</required>
    </attribute>
    <attribute>
       <name>userdata</name>
       <required>false</required>
    </attribute>
  </tag>

Its TEI class :
 

  public VariableInfo[] getVariableInfo(TagData data) {
     return new VariableInfo []
        {
           new VariableInfo("eCTSResult",
                            "String",
                            true,
                            VariableInfo.AT_BEGIN),
           new VariableInfo("EndMsg",
                            "String",
                            true,
                            VariableInfo.AT_BEGIN),
           new VariableInfo("ReturnMsg",
                            "String",
                            true,
                            VariableInfo.AT_BEGIN)
        };
  }

Any help would be appreciated..

Wendell Nichols
Amdahl Software Ltd.
and
Fujitsu Apserv.

Reply via email to