[jira] Commented: (XDP-240) EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml
"Konstantin Kasatkin (JIRA)" <jira-yCVjj/[email protected]> Fri, 6 Mar 2009 01:10:12 -0600 (CST)
| Newsgroups | gmane.comp.java.xdoclet-plugins |
|---|---|
| Message-ID | <19404067.1236323412965.JavaMail.haus-jira@codehaus01.managed.contegix.com> |
[ http://jira.codehaus.org/browse/XDP-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168119#action_168119 ]
Konstantin Kasatkin commented on XDP-240:
-----------------------------------------
Some additional comments about attachment.
Archive xdoclet2.zip contains java source including xdoclet tags code for processing
and Atn build script.
Also it contains xdoclet1-generated.zip archive that
is a result of processing the same source code by xdoclet1 framework.
It is an example for EJB plugin how it should really work.
> EJB Plugin doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml
> ------------------------------------------------------------------------------------------------------------
>
> Key: XDP-240
> URL: http://jira.codehaus.org/browse/XDP-240
> Project: XDoclet 2 Plugins
> Issue Type: Bug
> Components: ejb
> Affects Versions: 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0
> Environment: JDK 1.5
> ANT 1.7
> Reporter: Konstantin Kasatkin
> Priority: Critical
> Attachments: xdoclet2.zip
>
>
> It doesn't parse EJB super class for xdoclet tags and doesn't put their description into ejb-jar.xml.
> XDoclet1 really did that, because I remember that I personally set this issue against project team.
> I have an 2 super classes for the EJB and a super interface for EJB Interface looking like
> public abstract class AbstractSessionBean implements SessionBean {...}
> public class AsyncPipesImpl extends AbstractSessionBean implements AsyncPipes {
> ...some business methods with xdoclet declarations...
> /**
> * @ejb.interface-method
> * @ejb.transaction-method type="Supports"
> */
> public void additionalMethods () { ... implementation ... }
> }
> public interface AsyncPipes extends Serializable {
> public void additionalMethods();
> }
> EJB class is declared as:
> /*
> * @ejb.bean ...
> * @ejb.interface extends="AsyncPipesImpl,javax.ejb.EJBObject"
> * local-extends=" AsyncPipes,javax.ejb.EJBLocalObject"
> */
> public class ImportEJB extends AsyncPipesImpl {
> ... implementation ...
> }
> When I run EjbJarXmlPlugin I see that all declarations in AsyncPipesImpl are ignored and ejb-jar.xml doesn't contain any of its methods.
> Same behavior with EjbConfig plugin, it doesn't check validity of xdoclet descriptors in the AsyncPipesImpl.
> Aslo I've noticed that EJB plugin generates nothing if I don't add "implements SessionBean" explicitly in declaration of ImportEJB class, however it would get this information from super class, so I have to put unnecessary declaration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H