Hi Randy,
I have been able to implement all that you have pointed me. Thanks a lot for helping me out with this. I think I do get the idea of having document sets. Its a good concept.
I have a couple of confusions though.
- In the document sets, there is a <profile-locator>page</profile-locator>. I dont know what that is for.
- Also you wanted to explain me on how to get this more dynamic with the help of profiler. I guess you can shoot that and I will try to grasp the concept.
- (This is not so relevant to this discussion, but) the pages directory that we are talking about --- I still have to put it under <tomcatInstall>/webapps/jetspeed/WEB-INF/pages/... I asked a question before and David said I can have the pages under my own portlet webapp and access it on the internet with -- http://localhost:8080/jetspeed/portlet/myApp/myPage.psml I tried that and it did not work. This however is not that big of an issue, but just a nice thing to have...
Thanks, Amit
----Original Message Follows---- From: [EMAIL PROTECTED] Reply-To: "Jetspeed Developers List" <jetspeed-dev@jakarta.apache.org> To: "Jetspeed Developers List" <jetspeed-dev@jakarta.apache.org> Subject: Re: J2 - Menu Navigation - Root Folder Date: Thu, 17 Feb 2005 08:20:04 -0700 (MST)
Amit,
Sorry, I am pressed for time this AM, but here are a few pointers to get you started. I will be back online in a bit to help you further.
1. Look at the nested document sets in the J2 demo example and how they are rendered in the decorator velocity templates. I would suggest you use these to generate the products and customer areas. 2. The top level pages, (home, contact us, etc.) should be simply sibling pages. 3. The home.psml should probably be set to be the default page of the root folder.
So, this boils down to this under WEB-INF/pages:
/folder.metadata, (sets home.psml to default page) /home.psml /contact-us.psml /about-us.psml /products.ds, (regexp document path set to /products/*.psml) /customer-area.ds, (regexp document path set to /customer-area/*.ds) /customer-area/download-reports/*.psml /customer-area/download-reports.ds, (regexp document path set to /customer-area/download-reports/*.psml) /customer-area/comparison-tools/*.psml /customer-area/comparison-tools.ds, (regexp document path set to /customer-area/comparison-tools/*.psml)
Give this a try. We can discuss how to make this more dynamic using the profiler after you get a handle on this approach.
Hope this gets you started....
Randy
> Hi Randy,
>
> Here is the tree that I want to create for my website -
>
> - Home (psml)
> - Contact Us (psml)
> - About Us (psml)
> - Products (SubMenu)
> - Product 1 (psml)
> - Product 2 (psml)
> - Product 3 (psml)
> - Customer Area (SubMenu)
> - Download Reports (SubMenu)
> - Report 1 (psml)
> - Report 2 (psml)
> - Comparision tools (SubMenu)
> - Tool 1 (psml)
> - Tool 2 (psml)
>
>
>
>
> How should I lay it out and how should I write my decorator so that I can
> display this tree on the left as my navigation menu ...
>
> Thanks,
> Amit
>
>
> ----Original Message Follows----
> From: Randy Watler <[EMAIL PROTECTED]>
> Reply-To: "Jetspeed Developers List" <jetspeed-dev@jakarta.apache.org>
> To: Jetspeed Developers List <jetspeed-dev@jakarta.apache.org>
> Subject: Re: J2 - Menu Navigation - Root Folder
> Date: Wed, 16 Feb 2005 10:54:52 -0700
>
> Shah,
>
> Right.... the problem is that the API is not designed to allow arbitrary
> use
> of the getParent() method because the profiler does not construct a
> complete
> view of the site on each page request. The reason is that it can be costly
> generate views of the site that are not necessarily going to be visited by
> the user.
>
> Instead, we would expect this to be done using document sets. Perhaps it
> is
> easy, perhaps not. Can you please generate an example set of folders and
> pages you'd like to add to your layout and I'd be glad to assist.
>
> Thanks,
>
> Randy
>
> Shah Amit wrote:
>
>>Hi David,
>>
>>Reposing my question on the developer thread.
>>
>>The problem is org.apache.jetspeed.profiler.ProfiledPageContext interface
>>and all the other related interfaces are very convinient to navigate
>> child
>>elements. But it is tough to reach the "root" folder, or to traverse up
>> the
>>tree.
>>
>>Now the reason I need to traverse up the tree is because I need to
>> display
>>a "tabbed" menu interface which goes 3 levels deep. Something similar to
>>amazon.com. Now all the samples included in J2 display all the child
>>folders and sub-elements, but there is no example that basically displays
>>"everything" under pages directory in like a tree format and let user
>>choose where he wants to go.
>>
>>Would really appreciate any help.
>>
>>For now the I am thinking of workaround where I will go 5 levels down. I
>>dont think I need to worry for more than that. Also to reach the root
>>folder, I am using following macro -
>>
>>#macro(createTree $folder)
>> #set($parent = $folder.getParent())
>> #if($parent != "/")
>> #createTree($parent)
>> #else
>> #set($folder=$parent)
>> #end
>>#end
>>
>>Thanks for all your helps,
>>Amit
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
