There is one particular setter that is not getting called after Migration.Bussiness logic written in the setter is failing.
Strange thing is this application works fine in Local but is failing in TEST and PROD Environment.
The first thing for you to do is to find evidence of this problem. Log entries, unusual output, error messages, that sort of thing. Just saying it's "failing" is unhelpful. Read this Ranch FAQ entry for more information: TellTheDetails.
Joined: Dec 12, 2011
Here are the details:
Detailed description of problem :: <jsp:setProperty /> is not calling the setter of Declare Bean.
what you did :Migrated Application from WAS 6.0 to WAS 7.0 in UNIX Environment.
what you expected to happen : using <jsp:setProperty property="*" name="customer_param"> ,I expected all the setter in the bean to be called.
what actually happened instead : A particular setter defined in the customer bean is not getting called.
why what happened is a problem to you : There is business logic defined in the bean which is not getting executed.
Error message : No Error Message.
Version numbers of relevant libraries, JDK, tools, operating system etc. : JDK 6.0 , WAS 7.0 ,UNIX Environment.
Sujai Chell wrote:I have tried all these lateral thinking and couldn't come up with anything.
What I suggested wasn't "lateral thinking". It was just basic debugging.
My Problem desciption, i have very well summarized to be understood by a java Techie.
I don't think so. You said that one setter was not being called in the migrated version of the project. That's all. You didn't show us the code which contained that setter. You didn't tell us which setter it was. You didn't show us the parameters which you thought should change that setter.
You have to look at the details. High-level descriptions are fine if you like paperwork but they don't really help somebody who wants to solve the problem.
Read our FAQ article TellTheDetails for more information about that.
subject: jsp:setProperty failing after Websphere migration