[JBoss Seam] - Re: @Convert and overriding standard types
by CptnKirk
Hmm, what I was seeing on JBoss 4.0.5, which should be MyFaces on JSF 1.1, is that my converter wasn't being called at all in either direction when I tried to override forClass=String.class.
What I've written is a quick converter to translate empty Strings into null. This makes my DB happier (as well as my equals()). Currently when I take input from a form and don't populate fields, they become empty strings. I'm trying to replace that default semantic with my Seam @Convert converter.
Works great if I specify a <f:converter> everywhere, but that's kind of a drag. On the whole I still love being able to register a JSF converter with two annotations. Thanks Seam.
PS: Perhaps this is an issue with MyFaces. As you say, the spec may not be clear. I'm looking forward to JBoss 4.2 and the 1.2 RI. (yea I know I could hack 4.0.5, but I'm not gunna :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037247#4037247
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037247
19 years
[JBoss Seam] - Re: core:managed-persistence-context question
by CptnKirk
The is the typical @In vs @PersistenceContext question. The answer is summed up nicely in this thread.
http://jboss.com/index.html?module=bb&op=viewtopic&t=106019
Basically to answer your questions:
1. What the <core:...> is doing for you is configuring a Seam managed persistence context. You take advantage of this by using the Seam managed context instead of the EJB3 managed context.
2. How do I do that? Use the @In annotation. The Seam managed context is a Seam component exposed via Seam's bijection mechanism so use the @In annotation to get it.
3. So how are they different? See Christian's answer in the link above, or read my answer here. First, the following link has a good description of Seam and ORM. http://docs.jboss.com/seam/1.2.1.GA/reference/en/html/persistence.html Use the link to familiarize yourself with the benefits of the EJB3 extended PersistenceContext. The difference between the Seam PC and the EJB3 PC is that Seam provides a couple of features that EJB3 doesn't, otherwise in terms of APIs they're the same.
1. The lifecycle of the EJB3 PC is bound to a Stateful Session Bean, and is only shared between components participating in the same transaction. The Seam PC has conversation scope and can be injected into any component participating in that conversation regardless of its transaction context.
2. Seam PC has better clustering and caching abilities. See the Seam doc link above for reasons why.
3. Seam PC is managed by Seam not EJB3, thus it can be used within non EJB3 Seam components. So you can still benefit from a standard JPA interface while allowing Seam to manage the PC and transactions for you, all outside of EJB3.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037241#4037241
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037241
19 years