?
-Original Message-
From: Alexey Loubyansky [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 4:37 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JNDI Name
Everything under 'java:/' is not remotely accessible.
alex
Rod Macpherson wrote:
JBoss is binding my datasource just fine
Okie dokie.
Thanks,
Rod
-Original Message-
From: Alexey Loubyansky [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 28, 2003 2:56 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JNDI Name
No, you have to expose some interface yourself to access it remotely.
alex
Rod Macpherson
Title: Message
The
java:/ context is only available within the same VM as the
server.
--
Danny Yates
-Original Message-From: Rod Macpherson
[mailto:[EMAIL PROTECTED] Sent: 27 August 2003
00:12To: [EMAIL PROTECTED]Subject:
[JBoss-user] JNDI Name
JBoss is binding
Everything under 'java:/' is not remotely accessible.
alex
Rod Macpherson wrote:
JBoss is binding my datasource just fine and my webapp works but trying
to connect from a stand-alone client outside of the server fails:
14:25:52,704 INFO [FoobarDS] Bound connection factory for resource
, August 27, 2003 4:37 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JNDI Name
Everything under 'java:/' is not remotely accessible.
alex
Rod Macpherson wrote:
JBoss is binding my datasource just fine and my webapp works but
trying
to connect from a stand-alone client outside of the server
Thanks a lot. Danch. Now, I am using: ctx.lookup(java:/Customer) and change
java:/DefaultDS to java:/Customer, my lookup code works fine. So I assumed if i
change java:/Customer back to java:/DefaultDS, I also can lookup for
java:/DefaultDS.
I will try to use java:comp/env/jdbc/Custmoer and the
You're close! See comments inline below.
-danch
Christine wrote:
Sorry for miscopy in my previous email!
The code in my function is :
javax.naming.Context ctx = new InitialContext();
DataSource dbs = (DataSource) ctx.lookup(jdbc/Customer);
the name should be
Why should jdbc/Customer be bound? if your code is in an ejb, you wouldn'
link from web.xml or jboss-web.xml but the ejb counterparts. If its in a
servlet, looks like you want to look up jdbc/MilosDataSource
david jencks
On 2002.03.01 18:44:41 -0500 Christine wrote:
Hi, Since I didn't get any
I am sorry to confuse you by my mistake. I have a database in MySQL called Customer,
which is specified in jboss.jcml.
mbean code=org.jboss.jdbc.XADataSourceLoader
name=DefaultDomain:service=XADataSource,name=MySQLDS
attribute name=PoolNameDefaultDS/attribute
attribute
Find it as an mbean, I don't think it is or should be in jndi. You can see
how to do this from a client (from a server is almost the same, but
simpler) in the (rabbithole) testsuite//test/JBossTestServices.java
file. If you are doing this from a client, the Connector class may be in a
So what you guys are saying is I should do this:
MBeanServer server = (MBeanServer)
MBeanServerFactory.findMBeanServer(null).iterator().next();
J2eeDeployer deployer = (J2eeDeployer)server.getObjectInstance(
service=J2eeDeployer );
Sorry about my misconception. I had based my understanding
]
Sent: Monday, September 17, 2001 5:10 PM
Subject: Re: [JBoss-user] JNDI name for J2eeDeployer?
So what you guys are saying is I should do this:
MBeanServer server = (MBeanServer)
MBeanServerFactory.findMBeanServer(null).iterator().next();
J2eeDeployer deployer = (J2eeDeployer
I haven't looked at the Castor stuff at all ever, but I suspect it uses
jndi binding because jndi is a required part of an app server whereas jmx
is not. This makes something using Castor not so jboss-specific.
However... I think the hot deploy is pretty jboss specific.
david jencks
On
Exactly the same problem. do you get some news !!
all my ejb are deployed with an old JNDI name,
if I specified in jboss.xml a JNDI name, they are not deployed!
Please help
Gianni
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Selvarajah
Vahees
Show your ejb-jar.xml and jboss.xml deployment descriptors.
- Original Message -
From: Selvarajah Vahees [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, May 31, 2001 1:27 AM
Subject: [JBoss-user] JNDI name bindings are not working properly on deployment
Hello folks,
I
Title: RE: [JBoss-user] JNDI name bindings are not working properly on deployment
You are talking about the OLD bean jndi. If you mean you've deployed a jar and all the jndi bindings were correct, then you changed something and restarted, but the changes don't seem to have effect...
Take
Title: RE: [JBoss-user] JNDI name bindings are not working properly on deployment
OK.fine that means if I am to make available my
bean classes to my JSPs in embedded Tomcat, I have to make another jar file
without DDs and put then in the classpath..right?
ok..lemme try
that
vahees
Your not declaring an ejb-ref in your ejb-jar.xml descriptor as required:
!-- EJB References (java:comp/env/ejb) --
ejb-ref
ejb-ref-nameejb/Actors/ejb-ref-name
ejb-ref-typeSession/ejb-ref-type
ejb-linkActors/ejb-link
18 matches
Mail list logo
