Tabs

Modifying the look and feel of the portal is extremely problematic and difficult. You have to play around with the files to figure out which ones "really" need modified, then, make sure you remove the pre-generated servlet files from the servers "tmp" folder to make sure you see everything you need to.

Also, because Sun uses <%@include %> versus <jsp:include /> in the templates, only the top-most .jsp file is compiled, so it's even more difficult to figure out which files you need to modify.

Maybe I'm just the abnormal one, but I have considerable development experience and it took me months to be able to figure out all of the spidery paths through the .jsp files before I could modify the templates with any skill.

dwyutzy at 2007-7-3 23:06:12 >

To help finding out what files need to be modified you can write a script which includes and HTML comment in each of them which shows the file name and path.

If you view the HTML source later on you will know exactly which file to change.

These comments has been there in former versions unfortunately they have gone.

Thalmayr at 2007-7-3 23:06:12 >

I have to agree with Jim. While its a pain to learn all the includes (yes, at one time there were comments, but, when they were there, they were often wrong) path especially the tableContainerProviders with multiple column support, it was certainly doable. I even went as far as to create my own extending from JSPProvider so I could better handle nested tab support.

Just like Jim mentioned, don't touch the default directory and use touch *.jsp. All JSP's are compiled when called, but its only the top level JSP that gets called to include the others. Therefore, you must remember to touch that top page.

Wes

wtreisz1 at 2007-7-3 23:06:12 >