Can't figure out this JasperException

[NoteMe]

If it is not too much trouble. Care to tell us what you had to do? So we can refer to it next time (if evere) it is asked.



Thanks
ØØ

[Dillinger4]

I thought i had it working at first but it seems i have to recompile my bean from the command line then resave the jsp page in order to see if any changes i make to the bean work or not. Jsp is starting to get annoying.

[NoteMe]

It never catched my eye at all... Never found the use for it.

[CornedBee]

And you worked the capitalization thing out? Beans are very simple. You have a bean property called "abcDefGhi", the setter is called "setAbcDefGhi" and the getter "getAbcDefGhi". I believe this capitalization is important, but it's also dead simple to remember, so there should be no problems.

The other steps are quite clear, too. Nowhere does JSP claim that it compiles beans. It only processes and compiles the JSP pages themselves.

*shrug*
I suppose it depends on the way you approach the whole thing. I wish I could get the Manager servlet working for virtual hosts.

[Dillinger4]

Posted by CornedBee

And you worked the capitalization thing out?

Yeah it was just odd though. For instance i just came back to my computer. The bean was the same bean i ran before with no errors.

private String output = "Brandon Rohlfs"; 
public String getOutput(){return output;}

I changed the bean

private String name = "Brandon Rohlfs"; 
public String getNameoutput(){return nameoutput;}

everything works. Now change back to the old bean

private String output = "Brandon Rohlfs"; 
public String getOutput(){return output;}

org.apache.jasper.JasperException: Cannot find any information on property 'output' in a bean of type 'com.TestBean'

I think it has to do with the memory within the server. Check out number four "Turn on servlet reloading". http://www.coreservlets.com/Apache-T...0-and-4.0.html

[Dillinger4]

I scaned the server.xml file for <Host name="localhost" debug="0" appBase="webapps" ...> and added this line right after it <DefaultContext reloadable="true"/> Seems to have worked.