Home

  

Product

  

Buy

  

Support

 First Line 
 FAQs 
 Tutorials 
 Registered Users 
 User Guide 
 Knowledge Base 

News

  

Press

  

Downloads

  

Contact

  

Company

  

Partners

  

Resources

 
 
Technical FAQ

    Architecture
  • What architecture is used for generated web applications?
  • Build/Compile
  • I get the following warning: Warning Entity Bean:XXX particpates in more than one relationship with target: YYYY and then I get Duplicate variable declaration error during compilation. What's causing this?
  • Why do I get a Collection not found error when I compile my application?
  • Why do I get lots of javax.ejb.* errors when I compile my application?
  •   What architecture is used for generated web applications?To top of page

    Web applications generated by JCodeBox use the JSP Model 2 architecture and utilise the following patterns:

    • Front controller (or controller servlet)
    • View Helper
    • Service to workers

    All client requests are processed by a front servlet (called front.java) which determines the next JSP to be displayed. Most JSPs have an associated View Helper class (implemented as a Java Bean) that is responsible for any processing required by the JSP and also stores model data required by the JSP. The front servlet calls the processRequest() method on the View Helper for the next JSP to be displayed passing through the details of the client request. When the View Helper has completed its processing, it forwards the request to the JSP using the RequestDispatcher class. This arrangement can be referred to as a service to workers pattern.

      I get the following warning: Warning Entity Bean:XXX particpates in more than one relationship with target: YYYY and then I get Duplicate variable declaration error during compilation. What's causing this?To top of page

    The particpates in more than one relationship warning together with the Duplicate variable declaration compile error mean that two or more relationships have been defined between the same entity beans. i.e. if you have two entity beans CUSTOMEREJB and ORDERSEJB you may have defined a 1:1 relationship between them and also a 1:M relationship between them. The solution is to delete one of the relationships.

      Why do I get a Collection not found error when I compile my application?To top of page

    The java.util.Collection class has not been included in your application. Try using the fully qualified name i.e. java.util.Collection.

      Why do I get lots of javax.ejb.* errors when I compile my application?To top of page

    Numerous javax.ejb.* errors (i.e. can't Interface javax.ejb.EJBLocalObject of interface aa.bb.cc not found) usually indicates an incorrect application server configuration (specifically the application server additional classpath libraries). JCodeBox cannot find the core J2EE classes required for compilation and these are usually provided by your application server vendor. Correcting your application server additional classpath in the Enterprise Server Setup dialog (Tools -> Enterprise server setup … menu) should correct the problem.
    Other classes that maybe missing include

    import javax.ejb.ObjectNotFoundException;
    import javax.ejb.FinderException;
    javax.ejb.CreateException
    etc

    [an error occurred while processing this directive]