Ming Fai wrote: >i've two odd questions, > >1. can I use Jetspeed without Turbine? >2. can I just use Portlet API of Jetspeed? (hopefully, the future JCP >Portlet API standard) > >basically, two questions are the same. > >what i mean is not leaving the Turbine features there without touching them. >But to take out the Jetspeed library and use it elsewhere. Take the >simpliest case, I want to make a simple site in sgml, and I use jsp to >render the sgml to html by the jetspeed library. Is it possible? > Jetspeed depends a lot on turbine:
- The turbine layout mechanism (layout, navigations, screen, actions, rundata) is used. - Quite a few services (userManagement, rundata, object pools, ...) - The current portlet api is dependent on turbine (this should change when we go portletAPI) There is no such thing as a Jetspeed library. You can have an idea with the Servlet API. What you would call Servlet library is a Servlet Container (like Tomcat, Resin, Caucho, JRun). Currently there is no standard so that you can exchange portlets between different servers (like in the Servlet API). This is what the jsr-162 and jsr-167 are about. For what you are looking currently, a publishing framework like Cocoon can help you (again, no library). But still you will miss some features thar are present in Jetspeed and Turbine. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
