3:06 a.m.
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
11:59 a.m.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
12:13 p.m.
On 04/09/2011 03: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?
Bindings outside of "java:" will not be backed my MSC services as we
have no way of controlling what is bound and when. We certainly could
support binding outside of "java:" but it's not really clear what the
semantics (or use cases) are.
I examined the example app and didn't find the lookup reference you're
referring to, but wouldn't it be a relative lookup regardless? Unless
they specified a URL scheme in the first segment that is?
--
- DML
12:35 a.m.
On Saturday 09 April 2011 10:43 PM, David M. Lloyd wrote:
Bindings outside of "java:" will not be backed my MSC services as we
have no way of controlling what is bound and when. We certainly could
support binding outside of "java:" but it's not really clear what the
semantics (or use cases) are.
I examined the example app and didn't find the lookup reference you're
referring to, but wouldn't it be a relative lookup regardless? Unless
they specified a URL scheme in the first segment that is?
First we (used to) allow
EJBs to be bound to JBoss specific (non java:)
jndi name (Keks and KeksLocal in this example) via the jboss.xml of the
ejb jar:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC
"-//JBoss//DTD JBOSS 5.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd">
<jboss>
<enterprise-beans>
<session>
<ejb-name>GeometricModelBean</ejb-name>
<jndi-name>Keks</jndi-name>
<local-jndi-name>KeksLocal</local-jndi-name>
</session>
</enterprise-beans>
</jboss>
Then we allow a ejb-ref/ejb-local-ref of the bean to point to this jndi
name. In this case the ejb-ref is in the web.xml. The jboss-web.xml of
the war allows for specifying the lookup name:
<jboss-web>
<ejb-ref>
<ejb-ref-name>ejb/GeometricModel</ejb-ref-name>
<jndi-name>Keks</jndi-name>
</ejb-ref>
....
<!-- EJB Local References -->
<ejb-local-ref>
<ejb-ref-name>ejb/GeometricModelLocal</ejb-ref-name>
<local-jndi-name>KeksLocal</local-jndi-name>
</ejb-local-ref>
</jboss-web>
That jndi-name/local-jndi-name gets translated to lookup name of the
ejb-ref/ejb-local-ref.
-Jaikiran
3:42 a.m.
For the moment we should *not* support this. Not only would it require
binding outside of java: space, but also combined proxies. There will be
more cases in which we're no longer backwards compatible with AS 5/6.
If we can do MSC services with outside bindings (and we have combined
proxies) then it should simply be a service that binds some LinkRefs.
Carlo
On 04/10/2011 07:35 AM, Jaikiran Pai wrote:
On Saturday 09 April 2011 10:43 PM, David M. Lloyd wrote:
> Bindings outside of "java:" will not be backed my MSC services as we
> have no way of controlling what is bound and when. We certainly could
> support binding outside of "java:" but it's not really clear what the
> semantics (or use cases) are.
>
> I examined the example app and didn't find the lookup reference you're
> referring to, but wouldn't it be a relative lookup regardless? Unless
> they specified a URL scheme in the first segment that is?
First we (used to) allow EJBs to be bound to JBoss specific (non java:)
jndi name (Keks and KeksLocal in this example) via the jboss.xml of the
ejb jar:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC
"-//JBoss//DTD JBOSS 5.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd">
<jboss>
<enterprise-beans>
<session>
<ejb-name>GeometricModelBean</ejb-name>
<jndi-name>Keks</jndi-name>
<local-jndi-name>KeksLocal</local-jndi-name>
</session>
</enterprise-beans>
</jboss>
Then we allow a ejb-ref/ejb-local-ref of the bean to point to this jndi
name. In this case the ejb-ref is in the web.xml. The jboss-web.xml of
the war allows for specifying the lookup name:
<jboss-web>
<ejb-ref>
<ejb-ref-name>ejb/GeometricModel</ejb-ref-name>
<jndi-name>Keks</jndi-name>
</ejb-ref>
....
<!-- EJB Local References -->
<ejb-local-ref>
<ejb-ref-name>ejb/GeometricModelLocal</ejb-ref-name>
<local-jndi-name>KeksLocal</local-jndi-name>
</ejb-local-ref>
</jboss-web>
That jndi-name/local-jndi-name gets translated to lookup name of the
ejb-ref/ejb-local-ref.
-Jaikiran
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
6:25 a.m.
On Monday 11 April 2011 02:12 PM, Carlo de Wolf wrote:
For the moment we should *not* support this. Not only would it
require
binding outside of java: space, but also combined proxies.
By combined proxies, I
guess you mean a proxy which is usable for all
(EJB3.x) exposed views of a bean. Yeah, we don't have that now in AS7.
And yes, except for backward compatibility, I don't see a usecase for
combined proxies.
-Jaikiran
There will be more cases in which we're no longer backwards
compatible
with AS 5/6.
If we can do MSC services with outside bindings (and we have combined
proxies) then it should simply be a service that binds some LinkRefs.
Carlo
On 04/10/2011 07:35 AM, Jaikiran Pai wrote:
> On Saturday 09 April 2011 10:43 PM, David M. Lloyd wrote:
>> Bindings outside of "java:" will not be backed my MSC services as we
>> have no way of controlling what is bound and when. We certainly could
>> support binding outside of "java:" but it's not really clear what
the
>> semantics (or use cases) are.
>>
>> I examined the example app and didn't find the lookup reference you're
>> referring to, but wouldn't it be a relative lookup regardless? Unless
>> they specified a URL scheme in the first segment that is?
> First we (used to) allow EJBs to be bound to JBoss specific (non java:)
> jndi name (Keks and KeksLocal in this example) via the jboss.xml of the
> ejb jar:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE jboss PUBLIC
> "-//JBoss//DTD JBOSS 5.0//EN"
> "http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd">
> <jboss>
> <enterprise-beans>
> <session>
> <ejb-name>GeometricModelBean</ejb-name>
> <jndi-name>Keks</jndi-name>
> <local-jndi-name>KeksLocal</local-jndi-name>
> </session>
> </enterprise-beans>
> </jboss>
>
> Then we allow a ejb-ref/ejb-local-ref of the bean to point to this jndi
> name. In this case the ejb-ref is in the web.xml. The jboss-web.xml of
> the war allows for specifying the lookup name:
>
> <jboss-web>
> <ejb-ref>
> <ejb-ref-name>ejb/GeometricModel</ejb-ref-name>
> <jndi-name>Keks</jndi-name>
> </ejb-ref>
> ....
>
> <!-- EJB Local References -->
> <ejb-local-ref>
> <ejb-ref-name>ejb/GeometricModelLocal</ejb-ref-name>
> <local-jndi-name>KeksLocal</local-jndi-name>
> </ejb-local-ref>
> </jboss-web>
>
> That jndi-name/local-jndi-name gets translated to lookup name of the
> ejb-ref/ejb-local-ref.
>
> -Jaikiran
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
8:56 a.m.
On Saturday 09 April 2011 10:43 PM, David M. Lloyd wrote:
Bindings outside of "java:" will not be backed my MSC services as we
have no way of controlling what is bound and when.
Wouldn't it be possible if
the bindings outside java: were always done
by a specific MSC service (like porting the JNDIBindingService which
Scott pointed to)?
-Jaikiran
11:55 a.m.
On 04/10/2011 08:56 AM, Jaikiran Pai wrote:
On Saturday 09 April 2011 10:43 PM, David M. Lloyd wrote:
>
> Bindings outside of "java:" will not be backed my MSC services as we
> have no way of controlling what is bound and when.
Wouldn't it be possible if the bindings outside java: were always done
by a specific MSC service (like porting the JNDIBindingService which
Scott pointed to)?
Yes, it would be possible, but there should be no reasonable expectation
that the JNDI context which backs non-"java:" bindings is an in-memory
context like "java:" is. That's why the URL scheme should be present.
I think we could also look at treating these names as relative though.
So for example they could be relative to "java:jboss/user/". This way
they are still in "java:" even if they don't explicitly say so. If we
wanted to support this from a lookup perspective though, that could get
tricky, though maybe we could just apply the same logic there.
--
- DML
5:38 a.m.
On 04/11/2011 06:55 PM, David M. Lloyd wrote:
On 04/10/2011 08:56 AM, Jaikiran Pai wrote:
> On Saturday 09 April 2011 10:43 PM, David M. Lloyd wrote:
>> Bindings outside of "java:" will not be backed my MSC services as we
>> have no way of controlling what is bound and when.
> Wouldn't it be possible if the bindings outside java: were always done
> by a specific MSC service (like porting the JNDIBindingService which
> Scott pointed to)?
Yes, it would be possible, but there should be no reasonable expectation
that the JNDI context which backs non-"java:" bindings is an in-memory
context like "java:" is. That's why the URL scheme should be present.
I think we could also look at treating these names as relative though.
So for example they could be relative to "java:jboss/user/". This way
they are still in "java:" even if they don't explicitly say so. If we
wanted to support this from a lookup perspective though, that could get
tricky, though maybe we could just apply the same logic there.
How do you want to handle remote clients lookups?
Carlo
9:45 a.m.
On 04/12/2011 05:38 AM, Carlo de Wolf wrote:
On 04/11/2011 06:55 PM, David M. Lloyd wrote:
> On 04/10/2011 08:56 AM, Jaikiran Pai wrote:
>> On Saturday 09 April 2011 10:43 PM, David M. Lloyd wrote:
>>> Bindings outside of "java:" will not be backed my MSC services as
we
>>> have no way of controlling what is bound and when.
>> Wouldn't it be possible if the bindings outside java: were always done
>> by a specific MSC service (like porting the JNDIBindingService which
>> Scott pointed to)?
> Yes, it would be possible, but there should be no reasonable expectation
> that the JNDI context which backs non-"java:" bindings is an in-memory
> context like "java:" is. That's why the URL scheme should be present.
>
> I think we could also look at treating these names as relative though.
> So for example they could be relative to "java:jboss/user/". This way
> they are still in "java:" even if they don't explicitly say so. If we
> wanted to support this from a lookup perspective though, that could get
> tricky, though maybe we could just apply the same logic there.
>
How do you want to handle remote clients lookups?
That depends on whether you're talking about in-VM or remote, external
clients.
For in-VM (and non-EE-app-client) clients we would obviously use our
current service-oriented system. App client would probably work the
same as remote: when the connection is established, we'll probably have
a Remoting service which will download a list of available names, and
set up a remote JNDI initial context if that's what the user wants.
Note that it still is theoretically possible for us to provide a
simplified remote client API as well, where a user can simply ask for an
EJB view by name and get it back without hitting JNDI at all.
--
- DML
5005
days inactive
5008
days old
9 comments
4 participants
participants (4)
-
Carlo de Wolf -
David M. Lloyd -
Jaikiran Pai -
Scott Stark