The following issue has been updated:
Updater: Andrew Stevens (mailto:[EMAIL PROTECTED])
Date: Sun, 16 Nov 2003 6:16 PM
Changes:
Component changed to EJB Module
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-633&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-633
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XDT-633
Summary: ejb deployment errors with inherited abstract classes.
Type: Bug
Status: Assigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: XDoclet
Components:
EJB Module
Versions:
1.2 Beta 3
Assignee: xdoclet-devel (Use for new issues)
Reporter: Tim
Created: Thu, 11 Sep 2003 3:35 AM
Updated: Sun, 16 Nov 2003 6:16 PM
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
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
