David,
You wrote:
Our goal is to make all resources deployable:
- layouts
- decorators
- portlet applications
If you develop a portlet application, simply drop it into the auto
deploy directory
Got it. It appears that decorators/layouts can be similarly dropped into
the jetspeed/WEB-INF/deploy directory, no?
You are right, you should not edit the portal or components directories
unless you are planning on submitting a patch
However if you develop your own component, such as the Portal's
NavigationState Component or Aggregator Component for example, then
you can extend the existing Jetspeed component if necessary, and
develop your own component and assemble it in the jetspeed-spring.xml
You can also assemble pipelines of request execution in the
pipelines.xml, also based on Spring components
How would Jetspeed2 find my custom component classes/jars, (i.e. where
should these be installed)? I generally understand the configuration
being done in jetspeed-spring.xml and pipelines.xml. Would I edit these
configuration files in the deployed jetspeed/WEB-INF/assembly directly?
To create your own portal layout on a page, you will still need to
manually edit the PSML until our customizer is ready
We have made some progress in the customizer recently, but its still
not quite there
Right. Editing PSML is certainly not a big deal. I suppose adding and
deleting pages falls into the same category. However, I am still
hesitant to modify the deployed jetspeed webapp... is that the intended
development strategy? Obviously, there are numerous jetspeed
configuration and content files that one might wish to
edit/delete/create. I am trying to understand how to approach making
these changes in the jetspeed2 environment for a formal production
portal/development process, (despite the fact that jetspeed2 is just
entering first alpha). Basically, if I am going to write a tutorial for
the Wiki, I'd like to get it "right" from the start!
Thanks,
Randy Watler
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
