File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes jsp:setProperty failing after Websphere migration Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "jsp:setProperty failing after Websphere migration" Watch "jsp:setProperty failing after Websphere migration" New topic
Author

jsp:setProperty failing after Websphere migration

Sujai Chell
Greenhorn

Joined: Dec 12, 2011
Posts: 3
Hi All,
Am getting a strange issue in My Application. I have recently migrated my app from WAS 6.0 to WAS 7.0 . The Deployment went fine,but a piece of code is failing in JSP.
Am Using

<jsp:useBean id="customer_param" scope="session" class="com.quality.cust.data.CustomerParameters" />
<jsp:setProperty property="*" name="customer_param">



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.

Any Help will be appreciated.

Thanks
J
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18541
    
    8

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.
Sujai Chell
Greenhorn

Joined: Dec 12, 2011
Posts: 3
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.
Code snippets

<jsp:useBean id="customer_param" scope="session" class="com.quality.cust.data.CustomerParameters" />
<jsp:setProperty property="*" name="customer_param">

Stack trace : NA
What else you tried/what worked/what didn't work : I did a WAS7.0 set up in windos environment in my localmachine. The problem never occurred and everything worked fine.

Do let me know for any more details.
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18541
    
    8

Here's a technique you might find useful: if only one thing out of a group of things fails, ask yourself what is different about that one thing.

(I can only post vague generalities like that because you didn't post any details about your problem.)
Sujai Chell
Greenhorn

Joined: Dec 12, 2011
Posts: 3
Paul,
I have tried all these lateral thinking and couldn't come up with anything.
Thats the reason i posted here in forum ,in case someone faced a similiar problem before.

My Problem desciption, i have very well summarized to be understood by a java Techie.

Thanks
Sujai
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18541
    
    8

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.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: jsp:setProperty failing after Websphere migration
 
Similar Threads
<jsp:include> and <jsp:useBean>
client application connecting to local server after failing to connect to remote server
Failing to do lookup in Backing Bean
How to get an ArrayList Object in servlet from JSP?
Loading classes from a jar which are not in ClassPath