Actually it does not work .. here's a patch, that fixes at least the local
ejb-links. Mappings, that are specified in jboss.xml are not supported as
of the current implementation. Somebody else posted the same bug, see
jboss-Bugs-520454.
There's another problem left with ejb-links, that span
I'm working on some other modifications to Container and I will apply this
patch (if no one objects).
I think there is a big problem with the deployment order. Right now with
an ear that contains many ejb jars we deploy the jars individually in a
more or less random order. I believe we need
On Wed, 20 Feb 2002, David Jencks wrote:
I'm working on some other modifications to Container and I will apply this
patch (if no one objects).
I think there is a big problem with the deployment order. Right now with
an ear that contains many ejb jars we deploy the jars individually in a
, February 20, 2002 8:03 AM
Subject: Re: [JBoss-dev] ejb-local-ref broken?
On Wed, 20 Feb 2002, David Jencks wrote:
I'm working on some other modifications to Container and I will apply
this
patch (if no one objects).
I think there is a big problem with the deployment order. Right now
On 2002.02.20 11:03:46 -0500 Holger Engels wrote:
On Wed, 20 Feb 2002, David Jencks wrote:
I'm working on some other modifications to Container and I will apply
this
patch (if no one objects).
I think there is a big problem with the deployment order. Right now
with
an ear that
On Wed, 20 Feb 2002, Scott M Stark wrote:
The DeploymentInfo object groups all of the elements together in
a heirarchy of components. This object is not passed into the
method that creates these ejb links. We need to unify the objects
created to model the deployment and get rid of legacy
The object model is fine, but this should be in the deployment
package as it is the object model corresponding to the j2ee
+ jboss packages. It should not depend on any specific container
other than a reference to the container ObjectName.
The DeploymentInfo object groups all of the elements
).
otoh if it isn't from the web tier then this will have nothing to do with it (o:
cheesr
dim
- Original Message -
From: Scott M Stark [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 20, 2002 9:32 AM
Subject: Re: [JBoss-dev] ejb-local-ref broken?
You'll have
: Tuesday, February 19, 2002 2:02 PM
Subject: [JBoss-dev] ejb-local-ref broken?
Is ejb-local-ref broken? I haven't changed my bean, client, or ejb-jar
file
for weeks and everything worked with a week+ old version of jboss3. Now,
when I go to look up an entity bean referenced in a session bean
: Tuesday, February 19, 2002 2:35 PM
Subject: Re: [JBoss-dev] ejb-local-ref broken?
If its from the web-tier, AbstractWebContainer assumes that the local
interface is bound to local/{remote_interface_name} in JNDI.
I thought I'd submitted a patch last night for this (to look for
local-jndi-name
the DTD doesn't agree with what we want...
cheesr
dim
- Original Message -
From: Scott M Stark [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 20, 2002 11:33 AM
Subject: Re: [JBoss-dev] ejb-local-ref broken?
I'll fix the AbstractWebContainer so forget about the patch
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
Subject: Re: [JBoss-dev] ejb-local-ref broken?
Look at the correct dtd:
jboss-all 1380grep 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
13 matches
Mail list logo
