I had the same exact isue, and I resolved this by creating an
AbstractSLSB.java file that extended Springs Abstract Session bean class,
then my XDoclet Bean extends that, and XDoclet was fine.
public abstract class AbstractSLSB extends AbstractStatelessSessionBean {
}
/**
* Bean implementation class for Enterprise Bean: ConsumerManagerBean
*
* @ejb.bean name="ConsumerManager"
* display-name="Consumer Manager Session Bean"
* type="Stateless"
* view-type="local"
* local-jndi-name="local/ConsumerManager"
*
* @ejb.home local-extends="javax.ejb.EJBLocalHome"
* @ejb.interface local-extends="ConsumerManager, javax.ejb.EJBLocalObject"
*
* @jboss.container-configuration name="Standard Stateless SessionBean"
*
* @websphere.container-configuration name="Standard Stateless SessionBean"
* @websphere.bean
*
* @ejb.env-entry name="ejb/BeanFactoryPath"
* type="java.lang.String"
* value="applicationContext.xml"
*
* @ejb.util generate="physical"
* @ejb.transaction type="Required"
* @ejb.transaction-type type="Container"
* @ejb.permission unchecked="true"
*/
public class ConsumerManagerBean extends AbstractSLSB
implements ConsumerManager {
.....
}
From: Stephane Nicoll <[EMAIL PROTECTED]>
Reply-To: Stephane Nicoll <[EMAIL PROTECTED]>
To: Maven Users List <[email protected]>
Subject: Re: A bug in the Maven plugin for XDoclet?
Date: Wed, 20 Jul 2005 16:23:41 +0200
Ken,
The maven plugin is just a wrapper around the ant task and the Xdoclet
guys manage this plugin themselves so you should contact them.
Cheers,
Stéphane
On 7/20/05, Ballard, Ken <[EMAIL PROTECTED]> wrote:
> Is this a bug in the Maven plugin for XDoclet (I'm using version 1.2.3)?
> When using EJBDoclet with ANT, you can write a Stateless Session Bean
that
> extends Spring's EJB support class
> org.springframework.ejb.support.AbstractStatelessSessionBean and XDoclet
> will generate the appropriate interfaces and descriptors. With the
XDoclet
> plugin for Maven you can only write a Stateless Session Bean that
implements
> javax.ejb.SessionBean and get the correct results. Otherwise EJBDoclet
> generates interfaces that extend fictitious classes. For example, if you
> have a Stateless Session Bean that extends AbstractStatelessSessionBean,
> instead of generating a RemoteInterface that extends
javax.ejb.EJBObject,
> ejbdoclet creates a RemoteInterface that extends a fictitious class. It
> takes the word AbstractStatelessSessionBean, and either adds Remote to
the
> end of it if you specified
> "maven.xdoclet.ejbdoclet.remoteinterface.0.pattern={0}Remote" in your
> project.properties or just strips off "Bean" leaving you with
> org.springframework.ejb.support.AbstractStatelessSession which also does
not
> exist. I've scoured the earth looking for any documentation, blog, or
> anything that will tell me how to get around this. I haven't found
anything.
> Is this a bug?
>
> Thanks,
> Ken
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is
> for the sole use of the intended recipient(s) and may contain
confidential
> and privileged information. Any unauthorized review, use, disclosure or
> distribution is prohibited. If you are not the intended recipient,
please
> contact the sender by reply e-mail and destroy all copies of the
original
> message.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
.::You're welcome ::.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thank You
Mick Knutson
Sr. Java/J2EE Consultant
BASE logic, inc.
(415) 648-1804 (S.F., CA)
http://www.BASELogic.com
HP Consulting Services (Walnut Creek, CA)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
