Well said.....
I agree. Struts has its place and so does EJB.
You can not compare them because they are apples and oranges.
I've had similar problems with articles from various magazines and Journals,
which shall rename nameless.
I don't think it is the magazine. It is the author.
Which reminds me of a saying......
"Everyone has an opinion. Some of them stink!"
--Rick Hightower
Director of Development
eBlox Tucson
phone: 520-615-9345 x103
fax: 520-529-5774
http://www.eblox.com/people_detail.php?id=52
http://www.geocities.com/rick_m_hightower/
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 19, 2001 9:02 AM
To: [EMAIL PROTECTED]
Subject: RE: java report article says "bye-bye struts" (answer to Bill
G)
Two years ago I came across an articlein JDJ comparing Servlets and CORBA
and
when you would use one vs. the other. I had just finished a project that
made
extensive use of both with servlets in the front end and CORBA as the middle
layer to talk to data access objects that were distributed throughout the
network.
As such, I felt the article was incredibly amateurish and that attempting to
even write an article describing the two technologies as replacements for
each
other utterly ridiculous. I have not read JDJ since.
Now I am finishing another elaborate project using STRUTS in the front end
with
JNDI to EJB data access objects in the back end and I come across this
discussion. I guess I don't need to read JavaWorld either as their authors
also
seem to demonstrate a basic lack of understanding of the technologies they
review.
In answer to your question Bill, yes you can use STRUTS to begin your
project
and no, you won't need to "replace" it with EJB. STRUTS simply gives you a
way
to retrieve and present data in a clear, concise way via the web. Your
Action
classes can do simple two-tier data access via JDBC, or they can do JNDI
lookups of EJBs located throughout your network, or they can behave as CORBA
clients in a heterogeneous environment. It doesn't matter, it's only up to
you.
If you feel that you may have a changing environment, I suggest you create
client-side data access interfaces that your actions use to access backend
data. Then you can use a 2-tier implementation of the interface to start and
replace it with an EJB client implementation when your system needs to
mature
without affecting the UI code that is in the JSPs and Action classes.
I hope this is of some help.
Don Clasen
Oak Grove Software
Quoting "Hogan, John" <[EMAIL PROTECTED]>:
> wasn't it nicer under that rock?
>
> -----Original Message-----
> From: Bill G [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 18, 2001 5:04 PM
> To: [EMAIL PROTECTED]
> Subject: RE: java report article says "bye-bye struts"
>
>
> Hi Craig,
>
> "Although excellent in dealing with Web-based applications, Struts is
> not
> ready to take on EJB."
>
> This is a concern of mine as well but as a newbie to this technology, I
> am
> wondering how to adopt the Struts framework knowing that I will move to
> EJB's. Is it worth starting with Struts with the idea of moving to EJB's
> or
> what? Any info on this matter is seriously appreciated!
>
> Thanks
> BG...
>
>
>
> -----Original Message-----
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 18, 2001 11:14 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: java report article says "bye-bye struts"
>
>
>
>
> On Mon, 18 Jun 2001, Ritter, Steve wrote:
>
> > Hi Hal, yeah I read the same article and couldn't help but laugh.
> > Prashant really made some outlandish comments and hopefully those
> > comments will diminish any negative impact his article might have on
> > Struts (or, the adoption of Struts I should say).
> >
> > Craig, if you read this thread it might not be a bad idea to send a
> > quick email to the editor's of Java Report and let them know about
> > some of the mis-leading statements. Sounds like their review board
> > needs a little re-org.
> >
>
> Looks like I'll have to go buy a copy -- I don't pay a lot of attention
> to
> trade magazines in print, because production cycles make them so far out
> of date.
>
> Judging from the many thank-you's I've received for the 1.0 final
> release, I wouldn't worry to much about negative impact on Struts
> adoption. :-)
>
> > --Steve
> >
>
> Craig
>
> > > -----Original Message-----
> > > From: Deadman, Hal [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, June 18, 2001 7:52 AM
> > > To: 'Struts List'
> > > Subject: java report article says "bye-bye struts"
> > >
> > >
> > > Clearly there are too many java magazines and they will
> > > publish anything. In
> > > the July issue of Java Report there is an article titled
> > > "Writing a Reusable
> > > Implementation of the MVC Design Pattern" by Prashant Sarode
> > > from Brience.
> > > It's interesting because it has a section title of "Bye-Bye
> > > Struts". The
> > > section starts out as follows:
> > >
> > > "While the Struts framework is a powerful idea, it is not yet
> > > a product.
> > > Although excellent in dealing with Web-based applications,
> > > Struts is not
> > > ready to take on EJB."
> > >
> > > There are other gems in the article but I won't reproduce
> > > them all here.
> > >
> > > The premise of the article is that the author went looking for an
> MVC
> > > framework. He found the Blueprint document and liked that but
> > > it was too
> > > complicated. He then found Struts but apparently it didn't
> > > meet his need for
> > > "a reusable implementation of the MVC pattern." Prashant must
> > > be a hard man
> > > to please. I think he wants one framework that can be used
> > > for both web
> > > applications and desktop applications. Personally I would
> > > rather share the
> > > model components and let my MVC framworks be a little less
> > > abstract and more
> > > useful to the task at hand.
> > >
> > > I couldn't find the article on-line. I just skimmed the rest
> > > of the article
> > > because it it was hard to concentrate or take it seriously
> > > after the Bye-Bye
> > > Struts section.
> > >
> > > Hal
> > >
> >
>
