amework provide a mechanism for the
templates? What about the idea to have the "page general look" (e.g.
page header, navigation) in just *one file* (clean HTML, because
designed by the designer), where the content is in the other markup
files (clean HTML, because designed by the designe
JSP mess.
>The other thing that is going wrong is that you are using JSF ;)
true :-) , it is was up to me .
Timo Stamm wrote:
tcolar schrieb:
That one kills me:
> Patrick (WebWork):
> "I've found that "HTML/CSS developers" and "app developers"
Exactly.
I found this same process (where the dsigner could do the desing
& HTML) much better by using velocity before, because the designer
*could change the design* without needing a developer.
Velocity wasn't perfect but that wasd a big step in the right direction
compare to JSP.
Tapestry
That one kills me:
> Patrick (WebWork):
> "I've found that "HTML/CSS developers" and "app developers" rarely
are >separated
>like Tapestry likes to pretend they are"
I could not disgree more with that, only geeks working on their ugly
homepage say this.
In large companies you have dev on one
Great article.
It reinforced my opinion that wicket, tapestry and stripes are the best
3 :-)
Eelco Hillenius wrote:
FYI, Matt Raible asked me to give my opinion about Wicket and some of
it's competitors. He presenting it tonight at the server side
symposium, and you can find his presentation
Tipycally i would leave the application server (tomcat, jetty) alone and
run in on port 8080 or whatever then have apache runnin on port 80 and 443.
then you configure apache ascially like this:
everything on port 80 goes to port 8080, except if it's /cart/* then
deny (or redirect to https://
