Hello,
I had been programming dynamic Websites with PHP the last few years until
I discovered Java, and all its advantages. But I had many problems
migrating to JSP, and tried many frameworks until I gave up and created an
own framework, that is easy to use even for ex-PHP developer (Targeting on
non commercial use, such as small dynamic websites up to discussion board.
I am not targeting on business use).
Now I made a complete redesign of the framework and I want to know if
there would be a chance to get that project into jakarta. I just want to
know if you think that its concept would match to jakarta, and what you
think about the concept in general.
Concepts:
Servlet/Module System:
I want to proved an own configuration file. I realized, that web.xml, its
servlet mappings and JNDI is pretty complicated to use. In the
configuration file the user can define servlets and modules. They can be
linked together by dependencies. An example:
<module name="persistence" class="PersistenceManager">
<dependency name="databasepool" module="localdb" />
</module>
<module name="localdb" class="DatabasePool">
<property name="driver" value="org.postgresql.Driver" />
<property name="url" value="jdbc://localhost/devarea" />
<property name="username" value="java" />
<property name="password" value="java" />
</module>
Well this configuration file does not have as much opportunities as the
web.xml but it is much easier to use.
Components/Pages:
Well this is a bit parallel to tapestry as I realized later. All
commponents have a template and a class file. The class file can assign
variables to the template at page creation and at each request. You can
insert component into other components, while pages are nothig else as a
component, without a parent component.
The template engine is based on xml, you can print variables with
${variablename} and you can iterate over lists, or use conditions using
<thor:if expression="$booleanVariable">...</thor:if> or even <table><tr
thor:foreach="$line in $list">....</tr></table>
Components are inserted in the template with the component tag
(<thor:component ...>). A component can take the same parameters as a
Module in the config file. You can assign depedencies and properties.
There will also be a small xml based content managment system and small
persistence framework, but that has to be implemented lateron.
please take some time to comment on this, i would really appreceate that
Dennis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
