We use an Axis SOAP interface to communicate to our session beans. I
don't necessarily recommend it, but it does the trick nonetheless...
Regarding EJBs, we saw significant performance hits when conducting
heavy CMP crunching. A simple solution was to employ direct JDBC calls
within the session beans. This increased performance 10-fold, in some cases.
Mike
[EMAIL PROTECTED] wrote:
I don't understand Dave's concern. Perhaps he would elaborate on why he says to
avoid Session beans.
I have developed applications using Session beans wrapping DAOs for search,
etc., along with timer-reloading Entity beans and have seen good results.
However, it may be that he would favor POJOs if the container isn't really
giving your app anything (why go through the trouble of EJB in other words). In
my case I found plenty of benefit in the declarative transaction handling alone.
As for business delegate + session facade. Sure, I can see a case for that. You
are adding more complexity, but, your Struts actions shouldn't need to interact
with EJB in an ideal world, even if it's a facade-level EJB. I like to have
actions access a Manager (aka business delegate) only. Everything else is
hidden behind the manager (whether that be EJB access, direct DAO access, or
some combination).
Another camp would tell you to just use something like a business delegate + iBatis or Hibernate. I cannot comment as I have not used that approach. Personally, I like to write all my own SQL (along with everything else you can write).
Erik
-----Original Message-----
From: Maya menon <[EMAIL PROTECTED]>
Sent: Jul 20, 2005 3:35 PM
To: Struts Users Mailing List <user@struts.apache.org>
Subject: Re: Hi-New to this group
Thank you dave and Eric for the quick solution regarding session facade.
Now using a business delegate and a session facade, is it a good idea ?
Also, As Dave wrote about session ejbs, please suggest some give work arounds
for a session ejb. Requirement is to read contents from database.
Maya
Dave Newton <[EMAIL PROTECTED]> wrote:
Maya menon wrote:
Now, back end I am thinking about session ejbs which reads database tables.
Unless there's a requirement or Very Compelling Reason to use EJB I'd
sure try to avoid them.
Now, what should I use in the middle layer ?
ie, intercation between action classes and session ejb: For a struts based
appp, whats best here ?
I'd think that a fairly basic facade between the session EJB and/or some
helper classes would be sufficient.
Googling for "session facade" should give you more than enough info.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
