cvs commit: db-ojb/xdocs deployment.xml

[ar...@apache.org]

arminw      2003/07/03 00:00:48

  Modified:    xdocs    deployment.xml
  Log:
  add section logging
  within jboss
  
  Revision  Changes    Path
  1.24      +37 -2     db-ojb/xdocs/deployment.xml
  
  Index: deployment.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/xdocs/deployment.xml,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- deployment.xml	22 Jun 2003 18:12:50 -0000	1.23
  +++ deployment.xml	3 Jul 2003 07:00:48 -0000	1.24
  @@ -477,9 +477,44 @@
   If you will get any problems, please let me know.
   </b>
   </p>
  +
  +<p>
  +<b>OJB logging within JBoss</b><br/>
  +Jboss use <a href="http://jakarta.apache.org/log4j">log4j</a> as standard logging api.
  +<br/>
  +In summary, to use log4j logging with OJB within jBoss,
  +<p>
  +1) in OJB.properties set
  +<source>
  +LoggerClass=org.apache.ojb.broker.util.logging.Log4jLoggerImpl
  +</source>
  +There is no need for a separate log4j.properties file of OJB-specific
  +log4j settings (in fact the OJB.properties setting LoggerConfigFile is
  +ignored).  Instead, the jBoss log4j configuration file must be used:
  +</p>
  +<p>
  +2) in JBOSS_HOME/server/default/conf/log4j.xml,<br/>
  +define appenders and add categories to add or filter logging of desired
  +OJB packages, following the numerous examples in that file.  For example,
  +<source><![CDATA[
  +<category name="org.apache.ojb">
  +      <priority value="DEBUG" />
  +      <appender-ref ref="CONSOLE"/>
  +      <appender-ref ref="FILE"/>
  +    </category>
  +
  +<category name="org.apache.ojb.broker.metadata.RepositoryXmlHandler">
  +      <priority value="ERROR" />
  +      <appender-ref ref="CONSOLE"/>
  +      <appender-ref ref="FILE"/>
  +     </category>
  +]]></source>
  +</p>
  +</p>
   </subsection>
   
   
  +
   <subsection name="Build the OJB sample session beans" anchor="Build the OJB sample session beans">
   <p>
   The OJB source distribution was shipped with a bunch of sample
  @@ -550,7 +585,7 @@
       <ejb-name>ODMGSessionBean</ejb-name>
       <jndi-name>org.apache.ojb.ejb.ODMGSessionBean</jndi-name>
       <local-jndi-name>org.apache.ojb.ejb.ODMGSessionBeanLocal</local-jndi-name>
  -    <depends ptional-attribute-name="Invoker">jboss:service=invoker,type=jrmp</depends>
  +    <depends optional-attribute-name="Invoker">jboss:service=invoker,type=jrmp</depends>
   </session>
   ...
   ]]></source>
  
  
  

OJB + JDORI

[Brian McCallister <mc...@forthillcompany.com>]

There is information in Tutorial 4 about setting up JDORI + OJB for the 
tutorials, but based on the recent volume of email asking about OJB and 
JDO I think it might be good to split out the documentation on setting 
up OJB to work with JDORI into its own page. A tutorial on how to use 
it isn't immediately clear as the place to look for how to set it up.

As the OJB + JDORI is a temporary solution, is *not* allowable for 
commercial development without contacting Sun for permission (anyone 
officially affiliated with OJB willing to nudge them about licensing 
changes so that it can be officially allowable?), and is not generally 
pushed on the lists as a "good" solution I figured I better ask 
opinions on making it easier for people to do before I started spewing 
words into xml.

JDO is getting a lot of press lately, is a pretty nice spec (imho) and 
is going to probably more important to people than ODMG in the future, 
so having a workable solution sooner rather than later might be a good 
idea - especially as OJB has a workable solution right now (but no one 
can figure it out apparently).

Thoughts?

-Brian