September 2006 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: @SelectItems and @SelectItemsSelection annotations?

by CptnKirk

This is the expected behaviour. The @SelectItems annotation applies a data binder and outjects the wrapped object as a contextual variable (regions). Direct access to the method selector.getRegions() will return the method's original values. Useful for calling the method from other components or JSF backing beans. Getting a List of SelectItems wouldn't be right in that case. As with most things in Seam bijection happens to and from a Seam context. Seam adds a variable resolver so that JSF can find things stored in these contexts. However it doesn't prevent you from calling things via the JSF std way, getting JSF std results/objects back. If you did want JSF to intercept and apply conversion to #{selector.regions} you might be able to call the data binder directly within your custom converter. I think the method that does the conversion might be private, but I could change that if you think this code could be reused elsewhere. Otherwise, just remember that #{regions} gets a contextual variable from a Seam context and #{selector.regions} calls a method on #{selector} View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972639#3972639 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972639

19 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: PAGE scope DataModel's selection not correct

by petemuir

anonymous wrote : The JSF implementation, however, continues to use the first one outjected This is because you are outjecting to the page scope. Why don't you outject the DataModel to the Session scope (same as the bean). It's unusual IMO to outject to a shorter lived scope than the managing bean. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972636#3972636 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972636

19 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: the database of Seam application

by norman.richards＠jboss.com

Woops - that'll teach me to not look at that example. The original poster was right that the hypersonic instance in the booking example is entirely in memory. We normally don't recommend using a private instance like this, but it works for the example. To use the JBoss-managed HSQL instance, change the connection-url in booking-ds.xml to: | <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB</connection-url> Redeploy the application (not just the datasource) and then from the JMX console, find the jboss:database=localDB,service=Hypersonic MBean. Click the link, then invoke the startDatabaseManager operation. You'll see your data. You can look at the DVD store for another example. The DVD store uses it's own HSQL instance, but it registers it as a proper MBean so you can manage the data. Hope that helps. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972633#3972633 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972633

19 years, 7 months

1
0
0 / 0

[JBoss Seam] - Found the cause but not the cure

by Holy Joe

I've figured out why this is happening, but I don't know how to fix it yet. The problem is this: Each time a method on my bean gets called, the DataModel is injected/outjected, and a new DataModel is created to wrap my list. The JSF implementation, however, continues to use the first one outjected, so when it finally sets the rowIndex for my selected item, it is on a DataModel that is no longer accessible from Seam (it has been replaced by subsequent outjections). Without the extra form field, there's only one call to my bean, so there's no problem. Although I'm less lost when wandering around the Seam source these days, this seems like a deeper fix than my limited understanding can supply. Do any Seam gurus out there have some advice on how to go about fixing this? I'll give it a try myself, but a couple of starting pointers would be welcome. Thanks, Joe View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972632#3972632 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972632

19 years, 7 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: java.lang.NoClassDefFoundError: org/jaxen/JaxenException

by taha1967

I did but no way, jboss use the it's dom4j (jboss_home/lib) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972631#3972631 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972631

19 years, 7 months

1
0
0 / 0

[Persistence, JBoss/CMP, Hibernate, Database] - Re: How to prevent ApplicationDeadlockException with READ-ON

by odg

Hi, at my company we had similair problems but we solved them by marking the whole bean as read-only ( luky for us they were :-) ) this prevents the beans to be associated with the transaction and therfore prevents deadlocks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972630#3972630 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972630

19 years, 7 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Different hostnames for different applications.

by PeterJ

For the benefit of others who come across your post looking to do the same thing, could you please post how you got this to work? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972627#3972627 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972627

19 years, 7 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Different hostnames for different applications.

by Linuso

I've just solved it.. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972626#3972626 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972626

19 years, 7 months

1
0
0 / 0

[Persistence, JBoss/CMP, Hibernate, Database] - Re: QueuedPessimistic Locking Mechanism & Deadlock

by odg

Hi, at my company we had similair problems but we solved them by marking the whole bean as read-only ( luky for us they were :-) ) this prevents the beans to be associated with the transaction and therfore prevents deadlocks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972625#3972625 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972625

19 years, 7 months

1
0
0 / 0

[EJB 3.0] - Re: javax.naming.NameNotFoundException: ws1 not bound

by ren1218

Thanks for your quick reply, but I don't have a ear file to be deployed yet. I am looking for sample EJB3 java code that comes with build script. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972624#3972624 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972624

19 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user September 2006