Search:

Actually, I'm referring to DB design and how it is handled by Hibernate. No one is saying that one-to-one object relationship is wrong. The problem is in its DB mapping. For example, PK generation...

Hmm. What's wrong with having many optional fields in one table?

It will look practically the same as one-to-many (in schema). That is, no one prevents you from attaching more than one entity in database (unless both entities share their primary keys, but then why...

The problem is that Hibernate does not really support optional one-to-one relationship.
In fact, such relationship is a mistake from relational point of view and indicates design problems. If you...

why do you think this is an architectural problem? I think you should post to Web forum instead.

Simply use #2. Unless you're pretty sure all your result sets fit in memory.
And think of this: you're wasting huge amounts of memory while users just never visit second page in 90% of cases.

OSGi services might be helpful here, but also could be an overkill.

Just curious - why are you unhappy with c:out and how replacing this tag with another tag makes any difference?

This is called Inheritance and Delegation. It is not a decorator/bridge/proxy/whatever.

It seems that your webapps will still be dependent on each other. What is the benefit of physically separating them?

some hardware devices support it on TCP level
and expensive ones - on HTTP level

as a low-cost solution you can try software LB, e.g. http://www.caucho.com/resin-3.0/config/balance.xtp#resin

Your operation spans multiple transactional resources. That means you have to either handle it in non-atomic way or use hardcore things like JTA and two-phase commits. Just a note, Spring cannot run...

Except that overhead of remote calls will eliminate any benefit you can achieve from this solution very quickly.

I would'nt do that, unless you are 100% confident that you can provide good balancing between these layers.

Different workload does not really make any sense because you use the same hardware i.e....

First of all, why do you want to distribute and cluster your application?
I know that "clustering" sounds cool, but what exactly do you plan to cluster?

E.g. if you want to cluster your Web load,...

You have to define return aliases, eg:


<sql-query name="hasValidCaseId">
<return-scalar column="id1" type="long"/>
<return-scalar column="id2" type="long"/>

We do it in a filter.
However, there's a big issue you have to worry about - error handling.
Usually any exception will cause transaction rollback, but how are you going to display error page is...

No, you don't need <form:options> to iterate a list.

Just wondering why you are using command.state, when your command is State. For some reason, you are putting data into request attributes,...

That's what every rookie OO designer does, at least once in his life...

I was very sad to hear that Guice provides support for such things. There's obviously something wrong with Guice or its...

Spring Framework itself does not provide anything except POJO wrappers.
Have a look at http://www.zeroc.com and their product called ICE.

Unit test is your documentation. And fairly good one. If you refactor something, and forgot to rename your model, tests will fail.

If you want more safety, add some jsp:useBeans into your JSP.

Sorry, I just don't get what sort of problem do you have.
A testcase may assert ModelAndView returned by Controller, why do you need anything more?

JSP is a class which has inputs:
- ServletContext
- HttpServletRequest & Session
- PageContext

and output which is HTML. A typical test will assert output depending on various inputs.

You...

Why don't you just take any of existing distributed filesystems?
Or buy a huge NAS and use it.

As I mentioned above, ${status.value} will always return java.util.Date.toString().

It does not use property editor. You have to format it explicitly, for example by using fmt taglib.