[JBoss Seam] - Dynamic number of input types
by leezard
Hi all again,
Now I'm trying to solve another JSF/Seam related problem and hope yopu will help me to do it :)
I have an Seam component defined as:
|
| @Name("account")
| class Account {
| private String id;
| private String name;
| private List<Limit> limits;
|
| // getters and setters here
| }
|
|
| class Limit {
| private String type;
| private Long value;
|
| // getters and setters here
| }
|
Now my problem begins here: each account can have different limits number. Limits are system-wide configuration (e.g. you can have 4 different limit types defined and the you get a list with 4 items in Account instance). I can easily print all limit types and their input types using facelets <ui:repeat>:
| <ui:repeat value="#{account.limits}" var="limit">
| <h:outputText value="limit.type"/>
| <h:inputText value="limit.value"/>
| </ui:repeat>
|
But I'm affraid is't a bad solution. I want to submit form data together with limits data. Now I get NullPointerException on limits field in my action Bean. How can i properly get all the data? Do I need to use Limit as seam component also? Or do I have to use long running conversation somehow?
Thanks for replies.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082355#4082355
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082355
18 years, 7 months
[JBossCache] - Patch adding transactional putSilent() method
by Cyberax
Please, can you review this patch for addition into the mainline JBoss Cache?
The motivation for this patch
Currently, JBoss Cache adapter for Hibernate uses putForExternalRead() method. This method suspends and then resumes the current transaction and this is slow with some transaction managers, particularly with ones that support transaction recovery. For example, with Atomikos Transaction Manager it takes 25 seconds with putForExternalRead() on my computer to load a big Hibernate model versus 3 seconds with simple put() method in org.hibernate.cache.Cache implementation.
But simple put() method can't be used reliably, because DataVersioningException will be thrown if another thread has loaded the same object and put it in the cache.
Patch details
I've developed this patch to solve this problem. It adds putSilently() method to Cache interface, this method works exactly like putForExternalRead() except that it does not suspend and resume the current transaction. Instead, workspace nodes are marked so they can be ignored during optimistic validation if it fails.
I don't have much experience with JBoss Cache, but this patch works for me (or at least looks like it is working :) ). If the general idea is OK, I'll add mode documentation and unit tests for inclusion into the official JBoss Cache package.
You can get the patch here: http://sd-sup.staffdirector.net/cache.patch
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082353#4082353
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082353
18 years, 7 months