Message: The following issue has been re-assigned.
Assignee: Matthias Germann (mailto:[EMAIL PROTECTED]) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/xdoclet/browse/XDT-633 Here is an overview of the issue: --------------------------------------------------------------------- Key: XDT-633 Summary: ejb deployment errors with inherited abstract classes. Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: XDoclet Components: EJB Module Versions: 1.2 Beta 3 Assignee: Matthias Germann Reporter: Tim Created: Thu, 11 Sep 2003 3:35 AM Updated: Sat, 12 Feb 2005 4:56 AM Environment: Redhat Linux 9.0 j2sdk1.4.2_01 Description: NOTE: NO failure in 1.2 b1 or 1.2 b2. Failure occurs **only** in 1.2 b3. >>> Class BaseSession is Abstract : public abstract class BaseSession { /** * Create the Session Bean * * @throws CreateException * * @ejb.create-method **/ public void ejbCreate() throws CreateException { } //blah blah blah } >>> Class Foo is Abstract : public abstract class Foo extends BaseSession { /** * * @ejb.interface-method view-type="both" * @ejb.transaction type="Required" */ public void f1() throws SomeException { } } } >>> Class Boo is concrete. public Boo extends Foo implements SessionBean { /** * * @ejb.interface-method view-type="both" * @ejb.transaction type="Required" */ public void f2() throws SomeException { } } } >>>> What Goes Wrong: In the ejb deployment Foo appears in <container-transaction> tag for every method Foo defines that has an @ejb deployment tag. This is wrong should be Boo methods since Boo inherits Foo. In 1.2b2 and 1.2b1 it was Boo and deployed ok. For instance in 1.2b3 you see Foo.f1() declared rather that Boo.f1() which WAS the case in 1.2b1 and 1.2b2. What you see is methods for Boo defined in ejb-jar.xml ok then all methods for Foo. Since for is not an actual bean, deployment fails when loading into jboss. the generate="false" tag on abstract beans seems to have no effect. >>>> What I noticed was that in 1.2b3 the xjavadoc was xjavadoc-1.0 not so for >>>> b2 and b1. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ xdoclet-devel mailing list xdoclet-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
