bean reinstanciation upon request

[DJViking]

What is frustrating - my advice or the whole situation

Concerning test application and real application - they, very likely , differs in a way how they load context. It is quite possible that in web application you load not that context that you mean to load (very typical error if you would look in the threads in this forum), especially if you have complicated context structure (e. g. multiply context files).

Try to make copy of your real application and strip it out step-by-step till you find a problem or obtain example that you may reveal.

Regards,
Oleksandr

It is frustrating not to find the error. There must be one someplace

My application would not work if I didn't load the application context that I mean to load(applicationContext.xml). And it loads that one. The application works fine when I create a new application context for each request. But now when I tried to define a bean as prototype so I did not have to load the application context each time. I only have two context files. (applicationContext.xml and DataSource.xml). The DataSource.xml is including in applicationContext.xml

Edit: I just created a new Web application. Loaded the application context(the entire piece) and prototyping worked.

[al0]

Is there in your real web application only one context file (no separate contexts for controllers and so on)?

How are you loading that context - with ContextListener configured in the web.xml or in some other way?

Can you put in your test web application the whole piece of code from real application that deals with those prototype beans?

Regards,
Oleksandr

It is frustrating not to find the error. There must be one someplace

My application would not work if I didn't load the application context that I mean to load(applicationContext.xml). And it loads that one. The application works fine when I create a new application context for each request. But now when I tried to define a bean as prototype so I did not have to load the application context each time.

Edit: I just created a new Web application. Loaded the application context(the entire piece) and prototyping worked.

[DJViking]

Is there in your real web application only one context file (no separate contexts for controllers and so on)?

How are you loading that context - with ContextListener configured in the web.xml or in some other way?

Can you put in your test web application the whole piece of code from real application that deals with those prototype beans?

Regards,
Oleksandr

I have one application context file(applicationContext.xml). Since I have 8 datasources I have seperated these bean in a DataSource.xml which application context import.

I load the application context the following way.

ApplicationContext applicationContext = new ClassPathXmlApplicationContext("applicationContext.xml");

I copied my entire web application code(one servlet) into the test web application and it still worked for the test web application. I have tried running in both WebSphere and Jetty with negative result for the real application as I run the test web application in WebSphere.

[al0]

Ok, so it seems that test web application handles context exactly the same way as real application, yes?

Then error shall be somewhere in the code of the real application.
Hard to say where w/o looking on the real code.

Regards,
Oleksandr

I have one application context file(applicationContext.xml). Since I have 8 datasources I have seperated these bean in a DataSource.xml which application context import.

I load the application context the following way.

ApplicationContext applicationContext = new ClassPathXmlApplicationContext("applicationContext.xml");

I copied my entire web application code(one servlet) into the test web application and it still worked for the test web application. I have tried running in both WebSphere and Jetty with negative result for the real application as I run the test web application in WebSphere.

[DJViking]

Ok, so it seems that test web application handles context exactly the same way as real application, yes?

Then error shall be somewhere in the code of the real application.
Hard to say where w/o looking on the real code.

Regards,
Oleksandr

It handles the context exactly the same way with one addedum it works with prototype beans while the real does not.

Edit: The error has been found. I had a copy of the applicationContext.xml in WebContent/WEB-INF/classes somehow.

[al0]

It handles the context exactly the same way with one addedum it works with prototype beans while the real does not.

Edit: The error has been found. I had a copy of the applicationContext.xml in WebContent/WEB-INF/classes somehow.

Exactly, as was predicted