Search:

Just as a warning to others reading this, I've had to remove this. It causes the bean post processors to run multiple times (due to refresh() at the end of context loading). I ended up having 8...

I managed to make the singleton context work but I wanted to ask to see if I've caused myself other problems. I did:



public class SingletonXmlWebApplicationContext extends...

We have multiple products. For simplicity, let's call them an orders system ("orders") and a billing system ("billing"). Customers may buy 1 or more of our products. No product must require another...

I'm trying to get the best of both worlds for transactions - aspects and annotations. I have a default aspect apply 'required' to all bean methods and then I want to override it with the...

To bring several posts together...

For HA, use a load balancer in front of your incoming requests (be it web services or browsers). Co-locate your spring services with your web server (tomcat,...

Job? WorkItem?

How large are the response HTML pages? If you've unsure, in Firefox you can right-click in the page and choose "View Page Info".

I've seen before that on a local computer, large pages still work...

Does your native method call some other dll/archive/library and is that library also in your library load path?

You might check that the 24x7 requirement includes client to server connectivity and update your time estimates. That sounds like something a clueless manager might throw in without asking how hard...

Here's a hint: Subsequent bean definitions replace earlier ones.

I'm trying to get a small Spring example running in WAS 5.1.1.11/WSAD 5.1.2 for the first time [so don't assume anything] and am having trouble.

The layout:
This is a large existing app with many...

Have you used any tools to determine what's taking the memory? Ideally, spring beans should be singletons and stateless which practically removes them from being the memory problem.

That seems hard to do. Time to start simple, like double checking that you're writing to the database you think you are, and are checking the same database. Then I'd start removing variables like the...

And if you're still nervious, build in some sort of check at build time. If you keep your interfaces in a different package than the implementations, simply grepping for usage of the impls should...

I think those layers allowed more flexibility than you realize.

Have you given much thought to how you're going to test with your flattened layering? Mock objects are obviously out.

How about...

[/QUOTE]

I agree with Simon -- putting libs in shared locations isn't the best way to go.

Problems that sharing libs can cause:

Class loader problems - you found this one
Independance -...