Scott,
I understand that the CompositeName is suppose to be used for names that span
Namespaces, but is appears that in all cases TopLink generates
CompositeNames. The name that I am passing into their JNDIConnector is
java:/XATestDS, however I wrote a simple test and it does not matter
what I pass in I get back a CompositeName. It is easy to test, just download TopLink
9.0.3 from Oracle and use the following code:
JNDIConnector connector = new JNDIConnector(null,java:/XATestDS);
//or a valid context it is just a test.
javax.naming.Name name = connector.getName();
This code does not require a database or even JBoss up, it simply constructs a
JNDIConnector which is used by TopLink's
other classes to lookup data sources in JNDI. You will see that the name
implementation that is returned on the above
getName() call is the CompositeName. So the problem is that TopLink will always
attempt to use a CompositeName.
Thanks
Mike H. Sr.
Michael Huneycutt Sr.
TRC - A perotsystems* Company
Email: [EMAIL PROTECTED]
Office FL: (813) 891-6084 x47395
Office VA: (804) 934-0977
Cell: (804) 304-7655
URL: www.trcinc.com
www.perotsys.com
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user