I would ask the people who critisize AppFuse for two things:
1. Their experience using AppFuse and/or its frameworks.
2. Specific reasons why they don't recommend the frameworks.
People like to critisize things they don't know or understand. Also,
you can discount the opinion of anyone who recommends using Struts 1
to build web applications.
You might also ask these architects what they think of Rails and
Grails. They're nice frameworks too.
Matt
On Aug 11, 2008, at 8:31 AM, krishgy <[EMAIL PROTECTED]> wrote:
Hi All,
We are doing our first web application :-) in our company.
I have 6 years of working experience in VC++, .NET and Python.
I have chosen the Appfuse framework & maven and created initial
application
to help our junior developers.
I don't work on Java projects on full time.
Our developers are very fresh engineers and who couldn't hope up
with the
project due to lack of experience or learning curve.
My choices (Maven, AppFuse, Struts, Hibernate and Spring) have been
criticized (kind of) by Java architects (3 people) who have more
than 8-12
years of working experiences.
They never explained me whats wrong with these frameworks. All of
them told
that all the frameworks won't suit together. All of them told that
hibernate
is for large & complex projects but not suitable for small projects
like us.
For me, hibernate is kind of life saver, saves our time from
fighting SQL. I
have worked with ORM (from Python, Sqlalchemy) which is great and I
have
used for small and big projects.
Then we met another java architect who suggests that these
frameworks are
good and time saver.
First I don't understand how experienced Java people differs their
opinion
on known, proven frameworks.
Then I started realizing their background. People who hates Maven,
AppFuse,
Struts, Hibernate and Spring are from service companies and the guy
who love
these frameworks is from product based company.
Here are my open question for people in this community who works for
service
and products.
1. Is learning these frameworks take too much of time?
2. Are these frameworks are self killer weapon? I don't know how to
explain
that. (We have a myth that there is special weapon which either
kills enemy
or ourself). These frameworks will kill the product?
3. Experienced people (architect) are telling that they can create
performance centric application in Struts without using Spring and
Hibernate. But for me Spring and Hibernate and the way appfuse
integrate
them seems like a time saver or more than life saver.
4. Are there any difference between the people who works for
products or who
works for services?
One different I can feel that service based companies create shit
product at
the end of the delivery because customer what the same by given the
deadline. So people in service may hesitant to take risk to use or
learn
these framework themselves (until and unless the customer explicitly
mention
to use a specific framework).
Product based companies need to maintain their code for years, so
they try
to make code smart and clean(less code).
How people here are feeling so?
I am sorry, If my post is irrelevant to this forum. I am not
trolling here.
When architects mentioned about Appfuse which itself a problem, I
really
don't understand why. I try to understand what is behind that?
Regards,
Krish
--
View this message in context:
http://www.nabble.com/Appfuse-%28Basic-Struts-%2B-Spring-%2B-Hibernate%29-tp18926990s2369p18926990.html
Sent from the AppFuse - User mailing list archive at Nabble.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]
