On 11/1/06, luiscolorado <[EMAIL PROTECTED]> wrote:
I think this is great stuff. However, I'm concerned about the development time... how much time did you spend doing this customization?
It probably took me about 3-4 weeks or so to: -get comfortable with building and deploying jetspeed -doing my custom skin -build my custom ATN/ATZ components to swap for jetspeed's default implementations The last step probably isn't absolutely necessary. I then spent maybe a week to build my custom user management portlet.
Did you basically download the source code and changed/extended/copied it as required?
I looked at the source yes. Jetspeed provides well-defined interfaces for the components I swapped out for authentication and authorization and the default implementations for LDAP served as a guide for me to write my own. Then it is a matter of changing two spring assembly files.
Now, I think that you probably have the best solution, but I just want to play devil's advocate: wouldn't it be faster or more convenient to have multiple deployments, and use scripts to copy/deploy files and configurations to the the multiple deployments? Wouldn't that, by the way, provide you the capability of using multiple servers more easily?
Just to be clear, the portal isn't really the core service that we are charging our customers for. If it were (ie. if we were a portal ASP), then yes, I would absolutely have multiple deployments rather than shared infrastructure. We are a VOIP service provider. The portal allows our customers to view and configure their services online as well as view reports and access other related application services. It is also used internally for us to provision and administrate our customers services. Thus, there are instances where we need a full view accross all customer data in a single place; hence, a single portal. The portal is also tightly integrated with many of our other internal systems as well as some 3rd party web services and I think multiple portals would just complicate things for us. We will need to setup a clustered environment soon (to distribute load), but we should be able to do that (since J2 is capable of that) without too much trouble. All that said, I'm sure in some cases (eg. a portal ASP) it might make sense to just have separate deployments.
Finally... did you look into any other projects, books, or any other resources I could look into.
Not really. I read the portlet spec (JSR 168) and a lot of the jetspeed documentation. I of course frequently reference tomcat documentation and the Java API docs. But that's about it really...
Thank you for an awesome post. Luis.
No problem, I hope it is helpful. -aaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
