Failed deployment
sysuser1 Nov 21, 2003 2:26 AMHi,
I've generated some CMP EJBs with middlegen and xdoclet. One of this EJBs, generates some problems during deployment when it's deployed in a .EAR file or when it's hot redeployed in a .JAR file.
The exception during the deployment is:
18:01:14,000 WARN [verifier] EJB spec violation:
Bean : Usuario
Section: 10.6.2
Warning: The entity bean class must define a get accessor for each CMP field.
Info : Field: fechaalta
18:01:14,000 WARN [verifier] EJB spec violation:
Bean : Usuario
Section: 10.6.2
Warning: The entity bean class must define a set accessor for each CMP field.
Info : Field: fechaalta
18:01:14,000 WARN [verifier] EJB spec violation:
Bean : Usuario
Section: 10.6.2
Warning: The entity bean class must define a get accessor for each CMP field.
Info : Field: fechabaja
18:01:14,000 WARN [verifier] EJB spec violation:
Bean : Usuario
Section: 10.6.2
Warning: The entity bean class must define a set accessor for each CMP field.
Info : Field: fechabaja
I have seen the xdoclet code generated by Middlegen and I can't found anything strange. Part of the UsuarioBean.java is:
/**
* Returns the fechaalta
* @todo support OracleClob,OracleBlob on WLS
*
* @return the fechaalta
*
* @ejb.interface-method view-type="local"
* @ejb.persistent-field
* @ejb.persistence column-name="fechaalta"
*/
public abstract java.sql.Timestamp getFechaalta();
/**
* Sets the fechaalta
*
* @param java.sql.Timestamp the new fechaalta value
* @ejb.interface-method view-type="local"
*/
public abstract void setFechaalta(java.sql.Timestamp fechaalta);
/**
* Returns the fechabaja
* @todo support OracleClob,OracleBlob on WLS
*
* @return the fechabaja
*
* @ejb.interface-method view-type="local"
* @ejb.persistent-field
* @ejb.persistence column-name="fechabaja"
*/
public abstract java.sql.Timestamp getFechabaja();
/**
* Sets the fechabaja
*
* @param java.sql.Timestamp the new fechabaja value
* @ejb.interface-method view-type="local"
*/
public abstract void setFechabaja(java.sql.Timestamp fechabaja);
I'm using a JBoss3.2.2 (with Tomcat).
I think it's a bit strange because, as I've said, when it's deployed as a single JAR file it works (but fail when hot redeployed). Perhaps it's the Timestamp types but I've used them in other EJB without problem. And it looks like the jbosscmp-jdbc.xml and ejb-jar.xml generated contain these fields.
Any help will be welcome.
Thanks,
Jorge