RE: [flexcoders] JNDI lookup failure

[Rob]

On the first, I’m declaring in server.xml…and have the <resource-ref> statements in web.xml… I haven’t done the context.xml…I was going to but had basic testing success with the server and web.xml updates.   BTW, thanks for the quick reply J   Rob   From: Jasper Blues [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17,2005 7:31 PM To: 'flexcoders@yahoogroups.com' Subject: RE: [flexcoders] JNDI lookup failure   Hi Rob,   1. Are you declaring your JNDI database connection in /${TomcatHome}/conf/server.xml or /${TomcatHome}/webapps/${yourWebApp}/META-INF/context.xml ? (I find the latter is easier) 2. Does web.xml include the correct <Resource-Ref> definition?   Cheers, Jasper       -----Original Message----- From: Rob [mailto:[EMAIL PROTECTED] Sent: Friday, 18 February 2005 10:26 To: [EMAIL PROTECTED] Subject: [flexcoders] JNDI lookup failure Hi, I’m testing deployment of flex webapp on Tomcat. Everything is configured correctly for rendering of page content, except when I try to call named webservices. The webservices are invoked correctly while inside the Builder dev environment; however, when all is deployed to Tomcat, the webservice calls fail with JNDI naming exceptions “javax.naming.NameNotFoundException: Name <webserviceJDBCConnector> is not bound in this Context”.  Problem is that, as a sanity check, I have a test JSP that uses the same JNDI resources as the Web Services and it runs fine…and is in the same Webapp context as the mxml / AS content.   My guess is that “this Context” is no longerthe context of the webapp as defined by web.xml, or I am missing something in the flex-config.xml.   Thanks for any info.   Regards, Rob ~~------- This e-mail may contain confidential information. If you are not the intended recipient, please notify the sender immediately and delete this e-mail from your system. You must not disclose this e-mail to anyone without express permission from the sender. The contents of all e-mails sent to and received from Optus may be scanned, stored, or disclosed to others at Optus discretion. Optus has exercised care to avoid errors in the information contained in this e-mail but does not warrant that the information is error or omission free.The information (including any pricing information) contained in this e-mail is subject to change. This e-mail is not a quotation or proposal and no contractual obligations arise until you and Optus sign a formal written contract or formal variation to your existing contract. Any pricing contained in this e-mail is exclusive of GST unless otherwise stated. ********************************************************************