From: Ken Paulsen <Ken.Paulsen_at_Sun.COM>
Date: Tue, 03 Jul 2007 20:27:14 -0700

Hi Irfan,

Are you on the admin@glassfish email alias?  I cc'd you in case you're not.

Attached is my copy of peTree.jsf, you can just place this in the <glassfish-root>/lib/install/applications/admingui/adminGUI_war/ directory.  After doing this, you should still be able to login and see the tree, but no "SIP" tree nodes should exist.

Next, stop the server, place the attached sip.jar file in the <gf-roo>/lib/install/applications/admingui/adminGUI_war/WEB-INF/lib/ directory.  Restart the server and try again.  You should now see the a "SIP Modules" tree node w/ a "SIP Module" tree node under it.  Both should be clickable and show an almost empty page.  The pages should contain a BreadCrumb which should work and should keep the right-hand tree synch'd up.

Thanks,

Ken

Sreenivas Munnangi wrote:

Ken Paulsen wrote:

Hi Irfan,

I'm sorry I may have confirmed too late for you -- we tried the call, but I think you weren't expecting it.  We can try again, perhaps tomorrow the same time?  Anissa and Sreeni are interested in joining the discussion also.  Anissa, Sreeni, would tomorrow at 7:30PM PDT work for you?

Yes that works for me and thanks for organizing.

Thanks,

Ken

Ken Paulsen wrote:

Hi Irfan,

We can use this conference call #:

   (866)545-5227 (US Toll-Free)
   (865)673-6950 (International-Caller Paid)
   Access Code: 3535518# 

I'll join in @ 8:00 AM IST (7:30PM PDT).  We'll discuss the proposal below.


Thanks!

Ken

Irfan Ahmed wrote:

Hi Ken,

I am available early morning Tuesday, my time which is late Monday for you. What time shall we meet. I am assuming you are in SCA. In that case how about 7:30PM Monday (PDT) which is Tuesday 8:00AM (IST).

Warm Rgds
Irfan.

Ken Paulsen wrote:

(I added the admin@gf email alias)

Hi Irfan,

Thanks for writing this up.  The added Tab may not be doable for this release, but we can discuss this further.  I think we should be able to do the added tree nodes for both cluster and non-clusterd case.  For the issues, I'd like to make sure we address how this will work for the initial release as well as future releases.  I would like to know how we'll support newer versions of GF with the initial Sailfin "plugin".  We need to be careful in this area to avoid having a support issue.

Perhaps we can meet on Monday?  I can meet early my time (late Monday for you), or late Monday for me (early Tuesday for you).  Please suggest a time that works for you and we can discuss this more over the phone.  Also, I'm often avialable on IRC: irc.freenode.net #jsftemplating

Thanks!

Ken


Irfan Ahmed wrote:

Hi Ken,

Here is the proposal for pluggable admin GUI in Glassfish. Please tell me if I have to send the mail to admin@glassfish.dev.java.net.
------------------------------------------------------------------------------------------------------------------

The sailfin project leverages the Glassfish application server to provide SIP functionality to its users. However in-order to use the SIP functionality the Glassfish admin GUI needs to be enhanced to take care of SIP related configurations and properties. We do not want to modify the glassfish admin GUI for sailfin directly.

Hence I would like to propose to the team a concept of plugability for the Admin GUI. The Admin GUI will have hooks in place to read the new content from the classpath and display new screens to the user. The GUI tree code would have to be modified in-order to pick up the new content.

The hooks can be placed at present under Applications and Configuration (or a particular config under cluster mode). These are the two places where new screens for SIP functionality will appear eventually. The following is an example SIP functionality tree (I have listed the new screens only)

| Applications
-----| SIP Modules

| Configuration
-----| SIP Container
-----| SIP Service
      -----| SIP Listeners
             ----- sip-listener-01
            ----- sip-listener-02
      -----| SIP Link
      -----| SIP Timers
      -----| SIP Protocol Config

| Availability Service
-----| SIP Container Availability [This will appear as another Tab here]


The following are some of the issues that we will have to tackle immediately. I am sure there are going to be many more. We can discuss this once we start on this.

1. How will the screens be picked up and how will the code determine which screen appears where. For example the tree should know automagically that SIP Modules will come under Applications and SIP Container will come under Configuration.
2. We need to take care of screens that will show up only in a cluster configuration. For example HTTP Load Balancers, Availability Service.
3. How will the code deal with cases where the an existing screen needs to be updated with added functionality. For example Monitoring, Log Levels for SIP Container and Service.

Thanks and Warm Rgds,
Irfan.

--

Irfan Ahmed

Sun Microsystems Inc., Bangalore, India.

--------------------------------------------------------------------- To unsubscribe, e-mail: admin-unsubscribe@glassfish.dev.java.net For additional commands, e-mail: admin-help@glassfish.dev.java.net

--

Irfan Ahmed

Sun Microsystems Inc., Bangalore, India.

--------------------------------------------------------------------- To unsubscribe, e-mail: admin-unsubscribe@glassfish.dev.java.net For additional commands, e-mail: admin-help@glassfish.dev.java.net

--------------------------------------------------------------------- To unsubscribe, e-mail: admin-unsubscribe@glassfish.dev.java.net For additional commands, e-mail: admin-help@glassfish.dev.java.net

$page{configName}); /> $attribute{oldComp}); setAttribute(key="parent" value="#{oldComp.parent}"); // Replace it with something temporary to hold position // Needed, or it it will just find the old one vs. create it createComponent(type="staticText" component=>$attribute{temp}); replaceUIComponent(old="${oldComp}" new="$attribute{temp}"); // Rengenerate it getLayoutComponent(clientId="$requestParameter{updateTreeNode}" component=>$attribute{desc}); buildUIComponentTree(layoutElement="$attribute{desc}" parent="#{parent}" result=>$attribute{newComp}); replaceUIComponent(old="${temp}" new="$attribute{newComp}"); /> $page{treeId}); /> $attribute{encodedUrl}); redirect(page="webService/webServiceGeneral.jsf?webServiceKey=$attribute{encodedUrl}&webServiceName=#{click.parent.attributes.webServiceName}" ); /> "