[#EJB-13] [Stateful session bean] bean interface and bean implementation class does not match

Issue Details [XML]

Key:	EJB-13
Type:	Bug
Status:	Open
Priority:	Major
Assignee:	Sascha-Matthias Kulawik
Reporter:	Stefan Siegl
Votes:	0 (View)
Watchers:	0 (View)

Operations

If you were logged in you would be able to see more operations.

EJB Cartridge

[Stateful session bean] bean interface and bean implementation class does not match

Created: 06/Oct/04 09:49 AM Updated: 27/Jul/05 11:32 AM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

File Attachments:	1. SessionRemote.vsl-attributes-patch.diff (0.7 kb)
Environment:	Win2k, Java 1.4.2, andromda snapshot of 3rd of october

Description

I already put in the bug EJB-12. After changing the line as described at the end of the bug report, the fields are created correctly, but another problem arises.

I am refering to the same example as in bug report EJB-12:
I used a simple SessionBean, called "MyService", added the stereotype "Service" and added a field called "name" of the type "String" (just in case my little image is not readable).

The bean implemenatation class "MyServiceBean" adds a private accessor and mutator method for the created field "name". The problem is, that the bean interface "MyService" defines these methods as public methods (business methods) and the EJB specification states, that the bean implementation class must provide an implementation of these methods in the same way as defines in the business interface. Therefore a deploy to an application server will result in an error.

All

Comments

Change History

Sort Order:

[ Permlink ]

Comment by Lorenz Froihofer [27/Jul/05 11:28 AM]

This patch resolves this bug by only adding attributes with public visibility to the remote interface (SessionRemote.vsl). Interestingly, this bug is not present in SessionLocal.vsl.

[ Permlink ]

Comment by Lorenz Froihofer [27/Jul/05 11:32 AM]

Forgot to mention that the patch was built by using the 3.0 release of AndroMDA.