I am searching for an appropriate methodology for functionality deployed to a portal. This is a mix of code and file based configuration and "development" and configuration done through an administrative console. The latter may include permissioning, navigation definition, page creation, portlet instantiation, etc.
I am having tough time establishing an effective methodology for this type of development. It also makes controlled repeatable deployment problematic at best when an elevation consists of a packaged deployment (WAR, jsr-168 portlet, etc), an export/import form one portal environment to another and a series of clicks a human.
Can anyone speak to this? Our development is purely Java and object oriented on top of a Java based portal (Vignette, formerly epicentric). Testing is also difficult for similar reasons.
Any thoughts?
Mike
Example?
Hi Mike,
Can you please explain what an effective methodology means to you? What I mean is, what are your pain points? What is the problem you are trying to solve? I thought it was deployment, but you say above that it also makes deployment problematic, so it is the bit before the also I'd like to understand.
If it's about the mix of code and file based configuration, that's fine. Can you elaborate a bit please. Give us an example. I'd be happy to work through this with you.
Jeff