Hi,
I see the overnight changes for the protocol edit pages in today's
nightly build.
I was wondering if the implementation team realized that you have
organized these in a very unorthodox way.
Typically, tabs are used on the pages for an object that users do not
create themselves: the Application Server (which comes with 4 tabs, some
of which have sub-tabs), the Web Container (4 tabs), the Update Tool,
and formerly the HTTP Service.
For objects that users create themselves, the Edit pages normally look
like the create pages for those objects. The exception is when the
object is complex and there are a couple of create pages. In that case
there is more than one create page, and the edit page is divided into
sections that reflect the results of the different create pages.
Examples of this are JDBC connection pools and (formerly) HTTP
listeners. In this case, the creation takes two pages but the results,
for editing, appear on one page.
For Protocols the pages are exactly the opposite of normal procedure.
The create page has panels that show the different parts of the
protocol. But the Edit pages have three tabs: Edit Protocol, HTTP, and
File Cache. This makes no logical sense and violates the design
principles of the Admin Console.
Kim Haase