So, in case of a stateless Bean Seam uses for Injection via @In a common
JNDI-lookup to the containers registry(ENC) ?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956544#3956544
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mo
great, thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954846#3954846
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954846
Using Tomcat but need to do more? Need to support web services, security?
Get stuff
Ok, and state-management of [EMAIL PROTECTED]/@Out-fields is not subject to
Seam, right?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954843#3954843
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954843
Using Tomc
Hi,
the Seam-reference documentation says, Seam provides deep integration with EJB
3.0 and fully supports EJB3.0 session-beans.
It is clear that Seam manages state of components that are put into the
seam-context using @Out and fetched from the context using @In.
However if I have a stateful se
Hello,
when I have a stateless service-bean which contains several stateless
dao-beans, where is the difference between the two relevant annotations @In and
@EJB for injecting the dao.
Is it correct that @EJB means the EJB-Container manages and injects the dao and
that @In means the Seam-framew
Its better to use the conversation-context, because then you can exactly
control how long the state exists and you donĀ“t have to remove it manually from
the context. If you have a long message-list with a lot of data the session
context is not appropriate. The session-context should be used only
thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952620#3952620
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952620
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicia
Well, the UIViewRoot is the container for all controls on the Page and its the
root element of the component tree.
However I actually wanted to know where the data is physically stored. I looked
into some JSF books and found that client-state-saving puts the state into the
rendered markup that
Hello,
I am writing my master thesis about Jboss Seam/EJB3/JSF and I am looking for
some information about how the client-state saving takes place. In the Seam
reference documentation is written the state is saved within the client
browser. But where is the information exactly, is it in the cac
Hi,
I am getting exactly the same error, could you please tell me which block in
persistence.xml you have changed,
thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3950252#3950252
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting
10 matches
Mail list logo