I downloaded jetspeed version 1.3a2 because it was suggested that I get a copy of a recent version to eliminate class loading problems.
After some initial consternation with version 1.3a2, I find there are some great things that I really like about the direction that Jetspeed has taken. In the conf directory, the capability to have ones own portlet registration is a great thing. I have no idea how Jetspeed knows about user portlet registries. I looked to see if i could understand the principles involved - still no idea. But, it works great and I like it. I want to use Velocity for simple portlets and Cocoon fof complex portlets. I have tried to understand how to place Velocity into a portlet. I have examined demo-portlets.xreg I do not understand. I need to place Cocoon2 into other portlets. I want the pipeline feature of Cocoon. There was a CocoonPortlet avaiable in Jetspeed 1.3a1. I cannot find CocoonPortlet in 1.3a2 I really like the CardControllerPortlet. I believe it is poorly named because it is not relevant to portals. The CardStack in Java (Swing) applications is very useful. To have this capability in HTML is just the greatest. I like the version !.3a2 Tab Control. This is really great when you want to have a card stack of card stacks. A design can manage more information in a smaller footprint than any other method. I will turn off the TabControl on the main card stack - I want the navigation from the left .vm to cause navigation of the main CardControllerPortlet. I am still searching how to do this. The secondary card stacks will have their TabControl visible. After I have chosen my intial design using Jetspeed CardControllerPortlet, Velocity templates and Java classes, and Cocoon pipelines with generators and transformers - then, I will set my roles and permissions. On my site information may be viewed without logging in. Any creations or modifications of information will require authentication and ACLs to con trol permissions. I am hoping that i can secure my initial design without a total collapse. Any thoughts? In other words, I want to move through all of my informations screens and tag them with role permissions. I am hoping that Jetspeed does not hurt me bad by making me do a directory re-structure just to handle the permissions of my portlets (information views). When I have this design (using Jetspeed, Turbine, Torque, Velocity, Cocoon, and James) completed - it will be the most versatile design - one that I will be able to reuse many many times. I currently have three sites - hopefully more to the future. I hope to return the entire design to the open source community - WITH DOCUMENTATION. Thank you Apache Software Foundation. Thank you Jetspeed. Any pointers will be so greatly appreciated. thanx, Ray -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
