Win a copy of Rust Web Development this week in the Other Languages forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

jsp (jsf) & UML Class Diagram

 
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've been wondering & searching, but haven't found...

A good way to make a class diagram for a jsf project. My project is generally a bunch of jsf-files, which have no business logic; only processing instructions. These jsf-files, naturally, use (jsf)backing beans. The business logic is done in ejb-layer, which, from design point of view, can be invisible (just a layer).

So basically what I am looking for is a class diagram, which describes:
- jsf-files (what is happening there)
- backing-beans
- relations between the jsf-files
- relations with business logic

Something like:



Been trying to look for one, but just can't find anything. I could invent a sign-language of my own, but I'd like to have something done according to UML.

Any kind of hints / comments much appreciated,
Jussi
 
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I use JSF in my current project and, although my implementation doc is not detailed, I use class diagrams with dependency relationships.
Each JSF page is a class (which is true). Backing bean are also classes of course.
The dependency relationships have stereotypes such as navigation (between JSF pages) and ordinary (between JSF pages and backing beans, and between backing beans and business delegates).
In fact this is not a JSF problem: UML notation is not well suited to depict view layer.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic