Search:

You mean using those "advices" with AOP for exception handling? conceptually I don't get that approach. I think using a global exceptioan handler is a lot less trouble.

I know you can specify an error page for your JSPs. However, I have an exception handler which forwards to a custom made error view, and I like all exceptions go through there, regardless if they are...

What's wrong with havning a centralized location for exception handling and logging? Especially when in this particular application the lower level components don't know what to do with those...

I am using log4j with Spring, here is my log4j.xml file:

<appender name="WARN" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="C:\\logs\\app-info.log"/>
...

I tried this:
DefaultTransactionDefinition txDef =

new DefaultTransactionDefinition(DefaultTransactionDefinition.PROPAGATION_REQUIRED);



...

Any best practices, recommended approches, articles on the right way to handle exceptions in the Spring web framework?

Don't have a specific problem, but looking for general guidance.

Thanks!

k, let me see, thx.

hey guys,

This most likely won't be a Spring issue or have a Spring solution, but I thought I'd ask. What do you guys do to stop a query running over X secs with no results back? I am using...

Not really a problem. Just wondering where you are handling the responsiblity of persisting information to the session scope. I guess it cannot be in the usecase layer since you want to decouple that...

Good for you. But I can't seem to get away from persisting data to the session. Or persisting session specific data in one form or other.

http session.

"So only the controller needs to keep its hands of the session"

well, are you saving data/objects in the session? is the solely the responsiblity of the controllers?

Where do you handle the responsiblity of persisting/getting/managing information to session when you need to?

yes, I have similar concerns too.

If we stick the said "functionality" into controllers, there is no reusability. If we leave it out, the controllers become skeletons.

Some readers here...

I have thought about similiar approaches. I wonder, however, if so called usecase is the right type for the component. My thought was controller still control the usecase, however, there is a helper...

yup, that helps, thanks!

interesting point on the stateless nature of the helper. I was wondering about that since I do have to pass in "request" when I use the helper, not ideal. good point!

possibly...

my current solution is making a singleton called ControllerHelper, and IOC that into the controller needs its functions.

The reason I did that versus using an abastract controller...

Let me try to clarify a bit more.

I have a particular step in my presentation tier. Within this step, it executes some business logic, analyze the result, and based on the result prepare some...

In practice, should I create a component for the presentation tier that executes business logic and prepare model and handle view management because the combination of the three are reusable through...

Guys,

I have a design question I could use some inputs on.

The basic flow of the web application is basically:
1) A view forwards to a controller.
2) The controller processes the...

Guys,

I have a design question I could use some inputs on.

The basic flow of the web application is basically:
1) A view forwards to a controller.
2) The controller processes the...

still cannot find the right parameter to set in the datasource config. I am NOT using hibernate or transactions, just the basic datasource.

thanks!

Has anyone done this before? Basically I want an exception to be thrown if no resultset comes back in 60 seconds.

Thanks!