facebook

XDoclet generation errors

  1. MyEclipse IDE
  2.  > 
  3. Java EE Development (EJB, JSP, Struts, XDoclet, etc.)
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #272716 Reply

    feili
    Member

    Hi,

    If you do XDoclet generation for the following code you will find a few errors which are so easy to find. I do not know why your guys still have not fixed them.

    package com.mda.od.entity.ejb;

    import java.rmi.RemoteException;

    import javax.ejb.EJBException;
    import javax.ejb.EntityBean;
    import javax.ejb.EntityContext;
    import javax.ejb.RemoveException;

    import javax.ejb.CreateException;

    import com.mda.od.entity.interfaces.CountryValue;

    /**
    * XDoclet-based CMP 2.x entity bean. This class must be declared
    * public abstract because the concrete class will
    * be implemented by the CMP providers tooling.
    *
    * To generate EJB related classes using XDoclet:
    *
    * – Add Standard EJB module to XDoclet project properties
    * – Customize XDoclet configuration
    * – Run XDoclet
    *
    * Below are the xdoclet-related tags needed for this EJB.
    *
    * @ejb.bean name=”Country”
    * display-name=”Country”
    * description=”Country”
    * jndi-name=”ejb/Country”
    * type=”CMP”
    * cmp-version=”2.x”
    * primkey-field=”CountryKey”
    * view-type=”local”
    *
    * @ejb.value-object
    */
    public abstract class Country implements EntityBean {

    /** The entity context */
    private EntityContext context;

    public Country() {
    // TODO Auto-generated constructor stub
    }

    /**
    * There are zero or more ejbCreate<METHOD>(…) methods, whose signatures match
    * the signatures of the create<METHOD>(…) methods of the entity bean?s home interface.
    * The container invokes an ejbCreate<METHOD>(…) method on an entity bean instance
    * when a client invokes a matching create<METHOD>(…) method on the entity bean?s
    * home interface.<br>
    *
    * The entity bean provider?s responsibility is to initialize the instance in the ejbCreate<
    * METHOD>(…) methods from the input arguments, using the get and set accessor
    * methods, such that when the ejbCreate<METHOD>(…) method returns, the persistent
    * representation of the instance can be created. <br>
    *
    * The entity bean provider must not attempt to modify the values of cmr-fields in an ejbCreate<
    * METHOD(…) method; this should be done in the ejbPostCreate<METHOD(…) method instead.<br>
    *
    * The entity object created by the ejbCreate<METHOD> method must have a unique primary
    * key. This means that the primary key must be different from the primary keys of all the existing
    * entity objects within the same home. However, it is legal to reuse the primary key of a previously
    * removed entity object. The implementation of the bean provider?s ejbCreate<
    * METHOD>(…) methods should be coded to return a null.<br>
    *
    * An ejbCreate<METHOD>(…) method executes in the transaction context determined by
    * the transaction attribute of the matching create<METHOD>(…) method.
    * The database insert operations are performed by the container within the same
    * transaction context after the Bean Provider?s ejbCreate<METHOD>(…) method completes.
    *
    * @throws CreateException Thrown if method fails due to system-level error.
    *
    * @throws CreateException
    *
    * @ejb.create-method
    */
    public Long ejbCreate() throws CreateException {
    return null;
    }

    /**
    * For each ejbCreate<METHOD>(…) method, there is a matching ejbPostCreate<
    * METHOD>(…) method that has the same input parameters but whose return type is
    * void. The container invokes the matching ejbPostCreate<METHOD>(…) method on
    * an instance after it invokes the ejbCreate<METHOD>(…) method with the same arguments.
    * The instance can discover the primary key by calling getPrimaryKey() on its
    * entity context object. <br>
    *
    * The entity object identity is available during the ejbPostCreate<METHOD>(…)
    * method. The instance may, for example, obtain the component interface of the associated entity
    * object and pass it to another enterprise bean as a method argument.<br>
    *
    * The entity Bean Provider may use the ejbPostCreate<METHOD>(…) to set the values
    * of cmr-fields to complete the initialization of the entity bean instance.
    * An ejbPostCreate<METHOD>(…) method executes in the same transaction context as
    * the previous ejbCreate<METHOD>(…) method.
    *
    * @throws CreateException Thrown if method fails due to system-level error.
    */
    public void ejbPostCreate() throws CreateException {
    }

    /**
    * @ejb.create-method
    */
    public Long ejbCreate(CountryValue countryValue) throws CreateException {
    setCountryKey(countryValue.getCountryKey());
    setCountryValue(countryValue);
    return null;
    }

    public void ejbPostCreate(CountryValue countryValue) throws CreateException {
    }

    public void ejbActivate() throws EJBException, RemoteException {
    // TODO Auto-generated method stub

    }

    public void ejbLoad() throws EJBException, RemoteException {
    // TODO Auto-generated method stub

    }

    public void ejbPassivate() throws EJBException, RemoteException {
    // TODO Auto-generated method stub

    }

    public void ejbRemove()
    throws RemoveException,
    EJBException,
    RemoteException {
    // TODO Auto-generated method stub

    }

    public void ejbStore() throws EJBException, RemoteException {
    // TODO Auto-generated method stub

    }

    /**
    * Set the associated entity context. The container calls this method
    * after the instance creation. The entity bean must not attempt to
    * access its persistent state and relationships using the accessor
    * methods during this method. <br>
    *
    * The enterprise bean instance should store the reference to the context
    * object in an instance variable. <br>
    *
    * This method is called with no transaction context.
    *
    * @throws EJBException Thrown if method fails due to system-level error.
    */
    public void setEntityContext(EntityContext newContext) throws EJBException {
    context = newContext;
    }

    /**
    * Unset the associated entity context. A container invokes this method
    * before terminating the life of the instance. The entity bean must not
    * attempt to access its persistent state and relationships using the
    * accessor methods during this method. <br>
    *
    * This method is called with no transaction context.
    *
    * @throws EJBException Thrown if method fails due to system-level error.
    */
    public void unsetEntityContext() throws EJBException {
    context = null;
    }

    /**
    * @ejb.interface-method view-type=”local”
    * @ejb.persistent-field
    * @ejb.pk-field
    * @return
    */
    public abstract Long getCountryKey();

    /**
    * @ejb.interface-method view-type=”local”
    * @param newCountryKeyValue
    */
    public abstract void setCountryKey(Long newCountryKeyValue);

    /**
    * @ejb.interface-method view-type=”local”
    * @ejb.persistence
    */
    public abstract String getCountryCode();

    /**
    * @ejb.interface-method view-type=”local”
    */
    public abstract void setCountryCode(String newCountryCodeValue);

    /**
    * @ejb.interface-method view-type=”local”
    * @ejb.persistence
    */
    public abstract String getCountryName();

    /**
    * @ejb.interface-method view-type=”local”
    */
    public abstract void setCountryName(String newCountryNameValue);

    /**
    * @ejb.interface-method view-type = “local”
    */
    public abstract CountryValue getCountryValue();

    /**
    * @ejb.interface-method view-type = “local”
    */
    public abstract void setCountryValue(CountryValue countryValue);

    }

    #272764 Reply

    Riyad Kalla
    Member

    feili,
    MyEclipse provides a *runner* for XDoclet (http://xdoclet.sf.net) we do not code any of the XDoclet generation libraries for any of the technologies that XDoclet supports. The bugs you are seeing are all from the XDoclet libraries themselves, and unfortunately it looks like the project is more or less dead… so I don’t know that any bug fixes or improvements will be forth coming from that group.

    Although if they do release an update version that fixes these bugs, we *will* happily integrate them.

Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: XDoclet generation errors

You must be logged in to post in the forum log in