[jboss-user] [JBoss Seam] - Re: Combining list and all CRUD functionality on a single pa

Also, is using disabled input components (e.g. h:inputText) instead of output components (e.g. h:outputText) considered bad practice? The reason I ask is that it would certainly simplify my forms if I can just set the disabled attribute on components rather than having to duplicate every input

[jboss-user] [JBoss Seam] - Combining list and all CRUD functionality on a single page?

Hi, I'm just wondering whether it makes sense to combine listing and all create, read, update and delete functionality all on the same page? The reason I ask is that all the examples I've seen tend to split this functionality out onto separate pages, and coming from a Swing background this see

[jboss-user] [JBoss Seam] - problem about @Observer and Events

Hello I have a bunch of session beans with conversation scope. the conversation starts by clicking search button. when the result is shown on the second page the user can go to its setting page and after make his changes and apply them he/she turns back to the result page. in order to apply n

<    1   2