[JBoss Seam] - Re: Seam-Managed Persistence Context
by christian.bauer@jboss.com
Scoping means defining a Begin and an End of the persistence context, when it is opened and when it is closed. Seam has the @Begin and @End method annotations for that, which can automatically scope the SMPC to that conversation. So the SMPC would have the same scope as the Seam CONVERSATION context. A PC manages entity instances, they are attached to a PC (when they are loaded or stored).
Eager fetching is an orthogonal concern, you want it for a) SQL query optimization with joins and b) fetching of instances/values that you need outside of the PC scope, when an entity instance is considered detached.
I don't recommend that you try to learn this ad hoc, you really need to look at some docs and books. This is the fundamental programming model you need to understand.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000797#4000797
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000797
19 years, 3 months
[Beginners Corner] - Re: correctly packaging ear, war, har and ejb3 in jboss
by MmarcoM
hello,
didnt read all the post.. it's quite long
deploying ear in jboss is actually straightforward, allyou need to avoid, as you said, is duplication of classes
so structure your ear:
- war
- ear
jars that are commons needs to be placed outside those war/ear/
those common jars needs to be included in the manifest file of the jar that are dependent on them
there's no ejb3 issues, i have deployed successfuly an ejb3 app made of jar, war and ear, and didnt need to do anything.
my build system (maven2) was taking care of classpath in manifest file
go ahead and try to deploy your ear, and you will see that it's easier than what you think
hth
marco
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000788#4000788
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000788
19 years, 3 months