Tracked it down to the following:
- If I only define the ejb-finder 'findAll' in the ObjectTypeBean which extends from 
TypeBean, the jar deploys fine.
- once I add an ejb-finder 'findAll' in the TypeBean (superclass), there's havoc.

> -----Original Message-----
> From: Henning Storhaug 
> Sent: 21. november 2002 23:51
> To: '[EMAIL PROTECTED]'
> Subject: RE: ejb inheritance
> 
> 
> Disclaimer: I may have jumped to conclusions in my previous 
> posting. I based my diagnosis on the following 
> deployment-exception in JBoss 3.0.4:
> 
> org.jboss.deployment.DeploymentException: Error compiling 
> ejbql; - nested throwable: 
> (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered 
> "Type" at line 1, column 32.
> Was expecting one of:
>     "IN" ...
>     <ABSTRACT_SCHEMA> ...
> 
> I couldn't find other occurences of "Type" in the ejb-jar.xml 
> that looked suspicious. However, when I manually removed the 
> 'extra' query-occurence the same deployment-exception pops up...
> 
> If you have ideas about what's wrong, I'd really like to 
> hear! Anyone used EJB-inheritance + xdoclet successfully?
> 
> 
> > -----Original Message-----
> > From: Henning Storhaug 
> > Sent: 21. november 2002 23:11
> > To: '[EMAIL PROTECTED]'
> > Subject: ejb inheritance
> > 
> > 
> > I'm attempting EJB-inheritance, but ejb-jar.xml does not 
> > generate properly using xdoclet 1.2.0 beta.
> > 
> > I have two beans:
> > 
> > 1. TypeBean
> >   - Primary key: Integer typeId 
> >  * @ejb:finder   signature="java.util.Collection findAll()"
> >  *               unchecked="true"
> >  *               query="SELECT DISTINCT OBJECT(i) FROM Type i 
> > WHERE i.typeId IS NOT NULL"
> >  *               result-type-mapping="Local"
> >                
> >  
> > 
> > 2. ObjectTypeBean extends TypeBean
> >   - using the primary key of the superclass.
> >  * @ejb:finder
> >  *    signature="java.util.Collection findAll()"
> >  *    unchecked="true"
> >  *    query="SELECT DISTINCT OBJECT(t) FROM ObjectType t 
> > WHERE t.typeId IS NOT NULL"
> >  *    result-type-mapping="Remote"
> > 
> >  * @ejb.interface       extends="blabla.interfaces.Type"
> >  *                      local-extends="blabla.interfaces.TypeLocal"
> >  * @ejb.home            extends="javax.ejb.EJBHome"
> >  *                      local-extends="javax.ejb.EJBLocalHome"  
> > 
> > 
> > When generating the descriptor-files I get the following:
> > ObjectType-ejb has two findAll-methods. One that uses the 
> > schema-name of it's super, duplicating the first (and 
> > correct) findAll-method.
> > 
> >  <entity>
> >         ......
> > 
> >          <query>
> >             <query-method>
> >                <method-name>findAll</method-name>
> >                <method-params>
> >                </method-params>
> >             </query-method>
> >             <result-type-mapping>Remote</result-type-mapping>
> >             <ejb-ql><![CDATA[SELECT DISTINCT OBJECT(t) FROM 
> > ObjectType t WHERE t.typeId IS NOT NULL]]></ejb-ql>
> >          </query>
> > 
> >          <query>
> >             <query-method>
> >                <method-name>findAll</method-name>
> >                <method-params>
> >                </method-params>
> >             </query-method>
> >             <result-type-mapping>Local</result-type-mapping>
> >             <ejb-ql><![CDATA[SELECT DISTINCT OBJECT(i) FROM 
> > Type i WHERE i.typeId IS NOT NULL]]></ejb-ql>
> >          </query>
> >  </entity>
> > 
> > -----------------------------
> > 
> > Why is the latter query method generated? Any workarounds, 
> > know-how or patches would be nice. 
> > 
> > Some other thing: Why does the ejb-home by default extend 
> > it's parent bean home? 
> > 
> > Regards, 
> > - Henning
> > 
> 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to