I am writing a review of different EIP implementations, and trying to analyze which "functionality" each framework provide.
The problem I'm facing with Jetspeed, is the documentation! I cannot seem to grasp the overview of Jetspeed, so if someone could clear up on a couple of problems I'm faced with, I would be very happy! If I obviously have missed some essential documentation, could someone please lead me to the light? ;) *) It seems like there are a couple of portlets present in the framework, and it looks to me like in the documentation that these are supposed to be enough for you, except if you have really weird needs. Is this so? Doesn't one break MVC somewhat by using Velocity template language in addition to the XML registiry stuff only to program new portlets? *) Is Jetspeed primarily designed to handle _viewing_ of enterprise data, that is to extract data from the underlying source, and then present it to the user? It seems a bit like this because of the "we have made 5 portlets for you that handle almost everything you'd want" approach. What about the Enterprise Application Integration concept, where portlets should expose some of an enterprise application's functionality? Or application-like functionality, e.g. implement a group calendar system or a simple CRM system like www.salesforce.com, directly in the portal system? *) The "instance" and "ref" types. What is this? Is it similar to the "instance" stuff talked about in this document: http://www-3.ibm.com/software/webservers/portal/doc/V41PortletDevelopmentGui de.pdf *) The actions. Are these supposed to take care of all your business logic needs? *) The "addressing" of the portlets. The hello-velocity portlet has some data that can be sent to it. 1) Where is the action defined? How is this configured? 2) How is it addressed? What if two portlets on the same screen had a submit button? *) "Porlet applications": are Jetspeed supposed to handle, at this stage, a ".par" file, where all the necessary stash is bundled into a file? Any help would be valued! Jetspeed isn't _that_ easy, with all the stuff coming from both turbine and jetspeed.. ;-) Endre. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
