Look at the correct dtd:
jboss-all 1380>grep local
server/src/resources/org/jboss/metadata/jboss_3_0.dtd
<local-jndi-name />
<local-jndi-name />
<!ELEMENT entity (ejb-name, jndi-name?, local-jndi-name?, read-only?,
home-invok
er?, bean-invoker?, configuration-name?, security-proxy?, ejb-ref*,
resource-ref
*, resource-env-ref*, clustered?, cluster-config?)>
<!ELEMENT session (ejb-name, jndi-name?, local-jndi-name?, home-invoker?,
bean-i
nvoker?, configuration-name?, security-proxy?, ejb-ref*, resource-ref*,
resource
-env-ref*, clustered?, cluster-config?)>
The JNDI name under with the local home interface should be bound
<!ELEMENT local-jndi-name (#PCDATA)>
when the client is local (same VM as the server). This optimizes RMI
calls.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Dmitri Colebatch" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, February 19, 2002 4:58 PM
Subject: Re: [JBoss-dev] ejb-local-ref broken?
> thanks...
>
> without wanting to be picky... any chance of updating the jboss.xml dtd to
allow the local-jndi-name? If there's a reason why this
> isn't so, then that reason would also be fine (o: Just as part of XDoclet
we validate the generated XML, and we cant do this for
> jboss.xml atm because the DTD doesn't agree with what we want...
>
> cheesr
> dim
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
