We should have an update of the org.jboss.naming.JNDIBindingService that exists in AS6, but apparently still only used and an mbean. Here are a couple of testsuite configuration files:

[38](ironmaiden:trunk) > cat testsuite/src/resources/client/urlbinding-service.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE server PUBLIC "-//JBoss//DTD MBean Service 4.0//EN"
          "http://www.jboss.org/j2ee/dtd/jboss-service_4_0.dtd">
<server>
  <mbean code="org.jboss.naming.JNDIBindingServiceMgr"
      name="jboss.tests:service=JNDIBindingServiceMgr">
      <attribute name="BindingsConfig" serialDataType="jbxb">
          <jndi:bindings
              xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
              xmlns:jndi="urn:jboss:jndi-binding-service:1.0"
              xs:schemaLocation="urn:jboss:jndi-binding-service:1.0 resource:jndi-binding-service_1_0.xsd"
              >
              <jndi:binding name="SomeWebSite">
                  <jndi:value type="java.net.URL">http://www.somesite.com</jndi:value>
              </jndi:binding>             
          </jndi:bindings>
      </attribute>
  </mbean>
 
</server>

[40](ironmaiden:trunk) > cat testsuite/src/resources/xml/mbeanserver/testBinding.xml
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: testBinding.xml 34236 2005-07-29 13:25:44Z starksm $ -->

<!-- An example legacy jboss-service.xml that contains an attribute type from
an unknown namespace with a schmema binding unknown to the SARDeployer.
-->
<server>
   <mbean code="org.jboss.naming.JNDIBindingService"
         name="jboss.tests:service=JNDIBindingService">
      <attribute name="Bindings" serialDataType="jbxb">
         <jndi:bindings
            xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
            xmlns:jndi="urn:jboss:jndi-binding-service"
            xs:schemaLocation="urn:jboss:jndi-binding-service jndi-binding-service_1_0.xsd"
            >
            <jndi:binding name="ctx1/key1">
               <jndi:value>value1</jndi:value>
            </jndi:binding>
            <jndi:binding name="ctx1/user.home">
               <jndi:value>${user.home}</jndi:value>
            </jndi:binding>
            <jndi:binding name="ctx1/key2">
               <jndi:value type="java.net.URL">http://www.jboss.org</jndi:value>
            </jndi:binding>
            <jndi:binding name="ctx2/key1">
               <custom:properties xmlns:custom="urn:jboss:custom-object-binding"
                  xs:schemaLocation="urn:jboss:custom-object-binding custom-object-binding.xsd">
                  <custom:property>
                     <custom:key>key1</custom:key>
                     <custom:value>value1</custom:value>
                  </custom:property>
                  <custom:property>
                     <custom:key>key2</custom:key>
                     <custom:value>value2</custom:value>
                  </custom:property>
               </custom:properties>
            </jndi:binding>

            <jndi:binding name="hosts/localhost">
               <jndi:value editor="org.jboss.util.propertyeditor.InetAddressEditor">
                  127.0.0.1
               </jndi:value>
            </jndi:binding>

         </jndi:bindings>
      </attribute>
   </mbean>

</server>
[41](ironmaiden:trunk) >

http://community.jboss.org/wiki/JNDIBindingServiceMgr

On 4/9/11 1:06 AM, Jaikiran Pai wrote:
While looking into https://issues.jboss.org/browse/JBAS-9261 I realized that we don't currently have support for non java: namespace JNDI bindings. The example application in that JIRA has a reference to a resource (a EJB in this case via ejb-ref and ejb-local-ref) and that reference points to a lookup name "Blah" (which is outside of java: namespace). Pre-AS7 days we allowed EJBs and other resources to be bound outside of java: namespace and then allow ejb-ref to point to that binding. Currently, in AS7 which is backed by Services for jndi bindings, I don't see how to deal with that since we don't have Services for non java: namespaces. Looking at this http://community.jboss.org/wiki/JavaEEImplementationTechnicalRequirements wiki I don't see it being covered. How do we plan to support such deployments, in AS7? Or more specifically, will binding outside of java: be backed by MSC services?

-Jaikiran
_______________________________________________ jboss-as7-dev mailing list jboss-as7-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev