Just an update: the problem seems to be solved in JBoss 4.0.2 RC1.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872129#3872129
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872129
--
Darranl,
Thanks a lot for your time taken to respond to me. Sounds like exactly my
problem (JBAS-1495). I will look into it to see if JBoss suplied a fix for this
or not. I just wanted to thank you for you kind responses.
Cheers,
Art.
View the original post :
http://www.jboss.org/index.html?mod
I think the following issue is the same as the problem you are encountering: -
http://jira.jboss.com/jira/browse/JBAS-1442
Can you try your code that reproduces the problem on JBoss 4.0.2 RC1.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871584#3871584
Rep
The JNDI name of the session bean: SomeSBHomeRemote.JNDI_NAME (which is: public
static final String JNDI_NAME="ejb/SomeSBRemote";) So it will be the same
deployed on the local box and the remote box, and the session bean is deployed
on box computers. But on the local box I am using a InitialCont
What is the String that you are passing into the call to lookup?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871366#3871366
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871366
I found what was it: even though i am using a different InitialContext (created
to point to the remote box), the Session bean B 's JNDI name existing localy in
the ENV it takes over, and any lookups (even using different InitialContext's)
is done using this exisiting jndi name. I wonder if this
I am having a strange problem. Let me describe it shortly.
I am having a simple java class, lets call it MyUtil. This class does a
jndi = new InitialContext( props ) in the constructor and uses this "jndi"
object to look up a remote home of a session bean, and then create a reference
to the remo
Ok I have had a look at passivation of JNDI ENC references, here is the session
bean that I have created: -
package com.darranl.encstateful.implementation;
|
| import javax.ejb.CreateException;
| import javax.ejb.EJBException;
| import javax.ejb.SessionBean;
| import javax.ejb.SessionC
Ok, I will have a look this, I will get back to you tomorrow.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870964#3870964
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870964
---
I am sorry to say it but I am not convinced about the quality of this.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870959#3870959
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870959
--
darranl,
This is not working either!
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870958#3870958
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870958
---
SF emai
Yes it does look as if you may have found a mistake in the book. The only
definitive guide is the EJB specification available for download from Sun.
>From oreilly the session bean chapter can be downloaded for free for the 4th
>edition. The example does show as you say that the InitialContext
[EMAIL PROTECTED], so why then the Enterprise Java Beans, second edition (can
be found on http://safari.oreilly.com) they state that the Context
(InitialContext) should be dealt with by the container? Even the examples they
give the Context is not transient, nor they deal with it in the Active a
oabidian, You may want to go back and have a look at the EJB specification it
may help your understanding of the requirements of the container.
In the EJB 2.1 specification section 7.4.1 there is a list of the items that
can be referenced by a bean that is being passivated, the item relating to
Try reading the ejb spec more carefully. There is no requirement to passivate
an InitialContext. The spec states that there is a requirement to passivate the
Context corresponding to ENC:
anonymous wrote :
| A reference to the environment naming context (that is, the java:comp/env
JNDI conte
What a smart reply: "why arent people read the stack trace?". That exception
should not be happening: when a bean is passivated , the JNDI ENC must be
maintained as part of the bean's conversational state. And it is the duty of
the container.
I wish JBoss would one day work properly.
Not to men
When will people start to read the stack traces that they post on these forums?
java.io.NotSerializableException: javax.naming.InitialContext
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840125#3840125
Reply to the post :
http://www.jboss.org/index.html?m
17 matches
Mail list logo
