Hello,
Im debating which framework to choose for my next project. I will not
be using EJB if that makes any difference. Having no experience in
either, which has more developer adoption. I know that they have a
eclipse plugin for Struts. How about Spring?
Thanks,
--Anna
Dmitry R - 24 Apr 2004 22:09 GMT
Are you restricted only selection from this two frameworks? Why I 'm
asking because neither is good in my opinion. I need also to know a
bit more about your project. What type of page you need to generate,
how big they, are they form, or report like, user authentication m
echanism and so on. I'd recommend to look in Tapestry.
> Hello,
>
[quoted text clipped - 5 lines]
> Thanks,
> --Anna
J - 27 Apr 2004 05:19 GMT
> Are you restricted only selection from this two frameworks? Why I 'm
> asking because neither is good in my opinion. I need also to know a
> bit more about your project. What type of page you need to generate,
> how big they, are they form, or report like, user authentication m
> echanism and so on. I'd recommend to look in Tapestry.
I agree with Tapestry. It is a simple way of looking at pages and dealing
with java objects then other frameworks. Personally I like it better than
Struts, but the learning curve is much higher. But once you get it, then
creating pages get simpler and faster.
J
Sudsy - 25 Apr 2004 02:46 GMT
> Im debating which framework to choose for my next project. I will not
> be using EJB if that makes any difference. Having no experience in
> either, which has more developer adoption. I know that they have a
> eclipse plugin for Struts. How about Spring?
Spring is coming! Finally!
But seriously, Struts seems to have more buy-in than any other
framework out there for MVC architectures. JavaServer Faces is
a contender, especially since Craig McClanahan is a senior
architect on that project. (Check his pedigree)
Jason Bell - 25 Apr 2004 10:08 GMT
Anna
First of all before you do anything, look at the size of the project. If
it's a small site then Struts, Spring and any other MVC framework are
basically overkill for most needs.
I've managed to steer away from dependency heavy frameworks by using my well
developed plain old Java objects (POJO's).
A Bean -> A Factory Manager -> A Data Access Object (DAO)
Regards
Jase
> Hello,
>
[quoted text clipped - 5 lines]
> Thanks,
> --Anna
P.Hill - 27 Apr 2004 17:16 GMT
> I've managed to steer away from dependency heavy frameworks by using my well
> developed plain old Java objects (POJO's).
>
> A Bean -> A Factory Manager -> A Data Access Object (DAO)
This sounds like a good approach. I'd like to hear a little
more about your particular version.
It it the case that the bean appears to just have access methods,
but it not only could hold data, it also can go out to factories
to get DAOs which can be queiried by the Bean to provide the
actual data. Is that a fair description or does all data come out
of a factory which hide the DAOs, so beans just talk to
Factory Manager as your arrows imply?
A Bean -> A Factory Manager
to get a Factory
A Bean -> Factory
to get a DAO
A Bean -> DAO
to get data.
Is the DAO a singleton?
-Paul