On Tue, 17 Dec 2002 21:03,
<[EMAIL PROTECTED]> wrote:
> Try XDoclet 1.2 beta 1. XDoclet 2 is barely started and far from
> useable.
Thanks. I thought I had, but apparently I didn't. I'm glad to find that 1.2
*doesn't* put the import statements in!
However, now I've got another problem :)
I've got a bunch of Query EJBs. I'm using an abstract QueryBean which defines
most of the behaviour, and each subclass of QueryBean implements the
specifics. I look the EJBs up using their home interface, but down-cast the
returned object back to a generic Query for access through the common
methods.
This all worked fine using XDoclet 1.1.2 (before the packages were rearranged
of course, necessitating the switch), but under 1.2, *only* the superclass
interfaces are being generated (ie, Query and QueryHome).
What other behaviour has changed from 1.1.2 to 1.2 that would cause this?
Below are some samples from the code...
==========
QueryBean:
==========
/**
* @ejb:bean generate = "false"
**/
public abstract class QueryBean implements SessionBean {
...
/**
* (One of several client methods)
* @ejb:interface-method view-type="remote"
**/
public void setParams(FieldMap fields) {
...
}
...
================
ClientQueryBean:
================
/**
* @ejb:bean name="ClientQuery"
* display-name="Client Query Bean"
* type="Stateful"
* transaction-type="Container"
* jndi-name="ejb/ClientQuery"
**/
public class ClientQueryBean extends QueryBean {
...
/**
* @ejb:create-method view-type="remote"
**/
public void ejbCreate()
throws CreateException {
log.debug("ClientQueryBean created");
}
...
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
