Cos Naming & WLS Naming Service

Hi,

we have been starting our investigation into using the distributed application
feature of Tuxedo (multiple machines running under 1 Tuxedo domain which make up
the entire Tuxedo Application).
when trying to access WLS EJB object references from Tuxedo, we hit a road
block.

we have been using the standard method of searching through Cos Naming for a
bind context which refers to WLS Naming Service.  (this method is documented
online and in dev2dev samples)  Under non distributed application setup (1 Tux
domain with 1 machine as in all examples), everything works fine and I can see
into 1 WLS server's JNDI tree.  But when in distributed application setup where
we want to have two (for example) machines and we also want two WLS managed
server with each running on their own machine, it seems that there are some
unexpected problems:

1. - only one set of GWADM/GWTDOMAIN is running
    - each WLS managed server has its own WTC server
    - each WTC server has its own LOCAL ACCESS POINTs
    - each WTC server uses the single REMOTE ACCESS POINT
      (since only one GWTDOMAIN is running in this scenario)
    --> problem: only one of the managed server's JNDI tree can be traversed
into, and only one of the WTC link works for Cos Naming -> WLS Naming Service
resolution

2. - each machine is running their set of GWADM/GWTDOMAIN
    - in dmconfig, two local Tux domain-ids are defined, for the
two groups of GW
    - WTC server setup is identical to above; except
      each of the WTC is pointing to separate REMOTE ACCESS POINTs
    - when DOMAINID in ubbconfig is not defined, the same Cos Naming to WLS
Naming Service search fails.
    - when DOMAINID in ubbconfig is defined, the same Cos naming to WLS Naming
Service search fails with an CORBA:INTERNAL error.

Does anyone know how to get Cos Naming -> WLS Naming Service working properly
under a distributed Tuxedo application setup and also with multiple sets of
GWADM/GWTDOMAIN?