Mikeh
You may use Cade strategy, you break your component diagram into separate diagrams, according to how you package your components : by related use cases, by responsabilities, by tiers....
Anothet strategy is to use generic component to model identical components: you don't need to show each
jsp page or each VO (jsp pages may be represented by a generic component labeled "View" or "User Interface", list them in your assumptions. You may also use composite components: component that contains other components: sample a
servlet which uses a view dispatcher, a request processor which uses actions, a BMP containing a DAO....
I have a component diagram with 30 components, it's very clean, without any intersection
Regards
Akar