Thanks,
I am using JBuilder 6 Enterprise (trial) and debugging using the Non-jpda
method described in the article that you mention.
I have managed to move on slightly from that problem, by changing the code
in the servlet to:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.evermind.server.ApplicationClientInitialContextFactory");
env.put(Context.PROVIDER_URL, "http://localhost/flexisale2";);
// Get the initial JNDI context using our settings
Context context;
try
{
context = new InitialContext(env);
}
catch (Throwable e)
{
e.printStackTrace();
throw new ServletException(
"Unable to get initial JNDI context: " + e.toString());
}
and by creating an application-client.xml file and puttnig it in the .war
file in the META-INF directory.
The xml file looks like this.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application-client PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE
Application Client 1.2//EN"
"http://java.sun.com/j2ee/dtds/application-client_1_2.dtd";>
<application-client>
<display-name>SPcontroller</display-name>
<ejb-ref>
<ejb-ref-name>ejb/SPControllerHome</res-ref-name>
<ejb-ref-type>Session</res-type>
<home>uk.co.britannic.flexisale.server.spcontroller.SPControllerHome</home>
<remote>uk.co.britannic.flexisale.server.spcontroller.SPController</remote>
</ejb-ref>
</application-client>
But when the line creating the new context is run;
context = new InitialContext(env);
I get the following exception:
javax.naming.NamingException: META-INF/application-client.xml resource not
found (see J2EE spec, application-client chapter for requirements and format
of the file)
at
com.evermind.server.ApplicationClientInitialContextFactory.getInitialContext
(Unknown Source)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at
uk.co.britannic.flexisale.server.test.TestServlet.init(TestServlet.java:46)
at com.evermind._ah._axe(Unknown Source)
at com.evermind._ah._fpd(Unknown Source)
at com.evermind._ah._cwc(Unknown Source)
at com.evermind._io._twc(Unknown Source)
at com.evermind._io._gc(Unknown Source)
at com.evermind._if.run(Unknown Source)
This error occurs even when I'm running orion by itself.
I've looked high and low and cant find any info that indicates why the file
can't be found.
Every example that I can find defines the provider_url as the root of the
web application, like this;
env.put(Context.PROVIDER_URL, "http://localhost/flexisale2";);
If the application-client.xml file is in the META-INF directory of the web
application, why do I get this error?
Has anyone done this before?
Thanks,
Grant Doran
Contract Java Developer/Architect
Britannic Assurance
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: 18 March 2002 15:05
> To: Orion-Interest
> Subject: RE: JNDI naming exception when running app on orion from
> JBuilder
>
> Are you running the servlet in orion or tomcat ?
>
> Does the console in JBuilder say:
>
> Orion/1.5.4 initialized (or whichever version you have)
>
> You should be able to make it work by replacing the code:
>
> java:comp/env/ejb/SPControllerHome
>
> with:
>
> SPControllerHome
>
> It sounds to me like you are running tomcat which is external to your
> session bean (not in the container) and requires the external context
> lookup. If this is the case, a better solution would be to debug the
> servlet in Orion which would mean starting Orion in JBuilder instead of
> tomcat.
>
> Here is an article on how to set up JBuilder to debug Orion, I recommend
> the non-JPDA method.
>
> http://kb.atlassian.com/content/orionsupport/articles/jbuilder-debugging.h
> tml
>
> Tips:
>
> 1. Make sure that your project does not include both the BAS4.5 library
> and the new Orion one you create.
> 2. Include all jar files in the Orion home directory (including
> orion.jar)and the Orion lib directory excluding the tool jars
> (ejb-assembler.jar, admin.jar, etc.) in your Orion library.
>
> I use JBuilder 5 to debug orion and it works great, JBuilder 6 should be
> the same.
>
>
> Original Message:
> -----------------
> From: DORAN, GRANT [EMAIL PROTECTED]
> Date: Mon, 18 Mar 2002 13:27:06 -0000
> To: [EMAIL PROTECTED]
> Subject: JNDI naming exception when running app on orion from JBuilder
>
>
> Hello,
>
> I'm having a terrible time trying to get my application to debug from
> JBuilder 6 Enterprise.
> When I build the application using ANT and deploy it to orion, the servlet
> can lookup the EJBs ok.
> But when I run Orion in debug mode from JBuilder, it starts up ok, but
> fails
> when the servlet tries to lookup the first EJB.
> The line of code is:
>
> Object boundObject =
> context.lookup("java:comp/env/ejb/SPControllerHome");
>
> The output to the log as a result is:
>
> javax.naming.NamingException: java:comp/env namespace is only available
> from
> within a J2EE component
> at
> com.sun.enterprise.naming.java.javaURLContext.getComponentContext(javaURLC
> on
> text.java:395)
> at
> com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:5
> 1)
> at javax.naming.InitialContext.lookup(InitialContext.java:350)
>
> Has anyone else had this problem?
> Has anyone successfully configured JBuilder5 or 6 to debug orion with a
> full
> J2EE app?
>
> If can't get this working, I'll have to change to Borland Appserver,
> which
> will slow my development down even more.
>
> Any help would be greatly appreciated.
>
> Grant Doran
> Contract Java Developer/Architect
> Britannic Assurance
>
> ************
> This email and any accompanying documents are intended only for the named
> recipient, are confidential and may be privileged. If you are not the
> intended recipient please notify us immediately by
> mailto:[EMAIL PROTECTED] and you must not copy, disclose or otherwise
> use this message. Unauthorised use is strictly prohibited and may be
> unlawful. The content of this email represents the view of the individual
> and not the company. The company reserves the right to monitor the content
> of all emails in accordance with lawful business practice.
>
> Whilst attachments are virus checked before transmission, Britannic
> Assurance plc does not accept any liability in respect of any virus which
> is not detected.
>
> Britannic Assurance plc, No.3002 is registered in England and maintains
> its registered office at 1 Wythall Green Way, Wythall, Birmingham B47 6WG.
> Telephone: 0870 887 0001
> Fax: 0870 887 0002
> Website: www.britannicassurance.com
>
> Britannic Assurance plc, Britannic Unit Linked Assurance Limited,
> Britannic ISA Managers Limited and Britannic Unit Trust Managers Limited
> are regulated by the Financial Services Authority. Each of these companies
> is a member of the Britannic marketing group which only advises on and
> sells its own life assurance, pension, unit trust and ISA products.
> ************
>
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
>
************
This email and any accompanying documents are intended only for the named recipient,
are confidential and may be privileged. If you are not the intended recipient please
notify us immediately by mailto:[EMAIL PROTECTED] and you must not copy, disclose
or otherwise use this message. Unauthorised use is strictly prohibited and may be
unlawful. The content of this email represents the view of the individual and not the
company. The company reserves the right to monitor the content of all emails in
accordance with lawful business practice.
Whilst attachments are virus checked before transmission, Britannic Assurance plc does
not accept any liability in respect of any virus which is not detected.
Britannic Assurance plc, No.3002 is registered in England and maintains its registered
office at 1 Wythall Green Way, Wythall, Birmingham B47 6WG.
Telephone: 0870 887 0001
Fax: 0870 887 0002
Website: www.britannicassurance.com
Britannic Assurance plc, Britannic Unit Linked Assurance Limited, Britannic ISA
Managers Limited and Britannic Unit Trust Managers Limited are regulated by the
Financial Services Authority. Each of these companies is a member of the Britannic
marketing group which only advises on and sells its own life assurance, pension, unit
trust and ISA products.
************
