When will the Portlet API v2 be (fully) integrated in Jetspeed? What are the next major steps until the release of at least a beta version?
Will Jetspeed become the reference implementation of a Portlet API with pluggable services so that IBM's Portal Server is based on that common core and offers additional/improved services? Unfortunately with Jetspeed v1.3a2 I ran into bug #5442 (jsp templates in parity with Velocity templates). I have a feeling that since Velocity is now the default template mechanism the JSP templates won't be _really_ maintained anymore. What about using the Velocity veltag JSP tag library to keep the maintenance effort required to keep both in sync at a minimum? I really like the Portlet API v2 design (escpecially the Portlet events) and would like to start with Jetspeed. But the lack of documentation for the current 1.3a2 is frustrating me right now. Maybe the available docs should include a version note since the "Portlet Howto" and the "Configuration Howto" at bluesunrise.com are deprecated... (our fallback portal server will be ATG 5.5 if I didn't manage to get the Jetspeed portlet samples and a custom portlet using JSP up and running soon ;-) btw, does anybody knows what the attitude of companies like ATG or BEA is concerning a standard Portlet API? Thanks, Eike -- Accept-Language: de, en, Java, XML, fr;q=0.1 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
