|
From: Rob B. <rob...@ve...> - 2003-11-27 12:44:23
|
> So options include: > - description element for bean and description attribute for finer-grained > elements Why not just keep things consistent and use the element everywhere instead of an element in some areas and attributes in others. Since the element will be optional it won't make the xml any more complex when not used. Also it allows for greater flexibiliy. Someone might need to put in an extended comment (a la element) where you only allow for attribute comments. > Another decision is whether to expose bean-level descriptions > programmatically via the BeanDefinition. This may be useful, although I > think it's lower priority than getting the DTD right. Any thoughts on this? > Practical situations in which it would be useful? I can't see how this would be useful in a J2EE environment.. But it could (possibly) be useful when using Spring for Swing apps, or other apps that are "visually" contructed from Javabeans. Later Rob |