Re: OJB Deployment Logging Issue
Hi Ryan, I was having the same problem after updating from an older rc to the 1.0 release, ( I posted a question a few days ago, but I realized now I was not giving the right info, I was going crazy with that Exception ). Well, I have just realized the problem is related with the Java policy permissions. I don't know yet which permission is needed, but if you want to try it, add "java.security.AllPermission" to your .java.policy file and try ( restart server ). Hope this helps! K. Ryan Layer wrote: I am able to get OJB to function properly in an un-managed environment. But when I attempt to deploy an EJB with in the Sun Application Server I get the following error : Could not create Entity EJB; nested exception is: java.lang.NullPointerException java.lang.NullPointerException at org.apache.ojb.broker.util.logging.LoggerFactoryImpl.getLogger(Unknown Source) at org.apache.ojb.broker.util.logging.LoggerFactory.getLogger(Unknown Source) The line causing this error is: private Logger log = LoggerFactory.getLogger(SectionBean.class); I have read the ejb deployment documentation but cannot seem to fix this issue. Could it be that I am not properly setting my CLASSPATH, therefore the LoggerFactory cannot get the configs? Or would this produce a different error? Thanks for your help. --Ryan Layer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OJB Deployment Logging Issue
Hi Ryan, this sounds as if ojb.properties and/or the repository files were not on the classpath. Did you follow the steps required for deploying ojb in an app server? http://db.apache.org/ojb/docu/guides/deployment.html cheers, Thomas Ryan Layer wrote: I am able to get OJB to function properly in an un-managed environment. But when I attempt to deploy an EJB with in the Sun Application Server I get the following error : Could not create Entity EJB; nested exception is: java.lang.NullPointerException java.lang.NullPointerException at org.apache.ojb.broker.util.logging.LoggerFactoryImpl.getLogger(Unknown Source) at org.apache.ojb.broker.util.logging.LoggerFactory.getLogger(Unknown Source) The line causing this error is: private Logger log = LoggerFactory.getLogger(SectionBean.class); I have read the ejb deployment documentation but cannot seem to fix this issue. Could it be that I am not properly setting my CLASSPATH, therefore the LoggerFactory cannot get the configs? Or would this produce a different error? Thanks for your help. --Ryan Layer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OJB Deployment Logging Issue
I am able to get OJB to function properly in an un-managed environment. But when I attempt to deploy an EJB with in the Sun Application Server I get the following error : Could not create Entity EJB; nested exception is: java.lang.NullPointerException java.lang.NullPointerException at org.apache.ojb.broker.util.logging.LoggerFactoryImpl.getLogger(Unknown Source) at org.apache.ojb.broker.util.logging.LoggerFactory.getLogger(Unknown Source) The line causing this error is: private Logger log = LoggerFactory.getLogger(SectionBean.class); I have read the ejb deployment documentation but cannot seem to fix this issue. Could it be that I am not properly setting my CLASSPATH, therefore the LoggerFactory cannot get the configs? Or would this produce a different error? Thanks for your help. --Ryan Layer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OJB deployment in J2EE reference Implementation 1.3.1
Hello everybody. I am new to OJB and I don't know how to deploy OJB in J2EE reference implementation (1.3.1). The only informations I find on the web deals with OJB deployment with JBoss. But nothing concerning J2EE RI. Any help is welcomed. Thanks. Jérôme - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OJB deployment.
I am debating on how to package/deploy OJB with J2EE apps. Is it best to include it as a part of the ejb.jar to avoid metadata conflicts with other apps? If OJB is deployed, for example as a .sar file within an application server like JBOSS, then how do you resolve metadata conflicts between different apps? Is it possible to keep the metadata definition per application separate from the OJB module in the .sar file? If so, is there an example that shows how to do that? - Original Message - From: "Armin Waibel" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Thursday, March 20, 2003 11:39 PM Subject: Re: OJB + Custom connection > Hi Edson, > > hope I don't misunderstand you, > > > I wan't to use a "user authenticated" database connection, not one > open with > > general credentials... > Do this mean you want pass user/password at runtime? > No problem, see FAQ "Many different database user - How do they login?" > > OR > > > Isto possible to open external connection and then configure OJB to > use it > Do you mean to pass the complete connection properties at runtime? > No problem, before the first use of PBF use the MetadataManager and > add a JdbcConnectionDescriptor (contain all connection info). > > OR > > Do you mean you get the real connection by an external process and > you want to use this connection within OJB? > No problem, implement your own > org.apache.ojb.broker.accesslayer.ConnectionFactory and let OJB > use it. > > HTH > regards, > Armin > > - Original Message - > From: "Edson Carlos Ericksson Richter" > <[EMAIL PROTECTED]> > To: "'OJB Users List'" <[EMAIL PROTECTED]> > Sent: Thursday, March 20, 2003 11:40 PM > Subject: OJB + Custom connection > > > > Hi! > > > > Isto possible to open external connection and then configure OJB to > use it > > (not the one in repository.xml - in real, is better if I don't need to > > configure > > connection in repository.xml, besides I think this is not possible). > > > > I wan't to use a "user authenticated" database connection, not one > open with > > general credentials... > > > > Thanks, > > > > Edson Richter > > > > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.463 / Virus Database: 262 - Release Date: 17/3/2003 > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
