You can use the html iframe tag to include the jsf/seam applications in your static or php stuff.
Frank Bitzer wrote on Dec 03, 2008 17:05:
should be integrated seamlessly
Heh heh good one :-)
I don't see the problem, if your pages have the extension .html JSF won't touch them.
Hope this helps!
You can do the login using a plain HTML form, then, redirect to the JSF/Seam portion of your site.
thank you for your answers, both your suggestions are very good. I will think about it.
Do you have some experiences in combining Tomcat (for serving JSF content) with Apache httpd (for static or PHP stuff)? Does this work without problems? Or is it probably the better alternative to let Tomcat serve the static HTML, too?
I think, only if Apache is in front of Tomcat and you save a network hop.
Otherwise, I can't imagine why Apache would be better than Tomcat at simply copying a file to the OutputStream. Again, if the file extension is HTML there is no scanning and interpretation of pages, they ae just served as is.
You also have to balance the cost of hardware against the complexity (cost) of development and deployment. It is much simpler if everything goes into a single war file which is deployed to Tomcat. On the other hand, if there are a large number of Flash or other media files to serve, it is probably more convenient to deploy them separately.
Anyways, this is all somewhat hypothetical, if it is really a concern why not set up both configurations and compare them with a tool like JMeter?
Well, the main disadvantage of Tomcat is that it can not serve PHP files (or am I wrong here?). It's not sure yet, but probably I will use the PHP templating engine Smarty.
But you are right, it's all hypothetical. In case I can afford some time, I will do some testing.