"brachie" wrote : I thought it would be a too tight dependency between the
SFSB. For instance, if you inject SFSB A into SFSB B and SFSB C and change some
business logic in A maybe B or C are broken because they use some methods of A.
Umm. This is why you define an API? I think coupling that loo
mirko27,
Thanks, you saved my day (frustrations). I saw your post today but did not
realise the impact - thought is was about web.xml bindings. Now it works :-)
Regards,
Cyrill
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121640#4121640
Reply to the post
About the NameNotFoundException you got.
Search for my posts on the forum and you will find the solution.
You`ll have to declare ejb-reference in ejb-jar.xml when injection EJB.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121626#4121626
Reply to the post :
anonymous wrote : I thought it would be a too tight dependency between the
SFSB. For instance, if you inject SFSB A into SFSB B and SFSB C and change some
business logic in A maybe B or C are broken because they use some methods of A.
If you look at service oriented architectures (like SOA) - t
@Pete: thanks for the answer! :-)
"[EMAIL PROTECTED]" wrote : "brachie" wrote : In my opinion injecting one SFSB
into another should be avoided, but maybe I am wrong..
|
| anonymous wrote :
| | Why?
| |
|
I thought it would be a too tight dependency between the SFSB. For instan
Hi,
I tried a small example today (with glassfish) and failed to create it. There
is a thread and a JIRA-Issue failed against this problem:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=123592
and
http://jira.jboss.org/jira/browse/JBSEAM-2430
What's happening here is, that the bea
"brachie" wrote : In my opinion injecting one SFSB into another should be
avoided, but maybe I am wrong..
Why?
The following questions are in my mind:
anonymous wrote : Should there be one SFSB for every persistent class of your
domain model which acts as a manager and manages the actions con
"ruettimac" wrote : a) Injecting stateful session beans into other stateful
session beans?
No problem here, just use @In
anonymous wrote : b) Are there any problems regarding the different seam scopes
like CONVERSATION and long running CONVERSTAION scopes beans?
Like what?
anonymous wrote : c
@Cyrill: Interesting questions! I would also be very interested in an answer,
since we are currently using Seam in our project and having a proper
architecture is essential. I agree, that the seam examples are a bit too simple
as template for real-world application architecture.
In my opinion i
