Thank you for making that very clear! :)
It would be great to have another level eventually, until then please do
what you must to get all of them displayed.
Thanks!
Ken
Kim Haase wrote:
> On 11/04/09 14:47, Ken Paulsen wrote:
>>
>> Hi Kim,
>>
>> I don't think I fully understand what is being asked here. Can you
>> give a comparison of before/after your proposed change?
>
> Our genhtml command has a limit of 4 levels of TOC. So right now all
> we see is (for example)
>
> Enterprise Server Administration Console Reference
> Resources
> JDBC
> Connection Pools
> JDBC
> JDBC Resources
>
> There are several topics under Connection Pools and JDBC Resources,
> but they aren't visible. To make them visible I have to put all of
> them directly under JDBC. In the TOC, once alphabetized, they would
> look like this.
>
> Enterprise Server Administration Console Reference
> Resources
> JDBC
> Connection Pools
> Edit Connection Pool
> Edit Connection Pool Advanced Attributes
> Edit Connection Pool Properties
> Edit JDBC Resource
> JDBC
> JDBC Resources
> New JDBC Connection Pool (Step 1 of 2)
> New JDBC Connection Pool (Step 2 of 2)
> New JDBC Resource
> Properties Specific to JDBC Connection Pools
>
> Kim
>
>>
>> Thanks!
>>
>> Ken
>>
>> chaase3_at_dev.java.net wrote:
>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=10743
>>>
>>>
>>>
>>> User chaase3 changed the following:
>>>
>>> What |Old value |New value
>>> ================================================================================
>>>
>>> CC|'pauldavies'
>>> |'anilam,kenpaulsen,pauldav
>>> | |ies'
>>> --------------------------------------------------------------------------------
>>>
>>>
>>>
>>>
>>>
>>> ------- Additional comments from chaase3_at_dev.java.net Wed Nov 4
>>> 19:32:00 +0000 2009 -------
>>> In order to make deeper subtopics visible I'm going to have to
>>> flatten the
>>> organization of the OLH for reference topics so that, for example,
>>> all the JMS
>>> resources topics, or all the Network Config topics, appear on the
>>> same level.
>>>
>>> Allowing deeper nesting is a tools issue that can't be fixed right
>>> away.
>>>
>>> Is that going to be a problem, Ken?
>>>