Dennis Kempin wrote:
Hello Ortwin,
* You mention "problems with JSP". What are they?
At first I tried to use JSP without any framework or taglib.
As you are coming from PHP that approach seems somehow natural, but of
course is totally wrong.
> In
contrast to templates JSP doesn't help much on seperating logic and
html code,
That's why we need webapp frameworks.
> because you still need comparatively much code to iterate
over Lists, or print out some text.
This is where taglibs come into play.
And I could not get used to the Model View Controller concept.
You said earlier that in your framework "All commponents have a
template and a class file". Template = View, Class file = Controller.
You also mentioned a persistence layer. You can not have a persistence
layer when your model is not separated from the rest. All this implies
you have implemented the MVC pattern in your framework. I don't see how
you can not get used to it then.
* Which frameworks do you mean and what's the problem with them?
I tried many of these GUI-Like Frameworks at first, but well I wanted
to create a small Discussion Forum, and these Frameworks have not
matched this target.
I also gave Tapestry a try. I really liked it, but I dont like this
Action, Objects and Methods instead of Pages and URLs concept.
The most other frameworks I tried implemented the MVC pattern
Because it's a natural and proven design that has evolved over the years
maybe?
> and used
a lot of xml configuration, and looked to me very complicated.
You got a point there. Many frameworks indeed rely on overly complicated
XML configuration and often offer no way around. But sometimes it's
worth diving into it because you get a lot in return - Spring's bean
factory for example.
* What does you framework make better?
Well I dont know if it is a subjective opinion of mine, but my target
is to make the development as easy as possible.
Sounds good.
I had this framework in a slightly different form nearly completly
implemented, used it and tried to make it easier whereever it was
possible. It was easy to implement a component that displays a paged
dataset, and reuse it with just one or two lines in the template.
Does it do anything else apart from being just "easy"?
Then my laptop HDD crashed and my last backup was a few weeks ago, so I
decided to reimplement it, and add a few new concepts.
Sounds sad, but doesn't answer my question.
I found it just -easy- to create pages with that framework, and when i
look at other framework i dont think that i would like them as much as
i liked my framework (well that is pretty much a subjective oppinion
of mine, but I find it hard to explain without examples).
* Why do you invent a proprietary XML scripting facility? JSTL is
standard and there are numerous development tools readily available.
I havent looked at JSTL that much, because it has gone to the trash in
my brain just with jsp.
I am afraid you completely missed the essence of JSP by this oversight.
I just looked around and think that i really should try to use it
instead of implementing my own template engine.
That would be reasonable.
well you dont disencourage me, but you make me think of special topic
of the framework, and that really helped me. thanks.
I hope that I get more comments on this
greetings
Dennis
Please pardon me for my basic english.
Your original request was that you would like to put your project into
Jakarta. Well, that's not simple. It needs a bit more than just a good
idea and intention. To make that happen the project technically needs to
go through the Incubator:
http://incubator.apache.org/incubation/Incubation_Policy.html
As you can see you need a "Champion" and get Jakarta as a "Sponsor".
Given the reluctant feedback to your request I doubt that you will find
sufficient support here. Maybe it's easier for you to put your project
on Sourceforge which can be done in a matter of days. There you get the
chance to build up a greater community and give people the chance to
actually look at your project. If the project is successful you can
always try Incubation. Many projects have been on Sourceforge before
they came to the ASF.
Kind regards
Ortwin Glück
--
[web] http://www.odi.ch/
[blog] http://www.odi.ch/weblog/
[pgp] key 0x81CF3416
finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
