Home

  

Product

  

Buy

  

Support

 First Line 
 FAQs 
 Tutorials 
 Registered Users 
 User Guide 
 Knowledge Base 

News

  

Press

  

Downloads

  

Contact

  

Company

  

Partners

  

Resources

 
 
Knowledge Base

ID: 1
Date: 15/06/2002
Title: JCodeBox Tips
Content: 
  1. Install a JDK prior to installing JCodeBox

  2. JCodeBox needs a JDK to be installed so that it can compile generated Java source code. We recommend that you install Sun's JDK (1.3.1 or higher) before installing so that when you install JCodeBox you can use the JVM that shipped with the JDK. This way JCodeBox can automatically use the Java compiler in the JDK. Without a compiler, compilation in JCodeBox will be disabled.

  3. Set a default DataSource JNDI name before building applications

  4. If you set the default DataSource JNDI name before building any applications with JCodeBox, JCodeBox will automatically use this DataSource JNDI name for any entity beans you create (it will also create the required resource reference).

  5. Configure your application server(s) before building applications

  6. JCodeBox uses the libraries that ship with your application server to compile generated Java source code. Without a configured application server compilation in JCodeBox will be disabled.

  7. Leave pattern package names blank

  8. If you leave the package names for patterns blank (i.e. don't enter a anything in the package name field in the pattern dialog) JCodeBox will place the pattern source code in a sub-directory relative to your entity bean source code directory.

  9. Preview components

  10. If you are defining a component that needs to reference other components, preview the other components before you start your definition. This way, when you are defining your component, you can switch to the other components whenever necessary to look up additional information (you can also use AutoCode if you are entering a method). For example, if you are defining a session bean that needs to reference a number of entity beans, preview the entity beans before starting the definition of the session bean. Then if you need to look up additional information (i.e. remote interface name) you can either use AutoCode or switch to the previewed entity bean and look up the information


[an error occurred while processing this directive]