RE: Questions about running an EJB client
sorry for the delay, I'll try and explain it again: let's say I (Juan) am a bean developer. Let's say you (Eric) are the application assembler, and let's say Lauren Commons is the deployer. I build a bean. I package the bean in a jar, then pass it on to you. It has some(but not all) of the info needed in ejb-jar.xml . So far it's completly portable across servers. You pick up my bean, add a few of your own, and repackage the .jar . You touch ejb-jar.xml to match your assembly needs(As an example, you want to mark some methods as TX_MANDATORY). You put the .jar in an .ear with the rest of the application modules, and application.xml. This is still PORTABLE across servers (As all in the spec). Now... deployment. A: simple deployment Lauren takes your ear and uses a deploy tool to install the app on a given server. She defines ejb-ref bindings runs required SQL scripts in the DB, maps the security to a given domain etc. To store all of these data(which is server DEPENDANT), the app server creates some files. The app is deployed. B: pre-deployment Deployment is in the corporate HQ of HAL, Inc. If you fuck up there, you're toast. Lauren works with a sturdy, fast server called orion. Regretably, it doesn't include a deploy tool (no, deploytool doesn't work... yet), so she wants to pre-deploy as much as possible about this app in order to have less work to do in the final deployment. So she deploys her app in a test machine. orion-xx.xml files are created. How does she use these files? She REPACKAGES the App, storing the new files alongside its counter-part (orion-application.xml and application.xml go in the same dir), except in the case of ejb-jar.xml, which goes in an orion directory inside the ejb jar. This app is still portable across servers, but it contains now some information on how to deploy on orion-servers. The same process could be done for J2EERI and WLS 6.0, making the actual deployment very accesible. When Lauren deploys this modified .ear, orion will find the orion-xxx files inside the ear, and instead of creating deployment files from scratch, using defaults, it will use the in-ear files to create the actual, $orion\application-deployment resident, orion-xx.xml files. I sure do hope this helps... JP PS: Lauren... may I stick my tongue in your ear? -Original Message- From: Eric Hodges [mailto:[EMAIL PROTECTED]] Sent: Jueves, 01 de Febrero de 2001 19:20 To: Orion-Interest Subject: Re: Questions about running an EJB client - Original Message - From: "Juan Lorandi (Chile)" [EMAIL PROTECTED] To: "Orion-Interest" [EMAIL PROTECTED] Sent: Thursday, February 01, 2001 3:33 PM Subject: RE: Questions about running an EJB client Read the j2ee spec again. orion-x.xml files are deployment info; deployment info is server dependant (in contrast to bean developer info assembly info); deployment info may override complete for j2eeri, files are named j2eeri-.xml basically, there's one of these per every .xml in the specs: SPEC file Orion file packageplace application.xml orion-application.xml \YOURAPP.ear\META-INF\ ejb-jar.xml orion-ejb-jar.xml \YOURAPP.ear\YOUREJB.jar\orion web.xml orion-web.xml \YOURAPP.ear\YOURWAR.war\WEB-INF\ I don't really understand what you just typed. So orion-application.xml gets its info from application.xml? If so, do I just stick this namespace stuff in application.xml?
Re: Questions about running an EJB client
OK, I got the security problem resolved. Thanks Juan! Now I've got another problem: javax.naming.NamingException: Error reading application-client descriptor: No location specified and no suitable instance of the type 'AgentRegistrar' found for the ejb-ref AgentRegistrar Where is it looking for the application-client descriptor location?
Re: Questions about running an EJB client
- Original Message - From: "Juan Lorandi (Chile)" [EMAIL PROTECTED] To: "Orion-Interest" [EMAIL PROTECTED] Sent: Thursday, February 01, 2001 3:33 PM Subject: RE: Questions about running an EJB client Read the j2ee spec again. orion-x.xml files are deployment info; deployment info is server dependant (in contrast to bean developer info assembly info); deployment info may override complete for j2eeri, files are named j2eeri-.xml basically, there's one of these per every .xml in the specs: SPEC file Orion file packageplace application.xml orion-application.xml \YOURAPP.ear\META-INF\ ejb-jar.xml orion-ejb-jar.xml \YOURAPP.ear\YOUREJB.jar\orion web.xml orion-web.xml \YOURAPP.ear\YOURWAR.war\WEB-INF\ I don't really understand what you just typed. So orion-application.xml gets its info from application.xml? If so, do I just stick this namespace stuff in application.xml?
Re: Questions about running an EJB client
It still doesn't work. I get the same error message. My orion-application.xml file looks like this: ?xml version="1.0"? !DOCTYPE orion-application PUBLIC "-//Evermind//DTD J2EE Application runtime 1.2//EN" "http://www.orionserver.com/dtds/orion-application.dtd" orion-application deployment-version="1.3.8" ejb-module remote="false" path="AgentRegistrar.jar" / persistence path="persistence" / principals path="principals.xml" / log file path="application.log" / /log namespace-access read-access namespace-resource root="" security-role-mapping name="lt;jndi-user-rolegt;" group name="Administrator" / /security-role-mapping /namespace-resource /read-access write-access namespace-resource root="" security-role-mapping group name="Administrator" / /security-role-mapping /namespace-resource /write-access /namespace-access /orion-application Administrator is defined in orion/config/principals.xml. I added it to the principals.xml for my EAR as well, with no luck.
Re: Questions about running an EJB client
Where did this file come from? I didn't put it in my EJB jar or my EAR file. It doesn't look like yours (there's no name attribute on the security-role-mapping tag), so once I edit it how will I stick it back in my EAR? That sounds odd, doesn't it? Thanks for the help. - Original Message - From: "Juan Lorandi (Chile)" [EMAIL PROTECTED] To: "Orion-Interest" [EMAIL PROTECTED] Sent: Thursday, February 01, 2001 11:51 AM Subject: RE: Questions about running an EJB client in orion-application.xml (you can find it in $orion\application-deployments\YOURAPP\) there should be a namespace tag; below is mine's form an app: namespace-access read-access namespace-resource root="" security-role-mapping name="lt;jndi-user-rolegt;" group name="admin" / /security-role-mapping /namespace-resource /read-access write-access /write-access /namespace-access then, whenever the current user belongs to group admin, you have read access for ALL resources. I believe that something on the line of group name="admin" impliesAll="true" / would grant everybody read access; AFAIK Orion's JNDI imp. doesn't support writing, so the write-access part is irrelevant HTH JP -Original Message- From: Eric Hodges [mailto:[EMAIL PROTECTED]] Sent: Mircoles, 31 de Enero de 2001 20:14 To: Orion-Interest Subject: Questions about running an EJB client I'm trying to set up an EJB (my first time) on Orion. I have the .EAR file running, I just need to get the client to test it. When I try to run the client, it fails on the constructor for InitialContext(). Here's the error: java.lang.SecurityException: Not allowed to look up java:comp/ResourceFinder, check the namespace-access tag setting in orion-application.xml for details at com.evermind.server.rmi.bb.f_(JAX) at com.evermind.server.rmi.RMIServer.f_(JAX) at com.evermind.server.rmi.RMIContext.lookup(JAX) at com.evermind.server.administration.LazyResourceFinder.f_(JAX) at com.evermind.server.administration.LazyResourceFinder.getEJBHome(JAX) at com.evermind.server.Application.ap7(JAX) at com.evermind.server.ApplicationClientInitialContextFactory.get InitialContext (JAX) at javax.naming.spi.NamingManager.getInitialContext(NamingManager .java:668) 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 com.mongoosetech.agent.AgentBase.registerWithServer(AgentBase. java:100) at com.mongoosetech.agent.AgentBase.register(AgentBase.java:71) at com.mongoosetech.agent.AgentBase.init(AgentBase.java:58) at com.mongoosetech.agent.jdbcagent.JDBCAgent.init(JDBCAgent.java:81) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.init(JDBCFramg ent.java:21) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.main(JDBCFramgen t.java:73) The problem is that I don't have a file called "orion-application.xml". From the docs, I get the impression this is an Orion specific version of application.xml. I have that, but I don't see a way to make it let me look up java:comp/ResourceFinder. Any clues?
Questions about running an EJB client
I'm trying to set up an EJB (my first time) on Orion. I have the .EAR file running, I just need to get the client to test it. When I try to run the client, it fails on the constructor for InitialContext(). Here's the error: java.lang.SecurityException: Not allowed to look up java:comp/ResourceFinder, check the namespace-access tag setting in orion-application.xml for details at com.evermind.server.rmi.bb.f_(JAX) at com.evermind.server.rmi.RMIServer.f_(JAX) at com.evermind.server.rmi.RMIContext.lookup(JAX) at com.evermind.server.administration.LazyResourceFinder.f_(JAX) at com.evermind.server.administration.LazyResourceFinder.getEJBHome(JAX) at com.evermind.server.Application.ap7(JAX) at com.evermind.server.ApplicationClientInitialContextFactory.getInitialContext (JAX) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:668) 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 com.mongoosetech.agent.AgentBase.registerWithServer(AgentBase.java:100) at com.mongoosetech.agent.AgentBase.register(AgentBase.java:71) at com.mongoosetech.agent.AgentBase.init(AgentBase.java:58) at com.mongoosetech.agent.jdbcagent.JDBCAgent.init(JDBCAgent.java:81) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.init(JDBCFramgent.java:21) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.main(JDBCFramgent.java:73) The problem is that I don't have a file called "orion-application.xml". From the docs, I get the impression this is an Orion specific version of application.xml. I have that, but I don't see a way to make it let me look up java:comp/ResourceFinder. Any clues?
Questions about running an EJB client
I'm trying to set up an EJB (my first time) on Orion. I have the .EAR file running, I just need to get the client to test it. When I try to run the client, it fails on the constructor for InitialContext(). Here's the error: java.lang.SecurityException: Not allowed to look up java:comp/ResourceFinder, check the namespace-access tag setting in orion-application.xml for details at com.evermind.server.rmi.bb.f_(JAX) at com.evermind.server.rmi.RMIServer.f_(JAX) at com.evermind.server.rmi.RMIContext.lookup(JAX) at com.evermind.server.administration.LazyResourceFinder.f_(JAX) at com.evermind.server.administration.LazyResourceFinder.getEJBHome(JAX) at com.evermind.server.Application.ap7(JAX) at com.evermind.server.ApplicationClientInitialContextFactory.getInitialContext (JAX) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:668) 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 com.mongoosetech.agent.AgentBase.registerWithServer(AgentBase.java:100) at com.mongoosetech.agent.AgentBase.register(AgentBase.java:71) at com.mongoosetech.agent.AgentBase.init(AgentBase.java:58) at com.mongoosetech.agent.jdbcagent.JDBCAgent.init(JDBCAgent.java:81) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.init(JDBCFramgent.java:21) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.main(JDBCFramgent.java:73) The problem is that I don't have a file called "orion-application.xml". From the docs, I get the impression this is an Orion specific version of application.xml. I have that, but I don't see a way to make it let me look up java:comp/ResourceFinder. Any clues?
RE: Questions about running an EJB client
in orion-application.xml (you can find it in $orion\application-deployments\YOURAPP\) there should be a namespace tag; below is mine's form an app: namespace-access read-access namespace-resource root="" security-role-mapping name="lt;jndi-user-rolegt;" group name="admin" / /security-role-mapping /namespace-resource /read-access write-access /write-access /namespace-access then, whenever the current user belongs to group admin, you have read access for ALL resources. I believe that something on the line of group name="admin" impliesAll="true" / would grant everybody read access; AFAIK Orion's JNDI imp. doesn't support writing, so the write-access part is irrelevant HTH JP -Original Message- From: Eric Hodges [mailto:[EMAIL PROTECTED]] Sent: Mircoles, 31 de Enero de 2001 20:14 To: Orion-Interest Subject: Questions about running an EJB client I'm trying to set up an EJB (my first time) on Orion. I have the .EAR file running, I just need to get the client to test it. When I try to run the client, it fails on the constructor for InitialContext(). Here's the error: java.lang.SecurityException: Not allowed to look up java:comp/ResourceFinder, check the namespace-access tag setting in orion-application.xml for details at com.evermind.server.rmi.bb.f_(JAX) at com.evermind.server.rmi.RMIServer.f_(JAX) at com.evermind.server.rmi.RMIContext.lookup(JAX) at com.evermind.server.administration.LazyResourceFinder.f_(JAX) at com.evermind.server.administration.LazyResourceFinder.getEJBHome(JAX) at com.evermind.server.Application.ap7(JAX) at com.evermind.server.ApplicationClientInitialContextFactory.get InitialContext (JAX) at javax.naming.spi.NamingManager.getInitialContext(NamingManager .java:668) 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 com.mongoosetech.agent.AgentBase.registerWithServer(AgentBase. java:100) at com.mongoosetech.agent.AgentBase.register(AgentBase.java:71) at com.mongoosetech.agent.AgentBase.init(AgentBase.java:58) at com.mongoosetech.agent.jdbcagent.JDBCAgent.init(JDBCAgent.java:81) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.init(JDBCFramg ent.java:21) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.main(JDBCFramgen t.java:73) The problem is that I don't have a file called "orion-application.xml". From the docs, I get the impression this is an Orion specific version of application.xml. I have that, but I don't see a way to make it let me look up java:comp/ResourceFinder. Any clues?
Re: Questions about running an EJB client
never stick ANYTHING in your ear --- Eric Hodges [EMAIL PROTECTED] wrote: Where did this file come from? I didn't put it in my EJB jar or my EAR file. It doesn't look like yours (there's no name attribute on the security-role-mapping tag), so once I edit it how will I stick it back in my EAR? That sounds odd, doesn't it? Thanks for the help. - Original Message - From: "Juan Lorandi (Chile)" [EMAIL PROTECTED] To: "Orion-Interest" [EMAIL PROTECTED] Sent: Thursday, February 01, 2001 11:51 AM Subject: RE: Questions about running an EJB client in orion-application.xml (you can find it in $orion\application-deployments\YOURAPP\) there should be a namespace tag; below is mine's form an app: namespace-access read-access namespace-resource root="" security-role-mapping name="lt;jndi-user-rolegt;" group name="admin" / /security-role-mapping /namespace-resource /read-access write-access /write-access /namespace-access then, whenever the current user belongs to group admin, you have read access for ALL resources. I believe that something on the line of group name="admin" impliesAll="true" / would grant everybody read access; AFAIK Orion's JNDI imp. doesn't support writing, so the write-access part is irrelevant HTH JP -Original Message- From: Eric Hodges [mailto:[EMAIL PROTECTED]] Sent: Miércoles, 31 de Enero de 2001 20:14 To: Orion-Interest Subject: Questions about running an EJB client I'm trying to set up an EJB (my first time) on Orion. I have the .EAR file running, I just need to get the client to test it. When I try to run the client, it fails on the constructor for InitialContext(). Here's the error: java.lang.SecurityException: Not allowed to look up java:comp/ResourceFinder, check the namespace-access tag setting in orion-application.xml for details at com.evermind.server.rmi.bb.f_(JAX) at com.evermind.server.rmi.RMIServer.f_(JAX) at com.evermind.server.rmi.RMIContext.lookup(JAX) at com.evermind.server.administration.LazyResourceFinder.f_(JAX) at com.evermind.server.administration.LazyResourceFinder.getEJBHome(JAX) at com.evermind.server.Application.ap7(JAX) at com.evermind.server.ApplicationClientInitialContextFactory.get InitialContext (JAX) at javax.naming.spi.NamingManager.getInitialContext(NamingManager .java:668) 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 com.mongoosetech.agent.AgentBase.registerWithServer(AgentBase. java:100) at com.mongoosetech.agent.AgentBase.register(AgentBase.java:71) at com.mongoosetech.agent.AgentBase.init(AgentBase.java:58) at com.mongoosetech.agent.jdbcagent.JDBCAgent.init(JDBCAgent.java:81) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.init(JDBCFramg ent.java:21) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.main(JDBCFramgen t.java:73) The problem is that I don't have a file called "orion-application.xml". From the docs, I get the impression this is an Orion specific version of application.xml. I have that, but I don't see a way to make it let me look up java:comp/ResourceFinder. Any clues? __ Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
RE: Questions about running an EJB client
Read the j2ee spec again. orion-x.xml files are deployment info; deployment info is server dependant (in contrast to bean developer info assembly info); deployment info may override complete for j2eeri, files are named j2eeri-.xml basically, there's one of these per every .xml in the specs: SPEC file Orion file packageplace application.xml orion-application.xml \YOURAPP.ear\META-INF\ ejb-jar.xml orion-ejb-jar.xml \YOURAPP.ear\YOUREJB.jar\orion web.xml orion-web.xml \YOURAPP.ear\YOURWAR.war\WEB-INF\ At deployment time, orion creates a counter-part of your SPEC files in $orion\application-deployments\ for this it may use templates bundled in your package (if found in packageplace) HTH JP -Original Message- From: Eric Hodges [mailto:[EMAIL PROTECTED]] Sent: Jueves, 01 de Febrero de 2001 15:50 To: Orion-Interest Subject: Re: Questions about running an EJB client Where did this file come from? I didn't put it in my EJB jar or my EAR file. It doesn't look like yours (there's no name attribute on the security-role-mapping tag), so once I edit it how will I stick it back in my EAR? That sounds odd, doesn't it? Thanks for the help. - Original Message - From: "Juan Lorandi (Chile)" [EMAIL PROTECTED] To: "Orion-Interest" [EMAIL PROTECTED] Sent: Thursday, February 01, 2001 11:51 AM Subject: RE: Questions about running an EJB client in orion-application.xml (you can find it in $orion\application-deployments\YOURAPP\) there should be a namespace tag; below is mine's form an app: namespace-access read-access namespace-resource root="" security-role-mapping name="lt;jndi-user-rolegt;" group name="admin" / /security-role-mapping /namespace-resource /read-access write-access /write-access /namespace-access then, whenever the current user belongs to group admin, you have read access for ALL resources. I believe that something on the line of group name="admin" impliesAll="true" / would grant everybody read access; AFAIK Orion's JNDI imp. doesn't support writing, so the write-access part is irrelevant HTH JP -Original Message- From: Eric Hodges [mailto:[EMAIL PROTECTED]] Sent: Mircoles, 31 de Enero de 2001 20:14 To: Orion-Interest Subject: Questions about running an EJB client I'm trying to set up an EJB (my first time) on Orion. I have the .EAR file running, I just need to get the client to test it. When I try to run the client, it fails on the constructor for InitialContext(). Here's the error: java.lang.SecurityException: Not allowed to look up java:comp/ResourceFinder, check the namespace-access tag setting in orion-application.xml for details at com.evermind.server.rmi.bb.f_(JAX) at com.evermind.server.rmi.RMIServer.f_(JAX) at com.evermind.server.rmi.RMIContext.lookup(JAX) at com.evermind.server.administration.LazyResourceFinder.f_(JAX) at com.evermind.server.administration.LazyResourceFinder.getEJBHome(JAX) at com.evermind.server.Application.ap7(JAX) at com.evermind.server.ApplicationClientInitialContextFactory.get InitialContext (JAX) at javax.naming.spi.NamingManager.getInitialContext(NamingManager .java:668) 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 com.mongoosetech.agent.AgentBase.registerWithServer(AgentBase. java:100) at com.mongoosetech.agent.AgentBase.register(AgentBase.java:71) at com.mongoosetech.agent.AgentBase.init(AgentBase.java:58) at com.mongoosetech.agent.jdbcagent.JDBCAgent.init(JDBCAgent.java:81) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.init(JDBCFramg ent.java:21) at com.mongoosetech.agent.jdbcagent.JDBCFramgent.main(JDBCFramgen t.java:73) The problem is that I don't have a file called "orion-application.xml". From the docs, I get the impression this is an Orion specific version of application.xml. I have that, but I don't see a way to make it let me look up java:comp/ResourceFinder. Any clues?
